OpenParable
Skip to content
← Back to skills

Orchestrator Worker

Productivity
orchestrator-worker

Orchestrator Worker is an Agent Skill for productivity published in the Th0rgal/sandboxed.sh repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Worker skill for boss-spawned missions. Stay within scope, verify, and report blockers quickly.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/Th0rgal/sandboxed.sh/blob/HEAD/skills/orchestrator-worker/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/orchestrator-worker, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Orchestrator Worker

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.

Rules

  1. Stay inside the assigned scope. Do not widen the task on your own.
  2. Work only in the provided working directory or branch.
  3. Do not modify files outside your scope unless the boss explicitly expands it.
  4. Verify with the command from the prompt before finishing.
  5. Do not report DONE unless the files on disk actually match your claimed result.
  6. If the prompt is wrong, the task is impossible, or scope is insufficient, report that immediately instead of exploring unrelated work.
  7. Be concise. Prefer changes, verification, and a short status over long explanation.

Communication

The boss may send follow-up messages or retask you. Treat them as updated instructions and reprioritize immediately.

Completion

When done, make the result easy to integrate:

  • commit on your branch if you changed files
  • include the verification result
  • include the changed file paths
  • report one of: DONE, BLOCKED, or NOT_FEASIBLE