Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →udecode/orchestrator
Turn the current Codex thread into a coordination thread that routes implementation work to durable reusable child threads in disposable worktrees with short-lived branches targeting main.
Passed 16 of 22 test cases with the skill, and 8 of 22 without it.
and 12 more in the full report
10 fixed6 passed either way4 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
After copying ignored environment configuration files into a freshly created sibling worktree directory, what git command must be run immediately to verify the root path, and what directories must be excluded during the copy?
| Checked | Without skill | With skill |
|---|---|---|
| Runs `git rev-parse --show-toplevel` immediately after copying environment files. | Missed | Passed |
| Excludes `.git` and dependency directories during the file copy. | Passed | Passed |
The instructions your model reads when the skill loads.
Use this skill when the user wants the current thread to act as a chief-of-staff thread: route work, keep context, supervise child threads, arbitrate conflicts, and avoid doing implementation locally.
$orchestrator on: activate orchestration-only mode for this thread.$orchestrator off: return this thread to normal local execution.$orchestrator status: report mode, active child threads, checkout slots,
branches, ports, data strategies, blockers, and push state.Routing is automatic while orchestrator mode is on. Do not invent a manual routing command.
Worktrees alone are not orchestrator mode.
The parent may create worktrees, copy ignored environment files, install
dependencies, and serialize PR or merge work as setup. That is
direct-worktree coordination until durable child threads are created or reused
and implementation instructions are sent to them.
Before code-changing work starts under an orchestrator claim:
orchestrator mode: on in the active plan or status.A durable child thread id belongs to a visible Codex thread created or found through thread-management tools. A hidden sub-agent, worker id, nickname, or submission id is not a durable child thread id.
If the child thread is attached to the root project but assigned to a manual
sibling worktree, every apply_patch target must be absolute under the assigned
test cases passed, vs 8 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.