agent-orchestration
Skill2 starsChanged 4 days agoApache-2.0View on GitHub
Coordinate multiple workers without recreating Codex's scheduler.
27 other projects use a version of this.
Adopted by
Most recently taken up by
- daryaKuto/claude-skillstheir own version, first seen Nov 15, 2026
- contactandrewchl-wq/turtle-mcptheir own version, first seen Nov 15, 2026
- CassetteTapeCrackle/claude-starterstheir own version, first seen Nov 8, 2026
- 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
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 versions27 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 27
- 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
- contactandrewchl-wq/turtle-mcp★ 2same name
- juninmd/skills★ 2same name
- CassetteTapeCrackle/claude-starters★ 1same name
17 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 repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- change-aware-verificationSkill
- context-continuitySkill
- execution-intent-preservationSkill
- independent-engineering-reviewSkill
- observable-progressSkill
- outcome-driven-engineeringSkill
- prototype-firstSkill
- repair-and-resumeSkill
- source-custodySkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 26 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Keep one accountable coordinator and allocate nonoverlapping assignments.
- Distinctive: line 15
Wait on useful worker outcomes, not repeated status polling.
- Distinctive: line 16
Avoid mandatory reviewer agents and redundant investigations.
“Common” is measured: kept by at least 6 in 10 of the 26 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
Objective
Coordinate multiple workers without recreating Codex's scheduler.
Practice
- Keep one accountable coordinator and allocate nonoverlapping assignments.
- Give workers original issues, selected playbooks and relevant skills.
- Dispatch independent work concurrently when capacity permits.
- Wait on useful worker outcomes, not repeated status polling.
- Avoid mandatory reviewer agents and redundant investigations.
Guidance only. Do not introduce new Graph services, approval gates or required reviewer loops.
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.