Swarm Orchestration
ruvnet/ruflo
Coordinates a hierarchical swarm of specialized agents through the claude-flow CLI for work that spans several files or modules at once.
Coordinate several workers: what idle agents do next, which finished work gets checked first, how to recover a dead one.
Apache-2.0Auto-check passed
Install Orchestrate
$ npx skills add boshu2/agentops --skill orchestrate -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install boshu2/agentops orchestrate --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/boshu2/agentops.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/orchestrate .claude/skills/orchestrate && 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 "orchestrate" agent skill from https://github.com/boshu2/agentops/tree/main/skills/orchestrate into .claude/skills/orchestrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrate", 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/boshu2/agentops/tree/main/skills/orchestrateType 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 boshu2/agentops --skill orchestrate -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install boshu2/agentops orchestrate --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boshu2/agentops.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/orchestrate .agents/skills/orchestrate && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "orchestrate" agent skill from https://github.com/boshu2/agentops/tree/main/skills/orchestrate into .agents/skills/orchestrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrate", 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 boshu2/agentops --skill orchestrate -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install boshu2/agentops orchestrate --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boshu2/agentops.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/orchestrate .cursor/skills/orchestrate && 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 "orchestrate" agent skill from https://github.com/boshu2/agentops/tree/main/skills/orchestrate into .cursor/skills/orchestrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrate", 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/boshu2/agentops.git --path skills/orchestrate--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 boshu2/agentops --skill orchestrate -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install boshu2/agentops orchestrate --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boshu2/agentops.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/orchestrate .gemini/skills/orchestrate && 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 "orchestrate" agent skill from https://github.com/boshu2/agentops/tree/main/skills/orchestrate into .gemini/skills/orchestrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrate", 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 boshu2/agentops orchestrateInstalls 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 boshu2/agentops --skill orchestrate -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/boshu2/agentops.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/orchestrate .github/skills/orchestrate && 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 "orchestrate" agent skill from https://github.com/boshu2/agentops/tree/main/skills/orchestrate into .github/skills/orchestrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrate", 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 boshu2/agentops --skill orchestrate -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install boshu2/agentops orchestrate --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/boshu2/agentops.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/orchestrate .opencode/skills/orchestrate && 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 "orchestrate" agent skill from https://github.com/boshu2/agentops/tree/main/skills/orchestrate into .opencode/skills/orchestrate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "orchestrate", 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
orchestrate- GitHub stars
- 447
- Used in
- 1 other repo
- Token cost
- ~2.3k tokens
- SKILL.md length
- 1,114 words
- Files
- 1
- Skills in repo
- 31
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Coordinate several workers: what idle agents do next, which finished work gets checked first, how to recover a dead one.
- : managing multiple agents
- SKILL.md covers Before any dispatch, Recover the actual work, Choose the next useful dispatch and Integrate and obtain judgment, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Orchestrate is an agent skill from boshu2/agentops. Coordinate several workers: what idle agents do next, which finished work gets checked first, how to recover a dead one. Use when: managing multiple agents.
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: DevOps discipline for AI coding agents: shape the work, track it as a graph, and get each change judged by a context that didn't write it. The licence is Apache-2.0.
When your agent uses it
- : managing multiple agents
Example prompts
- “/orchestrate”
What it can do on your machine
Read from SKILL.md and the folder at commit 3bdbfed. 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
No scripts in the folder and no shell commands in SKILL.md.
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
Orchestrate loads about 2.3k tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 1,114 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 boshu2/agentops at commit 3bdbfed, republished under its Apache-2.0 licence (© boshu2). 1,114 words, ~2,335 tokens.
Download SKILL.mdSave it as
.claude/skills/orchestrate/SKILL.md (or your agent's skills folder).- name
- orchestrate
- description
- Coordinate several workers: what idle agents do next, which finished work gets checked first, how to recover a dead one. Use when: managing multiple agents.
- practices
- team-topologies, evidence-based-engineering
- hexagonal_role
- supporting
- consumes
- accepted-intent, native-work-state, candidate-evidence
- produces
- native-handoffs, reconciled-feedback
- skill_api_version
- 1
- user-invocable
- true
- metadata.graph_root
- true
- metadata.tier
- execution
- metadata.capabilities
- coordinate_native_work, recover_assignments, reconcile_feedback
- metadata.effects
- dispatch_authorized_workers, update_native_handoffs
Orchestrate
Coordinate caller-authorized work through its existing tracker and runtime. Use the accepted task or conversation; a clear task needs zero mandatory skills. Selecting Orchestrate adds in-session guidance, not an AgentOps scheduler, work index, queue, ownership system, aggregate retry controller or delivery authority. The caller's tracker owns assignments and dependencies; its runtime owns running contexts, bounds and supervision; repository policy owns integration and delivery. Orchestrate decides what each worker does next. Agent Native launches and observes workers; Navigate picks the wave on a bead graph toward frozen acceptance and records verdicts.
Before any dispatch
- Finished is not done. Exit 0, a pushed branch, a closed tracker item or a worker saying "done" makes a candidate. It still owes its checks, integration and, when one is owed, a fresh judgment.
- Drain before starting. While candidates wait on checks, repair, integration or an owed judgment, free capacity goes there first. A free slot alone is not a dispatch reason; start new implementation with what is left.
- Judges did not author. Review or validation of a candidate goes to a context that did not write it.
- Readiness is content. A prerequisite counts only when its bytes are in the intended checkout. A closed item whose change is missing, stale or unavailable there is not ready: hold its dependents, keep its native status, and report the gap.
- Reconcile before resuming. Match tracker assignments against observed runtime state, validators included, before dispatching. Never duplicate an assignment because this conversation lacks it.
Recover the actual work
Read the accepted outcome, examples and scope from their current owner. Recover settled caller choices and rationale, completed history, consequential open questions and the next investigation from the existing native handoff. Do not repeat settled interviews or require the full transcript. Missing or contradictory pointers require source investigation, not a guessed decision.
Inspect, together: task acceptance, observed worker/context identity, workspace and starting content, occupied write scope, pending checks and review, current candidate identity, integration owner, and the actual content and evidence of each prerequisite. An empty ready list does not prove completion.
Choose the next useful dispatch
Concurrency follows the observed bottleneck. Reserve capacity for integration, review and repair, and reduce new starts while candidates accumulate. Record only the concrete constraint and next action in the existing native handoff, then reassess when evidence changes. Do not add a capacity ledger or queue.
Agent Native owns runtime mechanics: executor selection, startup and engagement evidence, actual context identity, normalized scopes, native waits and follow-up, bounds and cleanup. One-shot headless runs go through Codex Exec, Claude Exec or AGY Native. Concurrent writers require disjoint write scopes and separate isolation, including generated companions and transitive effects. Serialize shared paths. A worktree separates Git edits; it does not establish restricted-source or model-egress enforcement.
Dispatch a genuinely fresh implementer for one coherent accepted task, without the coordinator's accumulated transcript or unrelated research. A new goal, role label, cleared summary or resumed author context is not a fresh context. Pass the accepted examples, applicable constraints, exact starting content, usable prerequisites, authorized write/output scope, relevant source pointers, required checks, integration responsibility and real remaining bounds. Expand pointers when needed; brevity cannot omit a constraint. Record observed native identity at startup through Agent Native's existing association procedure.
Implement owns the complete change, meaningful checks and direct repair. It is optional guidance for that worker, not a compulsory stage. The handoff returns candidate identity, changed scope, check facts, discoveries and gaps; prompt delivery proves neither engagement nor acceptance.
Show full SKILL.md (536 more words)Show less
Integrate and obtain judgment
Name the integration responsibility before launch, and decide then whether the integrated candidate needs a fresh judgment at all. Follow the consumer repository's integration policy, include all changed paths and generated companions, and run affected checks on the actual integrated subject. Acceptance of a leaf does not establish the combined release.
For an ordinary candidate the integrated checks and CI are the gate. Assign one fresh author-distinct judgment through Validate, the sole skill owner of acceptance semantics, only when the caller asks, when a mistake cannot be cheaply undone after it lands (a published release or instructions users will follow, a security boundary, destroying data or tracker state, deleting a check that protects the product), or when no deterministic check covers the changed behavior. Preserve every explicitly required review leg. Advisory Review, Plan challenge and Council advice are not binding acceptance and cannot stand in for a judgment the caller requested.
One round. The validator does not re-run the integrated checks. Route back as repairs only what fails the accepted behavior or would mislead a user, break install or the CLI, or remove protection for the product; confirm each repair with a check. Changed candidate bytes need their affected checks rerun; they need a new judgment only when the caller asks for one. Keep review cost a fraction of the cost of the work. No report format or persisted artifact is mandatory unless the caller or an existing consumer requires one.
Reconcile feedback and resume
Preserve successful and failed evidence in the existing native task or handoff. Identify affected unfinished work and update its native dependencies or handoff within authority. Stop or explicitly re-scope an affected active assignment before it continues on a disproven premise; obtain observable acknowledgment or stopped runtime state before treating the revision as effective. Unaffected work continues unchanged. Repeating reconciliation with unchanged facts creates no new artifact or dispatch.
Plan owns consequential uncertainty, optional challenge and refining the next complete slice. Reuse settled decisions and accepted examples; new evidence may change an approach within the accepted outcome. A different promised outcome or authority choice returns to the caller. Agent advice cannot supply that choice. Preserve completed history instead of reopening accepted work merely to fit a revised story.
Known failures return to the responsible task for direct repair. On a genuine causal stall, the existing operating contract permits at most one authorized bounded fresh helper for that incident within remaining bounds; an unhelpful answer ends that attempt. Cancellation, refusal or exhausted bounds skip help. Replacement workers, retries, new subjects and compaction never reset those bounds. Inspect native evidence before replacing a worker; use native waits for unchanged pending state instead of repeated analysis or probes.
When maintained context could change the next action, use Memory find/recall; coordination triggers no automatic capture, import or recall.
A caller-selected external factory keeps its coordinator in control: hand it source intent through its supported door, never create, scale or repair its internal sessions by hand, and do not mirror its work in an AgentOps tracker. Judge the returned exact content independently; factory completion neither authorizes delivery nor establishes acceptance. For Gas City, follow Using GC.
Status block
When reporting coordination state, return:
assignments: <worker/context id> -> <task>, state as observed (how)
candidates: <task> -> <exact ref>; checks <result>; judgment <ref | owed | not owed>
next: <free capacity> -> <dispatch>, because <observed bottleneck>
held: <task>, blocked by <prerequisite gap>
handoffs: <affected work updated, and where>
gaps: <unobserved state, unknown identities, unresolved dissent>© boshu2, 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 skills/orchestrate of boshu2/agentops.
Open the folder on GitHubat commit 3bdbfed
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in boshu2/agentops, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Orchestrate 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 |
|---|---|---|---|---|---|---|
| Orchestrate this skillboshu2/agentops | 447 | 1 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Swarm Orchestrationruvnet/ruflo | 74k | 2 repos | ~779 | Automated safety check: Pass | MIT | |
| Superset Agent Orchestrationsuperset-sh/superset | 15k | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Orchestratesickn33/agentic-awesome-skills | 47k | 1 repos | ~692 | Automated safety check: Pass | MIT | |
| Team Agent Orchestrationaffaan-m/ECC | 275k | 1 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Cursor Orchestratecursor/plugins | 10k | — | ~1.1k | Automated safety check: Pass | None |
Similar skills
Superset Agent Orchestration
superset-sh/superset
Coordinates several coding agents in parallel through the Superset CLI, each in its own workspace, with a dependency table, bounded worker prompts and structured results.
Orchestrate
sickn33/agentic-awesome-skills
Coordinate focused subagents on substantial work, keep their ownership non-overlapping, and integrate verified results.
Team Agent Orchestration
affaan-m/ECC
Run team-based orchestration for agent squads: work items with owners and scope, agent Kanban state, branch isolation, control pane visibility, and merge gates.
- Official
Cursor Orchestrate
cursor/plugins
Splits a large goal into a tree of parallel Cursor cloud agents, with planners, workers and verifiers coordinated by a script and reporting through structured handoffs.
Orca Orchestration
stablyai/orca
Coordinate supervised Orca workers: threaded messages, blocking ask/reply, task dispatch, worker_done/escalation waits, task DAGs, decision gates, coordinator…
More from boshu2/agentops
All 31 skills in this repoAgent Native
boshu2/agentops
Dispatch independent tasks to parallel workers or subagents without write collisions.
Council
boshu2/agentops
Compare independent opinions from several models or contexts without inflating agreement.
Craft Goal
boshu2/agentops
Draft or lint a bounded long-running goal prompt with a finish line and hard limits.
Doc
boshu2/agentops
Write or update READMEs, docs, repo instructions and handoff notes, checked against source.
Idea Genie
boshu2/agentops
Brainstorm evidence-backed options for what to build, or stress-test an idea.
Implement
boshu2/agentops
Change or repair code, config or services without weakening tests; report what ran and what did not.
Questions about Orchestrate
What does Orchestrate do?
Coordinate several workers: what idle agents do next, which finished work gets checked first, how to recover a dead one. Orchestrate is an agent skill from boshu2/agentops. Coordinate several workers: what idle agents do next, which finished work gets checked first, how to recover a dead one.
When should I use Orchestrate?
Orchestrate fits situations like: : managing multiple agents.
How do I install Orchestrate in Claude Code?
Run `npx skills add boshu2/agentops --skill orchestrate -a claude-code`. Or copy the skill folder (skills/orchestrate in boshu2/agentops) into .claude/skills/orchestrate in your project. Claude Code loads it when a task matches its description.
How do I install Orchestrate in Codex?
Run `npx skills add boshu2/agentops --skill orchestrate -a codex`. Or copy the skill folder (skills/orchestrate in boshu2/agentops) into .agents/skills/orchestrate in your project. Codex loads it when a task matches its description.
Can I use Orchestrate 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 boshu2/agentops --skill orchestrate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/orchestrate, .gemini/skills/orchestrate, .github/skills/orchestrate and .opencode/skills/orchestrate in your project.
What does Orchestrate need to run?
SKILL.md names no scripts, command-line tools or credentials: Orchestrate is instructions for the agent only.
Does Orchestrate 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 Orchestrate 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 Orchestrate use?
Orchestrate 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 Orchestrate use?
About 2.3k tokens (SKILL.md is roughly 9.3k 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 Orchestrate?
Skills that share tags, products or a category with Orchestrate: Swarm Orchestration (ruvnet/ruflo, 74k stars), Superset Agent Orchestration (superset-sh/superset, 15k stars), Orchestrate (sickn33/agentic-awesome-skills, 47k stars) and Team Agent Orchestration (affaan-m/ECC, 275k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Orchestrate?
boshu2 (a GitHub user) maintains it in boshu2/agentops, which has 447 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on October 7, 2026.
Source: boshu2/agentops on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.