Team Topology
Cotal-AI/Cotal
Define a multi-agent team for ANY task on ANY system as an explicit deployment topology - pick the shape from the task's dominant risk, specify the runtime/communication/trust layers, place model…
Multi-agent orchestration patterns for production deployments.
$ npx skills add LeoYeAI/openclaw-master-skills --skill agent-orchestration -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills agent-orchestration --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/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/pl-agent-orchestration .claude/skills/agent-orchestration && 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 "agent-orchestration" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/pl-agent-orchestration into .claude/skills/agent-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-orchestration", 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/LeoYeAI/openclaw-master-skills/tree/main/skills/pl-agent-orchestrationType 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 LeoYeAI/openclaw-master-skills --skill agent-orchestration -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills agent-orchestration --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/pl-agent-orchestration .agents/skills/agent-orchestration && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "agent-orchestration" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/pl-agent-orchestration into .agents/skills/agent-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-orchestration", 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 LeoYeAI/openclaw-master-skills --skill agent-orchestration -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills agent-orchestration --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/pl-agent-orchestration .cursor/skills/agent-orchestration && 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 "agent-orchestration" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/pl-agent-orchestration into .cursor/skills/agent-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-orchestration", 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/LeoYeAI/openclaw-master-skills.git --path skills/pl-agent-orchestration--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 LeoYeAI/openclaw-master-skills --skill agent-orchestration -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills agent-orchestration --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/pl-agent-orchestration .gemini/skills/agent-orchestration && 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 "agent-orchestration" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/pl-agent-orchestration into .gemini/skills/agent-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-orchestration", 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 LeoYeAI/openclaw-master-skills agent-orchestrationInstalls 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 LeoYeAI/openclaw-master-skills --skill agent-orchestration -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/pl-agent-orchestration .github/skills/agent-orchestration && 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 "agent-orchestration" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/pl-agent-orchestration into .github/skills/agent-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-orchestration", 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 LeoYeAI/openclaw-master-skills --skill agent-orchestration -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install LeoYeAI/openclaw-master-skills agent-orchestration --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/pl-agent-orchestration .opencode/skills/agent-orchestration && 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 "agent-orchestration" agent skill from https://github.com/LeoYeAI/openclaw-master-skills/tree/main/skills/pl-agent-orchestration into .opencode/skills/agent-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agent-orchestration", 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.
agent-orchestrationMulti-agent orchestration patterns for production deployments.
Agent Orchestration is an agent skill from LeoYeAI/openclaw-master-skills. Multi-agent orchestration patterns for production deployments. Covers sub-agent QC workflow, model staggering across 5+ models, cross-validation patterns, fallback chains, task routing by model strength, ACPX configuration, and cost optimization. Use when coordinating multiple agents or models for complex workflows. Do NOT use for single-agent prompting, prompt engineering, or fine-tuning — those are separate skills.
Its SKILL.md is about 4.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `_meta.json`).
It sits in Agent Workflows, covering Multi-agent orchestration, Subagents and Machine learning. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.
7 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
geminiclaudeFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
ANTHROPIC_API_KEYOPENAI_API_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Agent Orchestration loads about 4.4k tokens when it runs. Until then it costs about 110 tokens; SKILL.md has 526 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.
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.
The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 526 words, ~4,410 tokens.
.claude/skills/agent-orchestration/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Production-tested patterns for coordinating multiple AI agents and models. This skill covers the full spectrum from simple fallback chains to complex multi-model workflows with cross-validation and quality control loops.
The core pattern: Produce → Review → Cross-Check → Incorporate → Deliver.
┌─────────────┐
│ 1. PRODUCE │ Sonnet 4.6 generates first draft
│ (Grinder) │ Fast, cost-effective, good enough for 80% of tasks
└──────┬──────┘
▼
┌─────────────┐
│ 2. REVIEW │ Same model self-reviews against criteria
│ (Self-QC) │ Catches obvious errors, formatting issues
└──────┬──────┘
▼
┌─────────────┐
│ 3. CROSS │ Different model (GPT-4o / Grok) validates
│ CHECK │ Catches blind spots, model-specific biases
└──────┬──────┘
▼
┌─────────────┐
│ 4. INCORP. │ Opus 4.6 synthesizes feedback
│ (Orchestr.) │ Resolves conflicts, applies judgment
└──────┬──────┘
▼
┌─────────────┐
│ 5. DELIVER │ Final output with confidence score
│ (Output) │ Includes provenance trail
└─────────────┘async def qc_workflow(task: str, context: dict) -> dict:
"""Five-step QC workflow with cross-model validation."""
# Step 1: Produce (Sonnet — fast, cheap)
draft = await call_model(
model="claude-sonnet-4-6",
prompt=f"Complete this task:\n{task}",
context=context,
max_tokens=4096
)
# Step 2: Self-review (same model, different prompt)
self_review = await call_model(
model="claude-sonnet-4-6",
prompt=f"""Review this output for errors, omissions, and quality:
TASK: {task}
OUTPUT: {draft}
Score 1-10 on: accuracy, completeness, clarity.
List specific issues to fix.""",
max_tokens=1024
)
# Step 3: Cross-check (different model family)
cross_check = await call_model(
model="gpt-4o",
prompt=f"""Independent review. Do NOT assume the draft is correct.
TASK: {task}
DRAFT: {draft}
SELF-REVIEW: {self_review}
Identify: factual errors, logical gaps, missing context, biases.""",
max_tokens=1024
)
# Step 4: Incorporate (Opus — best judgment)
final = await call_model(
model="claude-opus-4-6",
prompt=f"""Synthesize and produce final output.
TASK: {task}
DRAFT: {draft}
SELF-REVIEW: {self_review}
CROSS-CHECK: {cross_check}
Resolve any conflicts. Produce the best possible final output.
Include a confidence score (0-100) and list any unresolved concerns.""",
max_tokens=4096
)
# Step 5: Deliver with metadata
return {
"output": final,
"provenance": {
"producer": "claude-sonnet-4-6",
"reviewer": "claude-sonnet-4-6",
"cross_checker": "gpt-4o",
"synthesizer": "claude-opus-4-6",
"steps_completed": 5
}
}| Scenario | Skip | Rationale |
|---|---|---|
| Low-stakes internal task | Steps 3-4 | Self-review is sufficient |
| Time-critical (<30s budget) | Steps 2-4 | Single model, accept risk |
| High-stakes client deliverable | None | Full loop, every time |
| Coding task with tests | Step 3 | Tests serve as cross-check |
| Creative/subjective work | Step 3 | Cross-check adds noise, not signal |
Assign models to tasks based on their demonstrated strengths.
Model Strength Zone Cost Tier Speed
────────────────────────────────────────────────────────────────
Opus 4.6 Strategy, synthesis, $$$$$ Slow
complex reasoning,
judgment calls
Sonnet 4.6 Production work, coding, $$$ Fast
analysis, writing,
general-purpose grinder
GPT-4o Coding, scoring rubrics, $$$$ Medium
structured output,
alternative perspective
Grok X/Twitter analysis, $$ Fast
social media content,
real-time commentary
Gemini 2.5 Pro Deep research, long $$$ Medium
context analysis,
multimodal processing
Haiku 4.5 Classification, routing, $ Very Fast
simple extraction,
high-volume tasksrouting_rules:
# Strategic / High-judgment tasks → Opus
strategy:
models: [claude-opus-4-6]
triggers:
- "requires judgment between competing priorities"
- "synthesize conflicting information"
- "make a recommendation with tradeoffs"
- "review and improve another agent's work"
# Production work → Sonnet
production:
models: [claude-sonnet-4-6]
triggers:
- "write code to specification"
- "generate content from template"
- "analyze data and report findings"
- "standard business communication"
# Coding with scoring → GPT
coding_and_scoring:
models: [gpt-4o]
triggers:
- "write and debug complex algorithms"
- "score outputs against rubric"
- "generate structured JSON/YAML"
- "cross-validate another model's output"
# Social / real-time → Grok
social:
models: [grok-3]
triggers:
- "analyze X/Twitter trends"
- "generate social media content"
- "real-time event commentary"
- "meme-aware communication"
# Deep research → Gemini
research:
models: [gemini-2.5-pro]
triggers:
- "analyze documents >100K tokens"
- "cross-reference multiple long sources"
- "multimodal analysis (images + text)"
- "broad research synthesis"
# High-volume classification → Haiku
classification:
models: [claude-haiku-4-5]
triggers:
- "classify items into categories"
- "extract structured fields from text"
- "route incoming requests"
- "simple yes/no decisions"Example: "Write a market analysis report"
1. Gemini 2.5 Pro → Research phase (long context, web search)
2. Sonnet 4.6 → Draft the report (fast production)
3. GPT-4o → Score against quality rubric (structured eval)
4. Opus 4.6 → Final synthesis and executive summary (judgment)
5. Haiku 4.5 → Extract key metrics into structured JSON (cheap, fast)When a model is unavailable, rate-limited, or returns low-quality output, fall through to the next option.
fallback_chains:
# Primary reasoning chain
reasoning:
- model: claude-opus-4-6
timeout: 60s
retry: 1
- model: gpt-4o
timeout: 45s
retry: 1
- model: claude-sonnet-4-6
timeout: 30s
retry: 2
- model: gemini-2.5-pro
timeout: 45s
retry: 1
# Fast production chain
production:
- model: claude-sonnet-4-6
timeout: 30s
retry: 2
- model: gpt-4o
timeout: 30s
retry: 1
- model: grok-3
timeout: 20s
retry: 1
# Classification chain (optimize for cost)
classification:
- model: claude-haiku-4-5
timeout: 10s
retry: 3
- model: claude-sonnet-4-6
timeout: 15s
retry: 1async def call_with_fallback(chain: str, prompt: str) -> dict:
"""Try models in order until one succeeds with acceptable quality."""
for entry in CHAINS[chain]:
for attempt in range(entry["retry"] + 1):
try:
result = await call_model(
model=entry["model"],
prompt=prompt,
timeout=entry["timeout"]
)
# Quality gate: reject low-confidence outputs
if result.get("confidence", 100) < 30:
log(f"{entry['model']} returned low confidence, trying next")
break # Move to next model, don't retry
return {
"output": result,
"model_used": entry["model"],
"attempt": attempt + 1,
"fallback_depth": CHAINS[chain].index(entry)
}
except (TimeoutError, RateLimitError) as e:
log(f"{entry['model']} attempt {attempt+1} failed: {e}")
continue
raise AllModelsFailed(f"No model in chain '{chain}' produced acceptable output")ACPX (Agent Computer Protocol eXtended) enables tool-using agents to coordinate. Configuration for Claude Code and Codex environments.
In your project's CLAUDE.md:
# Agent Orchestration
## Sub-agent Spawning
When a task requires cross-model validation:
1. Use the Agent tool to spawn a sub-agent for the secondary task
2. The sub-agent inherits the project context but gets its own conversation
3. Results flow back to the orchestrator via the Agent tool response
## Model Selection
- Use claude-opus-4-6 for: architectural decisions, code review, complex debugging
- Use claude-sonnet-4-6 for: implementation, test writing, documentation
- Use claude-haiku-4-5 for: linting, formatting, simple refactors
## Tool Permissions
Sub-agents may: read files, search code, run tests
Sub-agents may NOT: push to git, modify CI/CD, delete files without confirmation{
"mcpServers": {
"orchestrator": {
"command": "node",
"args": ["./orchestrator-server.js"],
"env": {
"ANTHROPIC_API_KEY": "${ANTHROPIC_API_KEY}",
"OPENAI_API_KEY": "${OPENAI_API_KEY}",
"MAX_CONCURRENT_AGENTS": "5",
"DEFAULT_CHAIN": "production"
}
}
}
}# codex.yaml
agents:
orchestrator:
model: claude-opus-4-6
role: "Route tasks and synthesize results"
tools: [spawn_agent, review_output, merge_results]
grinder:
model: claude-sonnet-4-6
role: "Execute implementation tasks"
tools: [read_file, write_file, run_tests, search_code]
validator:
model: gpt-4o
role: "Cross-validate outputs"
tools: [read_file, run_tests, score_output]Subscription Models ($20-200/month flat):
Claude Pro/Max → Best for: daily interactive use, long sessions
ChatGPT Plus → Best for: GPT-4o access, plugins
Grok Premium → Best for: X integration, real-time
Gemini Advanced → Best for: Google ecosystem, long context
API Models (per-token):
claude-opus-4-6 → $15/M input, $75/M output
claude-sonnet-4-6 → $3/M input, $15/M output
claude-haiku-4-5 → $0.80/M input, $4/M output
gpt-4o → $2.50/M input, $10/M outputWhen you have active subscriptions, route interactive and exploratory work through subscriptions (zero marginal cost) and reserve API for automated/batch workflows.
Decision Tree:
Is this interactive/exploratory?
YES → Route through subscription (Claude Code, ChatGPT, etc.)
NO → Is this batch/automated?
YES → Use API with cheapest adequate model
NO → Is this high-volume (>1000 calls/day)?
YES → Use Haiku via API ($0.80/M input)
NO → Use Sonnet via API ($3/M input)Monthly AI Spend:
Subscriptions (fixed):
Claude Max $200.00
ChatGPT Plus $20.00
Grok Premium $30.00
Gemini Advanced $20.00
Subtotal Fixed $270.00
API Usage (variable):
Opus 4.6 42K tokens $3.78
Sonnet 4.6 380K tokens $6.84
Haiku 4.5 1.2M tokens $1.76
GPT-4o 95K tokens $1.19
Subtotal Variable $13.57
Total $283.57
Cost per task (avg) $0.28
Tasks completed 1,013Use the Agent tool to spawn sub-agents that inherit project context.
Orchestrator (Opus)
├── Agent: "Research the API surface" (Explore subagent)
├── Agent: "Implement the endpoint" (general-purpose subagent)
└── Agent: "Write tests" (general-purpose subagent)Best for: tasks where sub-agents need file system access and project context.
Call model APIs directly for tasks that don't need project context.
# Spawn multiple validators in parallel
import asyncio
async def parallel_validate(content: str) -> list:
tasks = [
call_model("claude-sonnet-4-6", f"Review for accuracy:\n{content}"),
call_model("gpt-4o", f"Review for accuracy:\n{content}"),
call_model("gemini-2.5-pro", f"Review for accuracy:\n{content}"),
]
return await asyncio.gather(*tasks)Best for: cross-validation, scoring, classification — tasks that are self-contained.
The orchestrator plans and delegates. Grinders execute. Never let a grinder make strategic decisions.
ORCHESTRATOR (Opus 4.6):
- Reads the task requirements
- Breaks into subtasks
- Assigns each subtask to appropriate grinder
- Reviews grinder outputs
- Synthesizes final deliverable
- Makes judgment calls on conflicts
GRINDER (Sonnet 4.6 / GPT-4o):
- Receives specific, scoped subtask
- Executes without strategic decisions
- Returns output with confidence score
- Flags uncertainty rather than guessing| Anti-Pattern | Problem | Fix |
|---|---|---|
| Grinder makes strategic calls | Inconsistent decisions, wasted work | Escalate to orchestrator |
| Orchestrator does grinder work | Slow, expensive, bottleneck | Delegate production tasks |
| No quality gate between steps | Errors compound through pipeline | Add review step after each stage |
| Same model reviews its own work | Blind spots persist | Cross-model validation |
| Spawning agents for trivial tasks | Overhead exceeds task cost | Direct call for simple tasks |
| Infinite retry loops | Cost explosion | Max 3 retries, then escalate |
This is the foundational principle of multi-agent systems.
The orchestrator thinks. The grinder does. Never confuse the two.
ORCHESTRATOR GRINDER
───────────────────────────────── ─────────────────────────────────
Decides WHAT to do Decides HOW to do it
Chooses which model/tool Uses the tools it's given
Reviews and judges quality Produces and reports confidence
Resolves conflicts between agents Flags conflicts for resolution
Owns the final output Owns its subtask output
Expensive, slow, high-judgment Cheap, fast, high-throughput
1 per workflow N per workflow"Should this be an orchestrator or grinder decision?"
Ask: "If two reasonable people disagreed on this, would it matter?"
YES → Orchestrator decision (judgment required)
NO → Grinder decision (execution, not judgment)
Ask: "Does this affect the overall workflow direction?"
YES → Orchestrator decision
NO → Grinder decision
Ask: "Could a junior employee do this with clear instructions?"
YES → Grinder task
NO → Orchestrator taskORCHESTRATOR (Opus):
1. Read client brief → decide deliverable structure
2. Break into sections → assign to grinders
3. Review all sections → identify gaps
4. Resolve quality issues → request rewrites
5. Synthesize → produce final deliverable
6. Generate executive summary → deliver
GRINDER 1 (Sonnet): Write Section A per outline
GRINDER 2 (Sonnet): Write Section B per outline
GRINDER 3 (GPT-4o): Generate data tables and charts
GRINDER 4 (Gemini): Research background for Section C
GRINDER 5 (Haiku): Format citations and referencesTotal cost: 1 Opus call (synthesis) + 5 cheaper calls (production) vs. doing everything in Opus: 6 Opus calls at 5x the cost.
© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file in skills/pl-agent-orchestration of LeoYeAI/openclaw-master-skills.
Open the folder on GitHubat commit e5199b5
Agent Orchestration 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 |
|---|---|---|---|---|---|---|
| Agent Orchestration this skillLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.4k | Automated safety check: Pass | MIT | |
| Team TopologyCotal-AI/Cotal | 313 | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Microsoft Foundrymicrosoft/GitHub-Copilot-for-Azure | 255 | 1 repos | ~6.7k | Automated safety check: Pass | MIT | |
| Claude Code Agent Developmentanthropics/claude-plugins-official | 38k | 7 repos | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Swarm Parallel Dispatchlangchain-ai/langchain-skills | 1.3k | — | ~3k | Automated safety check: Pass | MIT | |
| Fable Foremanolsenbrands/fable-foreman | 142 | — | ~5.2k | Automated safety check: Pass | MIT |
Cotal-AI/Cotal
Define a multi-agent team for ANY task on ANY system as an explicit deployment topology - pick the shape from the task's dominant risk, specify the runtime/communication/trust layers, place model…
microsoft/GitHub-Copilot-for-Azure
Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end.
anthropics/claude-plugins-official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
langchain-ai/langchain-skills
Fans a list of independent items out to subagents in parallel, merges the results back into a table and supports retrying only the rows that failed.
olsenbrands/fable-foreman
Turns the lead model into a foreman that plans, routes and verifies while cheaper Claude, Codex or Grok workers do the typing, using a per-machine routing card.
greatSumini/cc-system
Create specialized Claude Code sub-agents with custom system prompts and tool configurations.
LeoYeAI/openclaw-master-skills
Manages pipelines on a DevOps quality and efficiency platform through its OpenAPI: list workspaces and templates, create, update, run and cancel pipelines, and read run records.
LeoYeAI/openclaw-master-skills
Patches OpenClaw's Feishu extension so an edited document triggers an isolated agent session that reads the doc and replies inline, turning it into a live chat space.
LeoYeAI/openclaw-master-skills
Multi-context memory management system for OpenClaw agents with group-isolated storage, global shared memory, workspace organization, and group-specific skills isolation.
LeoYeAI/openclaw-master-skills
Runs a brand's AI-search visibility work end to end: diagnosing how AI platforms represent it, repositioning it, producing AI-optimized content and monitoring ongoing mentions.
LeoYeAI/openclaw-master-skills
Installs and authenticates the gws CLI, then automates Gmail, Drive, Sheets, Calendar, Docs, Chat and Tasks with ready-made recipes, persona bundles and security audits.
LeoYeAI/openclaw-master-skills
Runs four advisor roles, a fitness coach, nutritionist, data analyst and TCM practitioner, to build a health profile and track workouts, diet and wellness over time.
Categories
Multi-agent orchestration patterns for production deployments. Agent Orchestration is an agent skill from LeoYeAI/openclaw-master-skills. Multi-agent orchestration patterns for production deployments.
Agent Orchestration fits situations like: coordinating multiple agents; models for complex workflows; single-agent prompting; prompt engineering.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill agent-orchestration -a claude-code`. Or copy the skill folder (skills/pl-agent-orchestration in LeoYeAI/openclaw-master-skills) into .claude/skills/agent-orchestration in your project. Claude Code loads it when a task matches its description.
Run `npx skills add LeoYeAI/openclaw-master-skills --skill agent-orchestration -a codex`. Or copy the skill folder (skills/pl-agent-orchestration in LeoYeAI/openclaw-master-skills) into .agents/skills/agent-orchestration in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add LeoYeAI/openclaw-master-skills --skill agent-orchestration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/agent-orchestration, .gemini/skills/agent-orchestration, .github/skills/agent-orchestration and .opencode/skills/agent-orchestration in your project.
Going by SKILL.md and its folder, Agent Orchestration needs the command-line tools its instructions call (gemini and claude) and credentials named ANTHROPIC_API_KEY and OPENAI_API_KEY. Our summary lists: Python 3; A credential in ANTHROPIC_API_KEY; A credential in OPENAI_API_KEY.
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.
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.
Agent Orchestration is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.4k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Agent Orchestration: Team Topology (Cotal-AI/Cotal, 313 stars), Microsoft Foundry (microsoft/GitHub-Copilot-for-Azure, 255 stars), Claude Code Agent Development (anthropics/claude-plugins-official, 38k stars) and Swarm Parallel Dispatch (langchain-ai/langchain-skills, 1.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,160 GitHub stars. The repository holds 1,235 skills in this directory. The repository was last updated on July 20, 2026.
Source: LeoYeAI/openclaw-master-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.