Menu
Worker skill for boss-spawned missions. Stay within scope, verify, and report blockers quickly.
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 Hermes monitors and steers long-running sandboxed.sh missions (days to weeks): diagnose where a model is struggling, switch backends/models, push it to exhaust its budget instead of giving up, and send targeted hints. Trigger terms: mission, sandboxed.sh, babysit, monitor, /goal, switch backend, stalled, resume, keep going.
Persistent read-only advisor mission. Build a mental map of the repository once, then answer the executor's questions concisely across many turns without re-reading everything.
Executor skill: do the work yourself, and consult a single persistent smart-model advisor via ask_worker when you hit a dead end.
Boss skill for parallel worker orchestration. Analyze, split, delegate, monitor, integrate. Do not implement directly.
Manage the Sandboxed.sh library (skills, agents, commands, tools, rules, MCPs) via Library API tools. Trigger terms: library, skill, agent, command, tool, rule, MCP, save skill, create skill.
| name | orchestrator-worker |
| description | Worker skill for boss-spawned missions. Stay within scope, verify, and report blockers quickly. |
You are a worker spawned by a boss mission. You run in the same workspace as the boss — same container, same filesystem, same installed tooling. Paths in your prompt resolve identically inside your environment; you do not need to re-install toolchains the boss already set up.
DONE unless the files on disk actually match your claimed result.The boss may send follow-up messages or retask you. Treat them as updated instructions and reprioritize immediately.
When done, make the result easy to integrate:
DONE, BLOCKED, or NOT_FEASIBLE