Orca CLI
stablyai/orca
Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser…
Canonical reusable orchestration procedures for the ClosedLoop planning/implementation orchestrators — PLANVALIDATIONSEQUENCE and AWAITINGUSERSEQUENCE.
Install Orchestrator Sequences
$ npx skills add closedloop-ai/claude-plugins --skill orchestrator-sequences -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install closedloop-ai/claude-plugins orchestrator-sequences --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/closedloop-ai/claude-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/code/skills/orchestrator-sequences .claude/skills/orchestrator-sequences && 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-sequences" agent skill from https://github.com/closedloop-ai/claude-plugins/tree/main/plugins/code/skills/orchestrator-sequences into .claude/skills/orchestrator-sequences/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrator-sequences", 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/closedloop-ai/claude-plugins/tree/main/plugins/code/skills/orchestrator-sequencesType 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 closedloop-ai/claude-plugins --skill orchestrator-sequences -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install closedloop-ai/claude-plugins orchestrator-sequences --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/closedloop-ai/claude-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/code/skills/orchestrator-sequences .agents/skills/orchestrator-sequences && 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-sequences" agent skill from https://github.com/closedloop-ai/claude-plugins/tree/main/plugins/code/skills/orchestrator-sequences into .agents/skills/orchestrator-sequences/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrator-sequences", 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 closedloop-ai/claude-plugins --skill orchestrator-sequences -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install closedloop-ai/claude-plugins orchestrator-sequences --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/closedloop-ai/claude-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/code/skills/orchestrator-sequences .cursor/skills/orchestrator-sequences && 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-sequences" agent skill from https://github.com/closedloop-ai/claude-plugins/tree/main/plugins/code/skills/orchestrator-sequences into .cursor/skills/orchestrator-sequences/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrator-sequences", 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/closedloop-ai/claude-plugins.git --path plugins/code/skills/orchestrator-sequences--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 closedloop-ai/claude-plugins --skill orchestrator-sequences -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install closedloop-ai/claude-plugins orchestrator-sequences --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/closedloop-ai/claude-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/code/skills/orchestrator-sequences .gemini/skills/orchestrator-sequences && 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-sequences" agent skill from https://github.com/closedloop-ai/claude-plugins/tree/main/plugins/code/skills/orchestrator-sequences into .gemini/skills/orchestrator-sequences/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrator-sequences", 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 closedloop-ai/claude-plugins orchestrator-sequencesInstalls 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 closedloop-ai/claude-plugins --skill orchestrator-sequences -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/closedloop-ai/claude-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/code/skills/orchestrator-sequences .github/skills/orchestrator-sequences && 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-sequences" agent skill from https://github.com/closedloop-ai/claude-plugins/tree/main/plugins/code/skills/orchestrator-sequences into .github/skills/orchestrator-sequences/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrator-sequences", 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 closedloop-ai/claude-plugins --skill orchestrator-sequences -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install closedloop-ai/claude-plugins orchestrator-sequences --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/closedloop-ai/claude-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/code/skills/orchestrator-sequences .opencode/skills/orchestrator-sequences && 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-sequences" agent skill from https://github.com/closedloop-ai/claude-plugins/tree/main/plugins/code/skills/orchestrator-sequences into .opencode/skills/orchestrator-sequences/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrator-sequences", 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-sequences- GitHub stars
- 122
- Token cost
- ~777 tokens
- SKILL.md length
- 270 words
- Files
- 1
- Skills in repo
- 43
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Canonical reusable orchestration procedures for the ClosedLoop planning/implementation orchestrators — PLANVALIDATIONSEQUENCE and AWAITINGUSERSEQUENCE.
- Works in 4 steps: Activate code:plan-validate skill (runs… → If FORMAT_ISSUES: launch… → If VALID: launch @code:plan-validator… → …
- Tasks that involve Multi-agent orchestration
- SKILL.md covers PLAN_VALIDATION_SEQUENCE and AWAITING_USER_SEQUENCE
- Calls bash
What it does
Orchestrator Sequences is an agent skill from closedloop-ai/claude-plugins. Canonical reusable orchestration procedures for the ClosedLoop planning/implementation orchestrators — PLANVALIDATIONSEQUENCE and AWAITINGUSERSEQUENCE. Single source of truth shared by prompts/prompt.md (full loop), prompts/plan-prompt.md (/code:create-plan) and prompts/execute-prompt.md (/code:execute-implementation), which each load standalone and cannot reference one another at runtime. Triggers: - An orchestrator phase needs full plan validation (structural + semantic) — run PLANVALIDATIONSEQUENCE. - An…
Its SKILL.md is about 780 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Multi-agent orchestration. The repository describes itself as: Open-source Claude Code plugins for multi-agent software delivery. Plan-first SDLC workflow, code review, LLM quality judges, and self-learning — grounded in your codebase… The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Multi-agent orchestration
Example prompts
- “/orchestrator-sequences”
Requirements
- Python 3
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Activate code:plan-validate skill (runs Python script against $CLOSEDLOOP_WORKDIR)
- If FORMAT_ISSUES: launch @code:plan-writer to fix format issues, then re-activate code:plan-validate
- If VALID: launch @code:plan-validator with prompt: "WORKDIR=$CLOSEDLOOP_WORKDIR. SEMANTIC ONLY: Check semantic consistency of…
- If semantic check finds issues: launch @code:plan-writer to fix, then re-activate code:plan-validate
What it can do on your machine
Read from SKILL.md and the folder at commit 0e20ac0. 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:
bash
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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 Sequences loads about 777 tokens when it runs. Until then it costs about 162 tokens; SKILL.md has 270 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
The full file from closedloop-ai/claude-plugins at commit 0e20ac0, republished under its Apache-2.0 licence (© closedloop-ai). 270 words, ~777 tokens.
Download SKILL.mdSave it as
.claude/skills/orchestrator-sequences/SKILL.md (or your agent's skills folder).- name
- orchestrator-sequences
- description
- Canonical reusable orchestration procedures for the ClosedLoop planning/implementation orchestrators — PLAN_VALIDATION_SEQUENCE and AWAITING_USER_SEQUENCE. Single source of truth shared by prompts/prompt.md (full loop), prompts/plan-prompt.md (/code:create-plan) and prompts/execute-prompt.md (/code:execute-implementation), which each load standalone and cannot reference one another at runtime. Triggers: - An orchestrator phase needs full plan validation (structural + semantic) — run PLAN_VALIDATION_SEQUENCE. - An orchestrator reaches a hard stop that requires user action before continuing — run AWAITING_USER_SEQUENCE.
Orchestrator Reusable Procedures
These two procedures are referenced by name throughout the orchestrator prompts (prompt.md, plan-prompt.md, execute-prompt.md). They live here as the single source of truth so a change propagates to all three orchestrators at once. Substitute $CLOSEDLOOP_WORKDIR with the literal resolved workdir path in any subagent prompt (never the literal string $CLOSEDLOOP_WORKDIR).
PLAN_VALIDATION_SEQUENCE
Use this sequence whenever a phase needs full plan validation (structural + semantic):
- Activate
code:plan-validateskill (runs Python script against $CLOSEDLOOP_WORKDIR) - If
FORMAT_ISSUES: launch @code:plan-writer to fix format issues, then re-activatecode:plan-validate - If
VALID: launch @code:plan-validator with prompt: "WORKDIR=$CLOSEDLOOP_WORKDIR. SEMANTIC ONLY: Check semantic consistency of $CLOSEDLOOP_WORKDIR/plan.json — verify storage/query alignment and task/architecture decision consistency. Skip structural validation (already passed)." - If semantic check finds issues: launch @code:plan-writer to fix, then re-activate
code:plan-validate
AWAITING_USER_SEQUENCE
Use this sequence at any hard-stop that requires user action before continuing. The caller supplies the per-site phase, reason, file (path or null), and command (the resume command — built from the resolved CLOSEDLOOP_ORIGINAL_ARGS value, never the literal string $ARGUMENTS):
- FIRST — Write state.json with AWAITING_USER status:
echo '{"phase": "<current phase>", "status": "AWAITING_USER", "reason": "<why>", "userAction": {"description": "<what user should do>", "file": "<path or null>", "command": "<resume command>"}, "timestamp": "'$(date -u +%Y-%m-%dT%H:%M:%SZ)'"}' > $CLOSEDLOOP_WORKDIR/state.json - Record the native-command terminal iteration once:
bash "$CLAUDE_PLUGIN_ROOT/scripts/record_native_iteration_once.sh" "$CLOSEDLOOP_WORKDIR" 2>/dev/null || true - ONLY AFTER state.json is written — Output your command's completion promise:
<promise>PLAN_COMPLETE</promise>for/code:create-plan,<promise>IMPLEMENTATION_COMPLETE</promise>for/code:execute-implementation, or<promise>COMPLETE</promise>for the full/code:codeloop. Use the single promise token defined by your own prompt. - Tell the user what to do (review file, fix issues, run command)
- HARD STOP — Do not continue even if the user asks
© closedloop-ai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/code/skills/orchestrator-sequences of closedloop-ai/claude-plugins.
Open the folder on GitHubat commit 0e20ac0
Compare with similar skills
Orchestrator Sequences 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 Sequences this skillclosedloop-ai/claude-plugins | 122 | — | ~777 | Automated safety check: Pass | Apache-2.0 | |
| Orca CLIstablyai/orca | 87k | 2 repos | ~593 | Automated safety check: Pass | MIT | |
| Paseo Advisor Second Opiniongetpaseo/paseo | 20k | 1 repos | ~756 | Automated safety check: Pass | Custom licence | |
| O2 Review Loopopenobserve/openobserve | 22k | — | ~3.7k | Automated safety check: Pass | AGPL-3.0 | |
| Paseo Committeegetpaseo/paseo | 20k | 1 repos | ~496 | Automated safety check: Pass | Custom licence | |
| Mission Control Agent APIbuilderz-labs/mission-control | 6.3k | — | ~2.1k | Automated safety check: Pass | MIT |
Similar skills
Paseo Advisor Second Opinion
getpaseo/paseo
Launches one separate agent through Paseo to give a second opinion on the current task, with a self-contained briefing and no permission to edit files.
O2 Review Loop
openobserve/openobserve
Splits a change into planner, coder and independent reviewer roles: you confirm a spec, a subagent implements it, and a separate reviewer checks each round's local WIP commit.
Paseo Committee
getpaseo/paseo
Forms a two-agent committee with contrasting profiles to analyze a stuck problem in parallel, reconcile their views and return a consensus plan without editing files.
Mission Control Agent API
builderz-labs/mission-control
Teaches an agent to use the Mission Control dashboard API: register, send heartbeats, fetch assigned tasks, report progress and disconnect, with API key auth.
Paseo Agent Handoff
getpaseo/paseo
Hands off the current task, including context, decisions and failed attempts, to a fresh agent through Paseo by writing a self-contained briefing prompt and launching that agent.
More from closedloop-ai/claude-plugins
All 43 skills in this repoCodex Review
closedloop-ai/claude-plugins
Run Codex to review a plan file and return structured feedback with a verdict.
Critic Cache
closedloop-ai/claude-plugins
Check if critic reviews are still valid before re-running Phase 2.5 critics.
Cross Repo Cache
closedloop-ai/claude-plugins
Check if cross-repo coordinator results can be reused, avoiding redundant Sonnet agent launches.
Eval Cache
closedloop-ai/claude-plugins
Check for a cached plan-evaluation.json result before launching the plan-evaluator agent.
Find Plugin File
closedloop-ai/claude-plugins
This skill should be used when needing to locate files within the Claude Code plugins cache directory (~/.claude/plugins/cache).
Gh Monitor PR
closedloop-ai/claude-plugins
Start a detached GitHub pull-request monitor that wakes the exact launching Codex Desktop or CLI root through the managed Codex App Server when review, CI, conflict, merge-queue, closure, readiness…
Related
Categories
Questions about Orchestrator Sequences
What does Orchestrator Sequences do?
Canonical reusable orchestration procedures for the ClosedLoop planning/implementation orchestrators — PLANVALIDATIONSEQUENCE and AWAITINGUSERSEQUENCE. Orchestrator Sequences is an agent skill from closedloop-ai/claude-plugins. Canonical reusable orchestration procedures for the ClosedLoop planning/implementation orchestrators — PLANVALIDATIONSEQUENCE and AWAITINGUSERSEQUENCE.
When should I use Orchestrator Sequences?
Orchestrator Sequences fits situations like: tasks that involve Multi-agent orchestration.
How do I install Orchestrator Sequences in Claude Code?
Run `npx skills add closedloop-ai/claude-plugins --skill orchestrator-sequences -a claude-code`. Or copy the skill folder (plugins/code/skills/orchestrator-sequences in closedloop-ai/claude-plugins) into .claude/skills/orchestrator-sequences in your project. Claude Code loads it when a task matches its description.
How do I install Orchestrator Sequences in Codex?
Run `npx skills add closedloop-ai/claude-plugins --skill orchestrator-sequences -a codex`. Or copy the skill folder (plugins/code/skills/orchestrator-sequences in closedloop-ai/claude-plugins) into .agents/skills/orchestrator-sequences in your project. Codex loads it when a task matches its description.
Can I use Orchestrator Sequences 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 closedloop-ai/claude-plugins --skill orchestrator-sequences -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-sequences, .gemini/skills/orchestrator-sequences, .github/skills/orchestrator-sequences and .opencode/skills/orchestrator-sequences in your project.
What does Orchestrator Sequences need to run?
Going by SKILL.md and its folder, Orchestrator Sequences needs the command-line tools its instructions call (bash). Our summary lists: Python 3.
Does Orchestrator Sequences access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Orchestrator Sequences 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 Sequences use?
Orchestrator Sequences is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Orchestrator Sequences use?
About 777 tokens (SKILL.md is roughly 3.1k 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 Sequences?
Skills that share tags, products or a category with Orchestrator Sequences: Orca CLI (stablyai/orca, 87k stars), Paseo Advisor Second Opinion (getpaseo/paseo, 20k stars), O2 Review Loop (openobserve/openobserve, 22k stars) and Paseo Committee (getpaseo/paseo, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Orchestrator Sequences?
closedloop-ai (a GitHub organization) maintains it in closedloop-ai/claude-plugins, which has 122 GitHub stars. The repository holds 43 skills in this directory. The repository was last updated on October 7, 2026.
Source: closedloop-ai/claude-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.