Multi agent supervisor
Skill m00kk/agent-skills-playbook/skills/multi-agent-supervisor
15 production Agent Skills — MCP, LangGraph, RAG, security, Cursor SDK. MIT licensed.
npx -y skills add m00kk/agent-skills-playbook --skill multi-agent-supervisorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Implements the supervisor pattern: one orchestrator routes tasks to specialist agents (research, code, data). Use for multi-agent systems, delegating subtasks, LangGraph supervisor, or MCP-backed specialist workers.
SKILL.md
1.7 KB, 337 tokens by cl100k_base, as published. Nobody here has run it
Multi-Agent Supervisor
Architecture
User → Supervisor (routing only) → Specialist A | B | C → Supervisor → FINISH
Rule: Supervisor never executes tools directly — only picks the next worker.
Specialist design
| Specialist | Tools (via MCP) | Output |
|---|---|---|
| research | web_search, fetch_page | citations + summary |
| code | run_tests, lint, edit_files | patch or PR-ready diff |
| data | sql_query (read-only) | tables + interpretation |
Each specialist is a small ReAct or tool-calling subgraph with 2–5 tools max.
Routing prompt (supervisor)
Include in system message:
- List of workers with one-line capability
- Output format: exactly one of
[research, code, data, FINISH] - Stop when user goal satisfied; do not loop specialists unnecessarily
LangGraph sketch
- Node
supervisor— LLM returns next worker name - Nodes
research,code,data— run specialist; return to supervisor - Conditional edge from supervisor to worker or END
Failure handling
- Unknown route → default to clarifying question node
- Specialist error → append error to state; supervisor may retry once or escalate
- Max iterations (e.g. 15) to prevent infinite delegation
Scale-out
Add specialists by:
- New MCP server with focused tools
- New graph node + supervisor prompt line
- No change to other specialists
Pair with a2a-agent-delegation for cross-runtime agents.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most agent orchestration skills give in 337 tokens
Counted across 742 of the 995 authors here whose files we hold, read 2026-08-07
- Reference existing artifacts by path or URLin 53 of 742, across 25 files
- Run the full test suite after integrating changesin 51 of 742, across 19 files
- Dispatch one agent per independent problem domainin 50 of 742, across 17 files
- Verify fixes do not conflictin 45 of 742, across 13 files
- Include a suggested skills section in the documentin 45 of 742, across 17 files
- Redact sensitive informationin 41 of 742, across 11 files
- Save to the temporary directory of the operating systemin 39 of 742, across 10 files
- Tailor the document to user-provided focus argumentsin 39 of 742, across 9 files
- Spot check agent changes for systematic errorsin 34 of 742, across 7 files
- Write a handoff document summarising the current conversationin 31 of 742, across 6 files
- Assign each agent a specific scopein 23 of 742, across 8 files
- Provide specific scope and clear goalin 23 of 742, across 5 files
Said here and by no other author read
- restrict supervisor to routing only
- limit specialists to five tools maximum
- list worker capabilities in system message
- output exactly one worker name or finish
- stop when user goal is satisfied
- default unknown routes to clarifying question
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.