swarm-coordinator
Skill236 starsChanged 8 months agoMITView on GitHub
Coordinate multiple agents by splitting work into research, synthesis, implementation, and verification, assigning ownership, and keeping the coordinator focused on integration rather than raw exploration.
In this repository5 other files it gives its agents.
- dream-memorySkill
- kairos-liteSkill
- memory-extractorSkill
- structured-context-compressorSkill
- verification-gateSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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 8
Use this skill when a task is large enough that one coordinator and several bounded workers are more reliable than one monolithic agent …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Swarm Coordinator
Use this skill when a task is large enough that one coordinator and several bounded workers are more reliable than one monolithic agent loop.
Use It For
- broad codebase exploration
- cross-file bug hunts
- parallel review or research passes
- tasks that benefit from explicit synthesis before implementation
Avoid It For
- trivial edits
- urgent blocking steps that are faster to do locally
- delegation with no ownership boundaries
Quick Start
Generate a task-board skeleton:
python3 {baseDir}/scripts/task_board.py --goal "Investigate flaky CI failure" --worker research --worker implementation --worker verificationThen use the coordinator prompt in references/prompt-template.md.
Core Rule
The coordinator should own planning, routing, and synthesis. Workers should own bounded execution.
Supporting Files
- Prompt template: references/prompt-template.md
- Source notes: references/source-notes.md
- Helper script:
python3 {baseDir}/scripts/task_board.py ...
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.