Wf Player
catlog22/Claude-Code-Workflow
Workflow template player — load a JSON template produced by wf-composer, bind context variables, execute nodes in DAG order (serial/parallel), persist state at checkpoints, support resume from any…
Use Orchestrator as a CLI-backed skill to delegate and coordinate work across Claude Code, Codex, Copilot, Grok, Pi, shell, and custom runtimes.
Install Orchestrator
$ npx skills add backnotprop/orchestrator --skill orchestrator -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install backnotprop/orchestrator orchestrator --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/backnotprop/orchestrator.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/orchestrator .claude/skills/orchestrator && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "orchestrator" agent skill from https://github.com/backnotprop/orchestrator/tree/main/skills/orchestrator into .claude/skills/orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrator", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/backnotprop/orchestrator/tree/main/skills/orchestratorType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add backnotprop/orchestrator --skill orchestrator -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install backnotprop/orchestrator orchestrator --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/backnotprop/orchestrator.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/orchestrator .agents/skills/orchestrator && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "orchestrator" agent skill from https://github.com/backnotprop/orchestrator/tree/main/skills/orchestrator into .agents/skills/orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrator", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add backnotprop/orchestrator --skill orchestrator -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install backnotprop/orchestrator orchestrator --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/backnotprop/orchestrator.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/orchestrator .cursor/skills/orchestrator && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "orchestrator" agent skill from https://github.com/backnotprop/orchestrator/tree/main/skills/orchestrator into .cursor/skills/orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrator", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/backnotprop/orchestrator.git --path skills/orchestrator--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add backnotprop/orchestrator --skill orchestrator -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install backnotprop/orchestrator orchestrator --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/backnotprop/orchestrator.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/orchestrator .gemini/skills/orchestrator && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "orchestrator" agent skill from https://github.com/backnotprop/orchestrator/tree/main/skills/orchestrator into .gemini/skills/orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrator", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install backnotprop/orchestrator orchestratorInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add backnotprop/orchestrator --skill orchestrator -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/backnotprop/orchestrator.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/orchestrator .github/skills/orchestrator && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "orchestrator" agent skill from https://github.com/backnotprop/orchestrator/tree/main/skills/orchestrator into .github/skills/orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrator", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add backnotprop/orchestrator --skill orchestrator -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install backnotprop/orchestrator orchestrator --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/backnotprop/orchestrator.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/orchestrator .opencode/skills/orchestrator && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "orchestrator" agent skill from https://github.com/backnotprop/orchestrator/tree/main/skills/orchestrator into .opencode/skills/orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrator", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
orchestrator- GitHub stars
- 118
- Token cost
- ~1.7k tokens
- SKILL.md length
- 661 words
- Files
- 2
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Use Orchestrator as a CLI-backed skill to delegate and coordinate work across Claude Code, Codex, Copilot, Grok, Pi, shell, and custom runtimes.
- Works in 6 steps: Read PREFERENCES.md beside this file.… → Follow an explicit instruction in the… → Check the CLI with orchestrator --help.… → …
- An agent should launch one
- SKILL.md covers Start, Preferences, Choose Models and Delegate One Job, plus 5 more sections
- Calls npm
What it does
Orchestrator is an agent skill from backnotprop/orchestrator. Use Orchestrator as a CLI-backed skill to delegate and coordinate work across Claude Code, Codex, Copilot, Grok, Pi, shell, and custom runtimes. Use when an agent should launch one or many sub-agents, choose runtimes or models, apply the user's orchestration preferences, inspect background work, collect results, resume sessions, or stop stale work.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `PREFERENCES.md`).
It sits in Agent Workflows, covering Subagents and Session handoff. The repository describes itself as: Agents orchestrating other agents.
When your agent uses it
- An agent should launch one
- Many sub-agents
- Choose runtimes
- Apply the users orchestration preferences
Example prompts
- “/orchestrator”
Requirements
- Node.js
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Read PREFERENCES.md beside this file. Apply only non-comment content
- Follow an explicit instruction in the current user request before a stored
- Check the CLI with orchestrator --help. If missing and npm is available,
- Run orchestrator help --json --compact for the current command contract.
- Run orchestrator doctor --json --compact when runtime availability is
- Run orchestrator models --json --compact before choosing an
What it can do on your machine
Read from SKILL.md and the folder at commit 583acf4. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Orchestrator loads about 1.7k tokens when it runs. Until then it costs about 91 tokens; SKILL.md has 661 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 661 words (~1,701 tokens).
“Use Orchestrator to let the current agent coordinate other agents. The skill is the interface; the orchestrator CLI is the deterministic control plane underneath it.”
- name
- orchestrator
Files
SKILL.md and 1 other file in skills/orchestrator of backnotprop/orchestrator.
- SKILL.md
- PREFERENCES.md
Open the folder on GitHubat commit 583acf4
Compare with similar skills
Orchestrator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Orchestrator this skillbacknotprop/orchestrator | 118 | — | ~1.7k | Automated safety check: Pass | Custom licence | |
| Wf Playercatlog22/Claude-Code-Workflow | 2.1k | — | ~1.3k | Automated safety check: Notes | MIT | |
| Knowledge Agent Execution And OrchestrationechoVic/blade-code | 180 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Exploreyonatangross/orchestkit | 288 | — | ~3.9k | Automated safety check: Notes | MIT | |
| Processnotque/vexjoy-agent | 435 | — | ~2.1k | Automated safety check: Notes | MIT | |
| Claude Code Agent Developmentanthropics/claude-plugins-official | 37k | 8 repos | ~2.8k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Knowledge Agent Execution And Orchestration
echoVic/blade-code
覆盖 Blade 的 Agent 决策执行、子代理、Agent Teams、Goal、任务列表与定时任务编排. An agent skill from echoVic/blade-code.
Explore
yonatangross/orchestkit
Multi-angle codebase exploration spawning 3-5 parallel agents for code structure, data flow, architecture patterns, and health assessment.
Process
notque/vexjoy-agent
Process: retrospectives, session handoff, pair programming, subagent-driven development, condition-based waiting.
- Official
Claude Code Agent Development
anthropics/claude-plugins-official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
Orca CLI
stablyai/orca
Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser…
Related
Categories
Questions about Orchestrator
What does Orchestrator do?
Use Orchestrator as a CLI-backed skill to delegate and coordinate work across Claude Code, Codex, Copilot, Grok, Pi, shell, and custom runtimes. Orchestrator is an agent skill from backnotprop/orchestrator. Use Orchestrator as a CLI-backed skill to delegate and coordinate work across Claude Code, Codex, Copilot, Grok, Pi, shell, and custom runtimes.
When should I use Orchestrator?
Orchestrator fits situations like: an agent should launch one; many sub-agents; choose runtimes; apply the users orchestration preferences.
How do I install Orchestrator in Claude Code?
Run `npx skills add backnotprop/orchestrator --skill orchestrator -a claude-code`. Or copy the skill folder (skills/orchestrator in backnotprop/orchestrator) into .claude/skills/orchestrator in your project. Claude Code loads it when a task matches its description.
How do I install Orchestrator in Codex?
Run `npx skills add backnotprop/orchestrator --skill orchestrator -a codex`. Or copy the skill folder (skills/orchestrator in backnotprop/orchestrator) into .agents/skills/orchestrator in your project. Codex loads it when a task matches its description.
Can I use Orchestrator in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add backnotprop/orchestrator --skill orchestrator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/orchestrator, .gemini/skills/orchestrator, .github/skills/orchestrator and .opencode/skills/orchestrator in your project.
What does Orchestrator need to run?
Going by SKILL.md and its folder, Orchestrator needs the command-line tools its instructions call (npm). Our summary lists: Node.js.
Does Orchestrator access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Orchestrator safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Orchestrator use?
Orchestrator has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Orchestrator use?
About 1.7k tokens (SKILL.md is roughly 6.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Orchestrator?
Skills that share tags, products or a category with Orchestrator: Wf Player (catlog22/Claude-Code-Workflow, 2.1k stars), Knowledge Agent Execution And Orchestration (echoVic/blade-code, 180 stars), Explore (yonatangross/orchestkit, 288 stars) and Process (notque/vexjoy-agent, 435 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Orchestrator?
backnotprop (a GitHub user) maintains it in backnotprop/orchestrator, which has 118 GitHub stars. The repository was last updated on July 10, 2026.
Source: backnotprop/orchestrator on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.