feat(skills): support repo and external commands

.codex/skills/remote-tests/SKILL.md

@@ -1,6 +1,26 @@
 ---
 name: remote-tests
 description: How to run tests using remote executor.
+commands:
+  - name: build-remote-env
+    source: repo
+    example_argv: ["./scripts/test-remote-env.sh"]
+    purpose: Build and initialize the Docker container used by remote executor tests.
+  - name: list-devboxes
+    source: external
+    example_argv: ["applied_devbox", "ls"]
+    purpose: List available devboxes before selecting one with codex in the name.
+  - name: connect-devbox
+    source: external
+    example_argv: ["ssh", "<devbox_name>"]
+    purpose: Connect to the selected Linux devbox.
+workflow_defaults:
+  - name: remote_env
+    value: CODEX_TEST_REMOTE_ENV
+    description: Set when integration tests should use a remote executor.
+  - name: remote_checkout
+    value: ~/code/codex
+    description: Reuse the devbox checkout and keep SHA and modified files in sync.
 ---
 
 Some codex integration tests support a running against a remote executor.

.codex/skills/test-tui/SKILL.md

@@ -1,6 +1,18 @@
 ---
 name: test-tui
 description: Guide for testing Codex TUI interactively
+commands:
+  - name: start-tui
+    source: repo
+    example_argv: ["just", "codex", "-c", "log_dir=<some_temp_dir>"]
+    purpose: Start the TUI interactively from the repo recipe with logs directed to a temp directory.
+workflow_defaults:
+  - name: rust_log
+    value: RUST_LOG=trace
+    description: Always set trace logging when starting the TUI for interactive testing.
+  - name: input_delivery
+    value: text_then_enter
+    description: Send text first, then Enter as a separate write when driving the TUI programmatically.
 ---
 
 You can start and use Codex TUI to verify changes.