agent-orchestration
Skill1 starsChanged 3 months agoMITView on GitHub
Use to decide whether to delegate a task to a specialist agent, do it inline yourself, or skip — a cost/benefit policy over the project's scoped agents. Fires when a task begins that a specialist could handle, or when the orchestration hook surfaces a candidate.
24 other projects use a version of this.
Adopted by
Most recently taken up by
- juninmd/skillstheir own version, first seen Nov 8, 2026
- scoobydrew83/skillstheir own version, first seen Nov 3, 2026
- krema/agent-skillstheir own version, first seen Nov 1, 2026
- black-yt/skillstheir own version, first seen Nov 1, 2026
- Wiserax/wisecrafttheir own version, first seen Oct 25, 2026
- parcadei/Continuous-Claudetheir own version, first seen Oct 17, 2026
Used with
Projects with it also use mcp-builder and code-review.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillmcp-builder
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
Also in 3 projects that use this
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 3 projects that use this
Other versions24 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 24
- parcadei/Continuous-Claude★ 3.9ksame name
- parcadei/Continuous-Claude-v2★ 3.9ksame name
- parcadei/Continuous-Claude-v3★ 3.9ksame name
- codeaholicguy/ai-devkit★ 1.7ksame name
- GTMify/aigtm★ 25same name
- black-yt/skills★ 16same name
- Sathvikar01/Agent-engineering-skills★ 3same name
- juninmd/skills★ 2same name
- hongdp/deskd★ 1same name
- j1nn0/skills★ 1same name
14 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- clean-code-audioSkill
- clean-code-bashSkill
- clean-code-coreSkill
- clean-code-cppSkill
- clean-code-cSkill
- clean-code-goSkill
- clean-code-pythonSkill
- clean-code-rustSkill
- clean-code-tsSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 23 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Only consider agents that actually exist for this project: the ones in .claude/agents/ (scoped) plus the global ones.
- Distinctive: line 26
SKIP: if the agent's concern isn't really implicated, or the change is trivial (docs, a rename, a one-line tweak).
- Distinctive: line 34
After you've handled a surfaced candidate, don't re-evaluate the same unchanged diff.
“Common” is measured: kept by at least 6 in 10 of the 23 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Agent orchestration (the dispatcher policy)
You are the orchestrator. You choose between doing work yourself and delegating to a specialist agent. Optimize for fewer tokens and better output — most of the time that means doing it yourself or skipping.
Candidates come from two channels
- Reactive — the Stop hook surfaced a code-risk candidate (e.g.
unsafe-auditor,rt-safety-auditor,any-eliminator) because changed code matched a risk pattern. - Proactive — the phase of the current task maps to a specialist:
- ideate →
plugin-ideator/idea-brainstormer/competitor-analyst - spec/plan →
prd-writer/spec-critic - research an unknown →
deep-researcher - design UI →
ui-designer/ux-critic/plugin-ui-designer/design-system-author - debug →
debugger/regression-hunter - audit quality → the per-stack auditors +
starter-conformance-checker - ship →
technical-writer/release-copywriter/demo-script-writer/naming-agent
- ideate →
Only consider agents that actually exist for this project: the ones in .claude/agents/ (scoped) plus the global ones. Don't invent agents.
The decision — skip / inline / delegate
For each candidate, pick the cheapest option that gets the job done well:
- SKIP if the agent's concern isn't really implicated, or the change is trivial (docs, a rename, a one-line tweak). This is the most common answer. Don't dispatch to prove diligence.
- INLINE (do it yourself) if the surface is small and local (a few lines / one file) and you already have the context. Spinning a subagent would cost more than just doing it.
- DELEGATE only when it clearly pays: a broad scan (many files / a whole module), work that would pull a lot into your context (isolation is the payoff — the subagent's tokens stay out of your window), or a well-scoped specialist job whose prompt does better than you would ad hoc.
Rules
- Bias to skip/inline. When unsure and the surface is small, inline.
- One agent at a time; don't chain speculative delegations. Delegate, read the result, then decide the next step.
- Respect the project's own rules (its
CLAUDE.md) — e.g. don't let an agent touch DSP on a non-DSP task. - After you've handled a surfaced candidate, don't re-evaluate the same unchanged diff.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.