Menu
Run shell commands in a sandboxed Docker container with the project directory mounted at /workspace.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
How to orchestrate work across large documents and multi-agent delegations without burning token budgets. Reconnaissance-first, search-then-read, parallel-after-reconnaissance.
Decision criteria for delegating to the writer agent vs synthesising directly in your own response.
When and how to use the document library
How the Coder agent drives an OpenCode session via dispatch_coder — the engineering loop, when to dispatch, and how to verify the result is real (vs. claimed).
Maintain a personal index of interesting things, open questions, and follow-ups across sessions
When and how to render a promoted export to PDF via the export_pdf tool. Reads the writer's draft → export → PDF lifecycle and the operator-facing failure modes when the host is missing pandoc or tectonic.
| name | shell-sandbox |
| description | Run shell commands in a sandboxed Docker container with the project directory mounted at /workspace. |
| agents | coder |
You have access to a run_shell tool that executes commands in an isolated
Debian (bookworm-slim) container.
/workspace (the project root, mounted read-write)run_shell calls within a session — file writes,
installed packages, and directory changes are rememberedFor simple file reads and writes without a shell, prefer:
read_file / write_file / list_directory — direct host filesystem access,
no Docker overhead, work even if Docker is unavailablefetch_url — HTTP GET on the host, faster than curl in the containerset -e in scripts to fail fasthead -50 or tail -50 to stay within context limits