Agent skill

Claw Multi Agent

by LeoYeAI in LeoYeAI/openclaw-master-skills

Multi-agent parallel orchestration for OpenClaw. An agent skill from LeoYeAI/openclaw-master-skills.

MITAuto-check passedAgent Workflows

Install Claw Multi Agent

skills CLI
$ npx skills add LeoYeAI/openclaw-master-skills --skill claw-multi-agent -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install LeoYeAI/openclaw-master-skills claw-multi-agent --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/LeoYeAI/openclaw-master-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/claw-multi-agent .claude/skills/claw-multi-agent && rm -rf skills-src

Use ~/.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/

Facts

Skill name
claw-multi-agent
GitHub stars
2.2k
Token cost
~5.5k tokens
SKILL.md length
1,474 words
Files
11 (incl. scripts)
Skills in repo
1,235
Repo updated
First seen
Licence
MIT

At a glance

Multi-agent parallel orchestration for OpenClaw. An agent skill from LeoYeAI/openclaw-master-skills.

  • Words: multi-agent
  • SKILL.md covers What can it do?, ⚡ Get started in 30 seconds, 🎭 Interaction Style — How to… and 🤖 Model Selection Guide —…, plus 10 more sections
  • Runs Python scripts from its folder; calls python
  • Parallel agents

What it does

Claw Multi Agent is an agent skill from LeoYeAI/openclaw-master-skills. Multi-agent parallel orchestration for OpenClaw. Spawn AI agents as a team — parallel research, multi-model comparison, code pipelines. Proven 50-65% time savings. Trigger words: multi-agent, parallel agents, swarm, spawn multiple agents, parallel research, compare models, deep research, comprehensive research, detailed investigation, thorough analysis, research multiple topics, 多智能体, 多个Agent, 并行调研, 并行搜索, 同时搜索, 同时调研, 深度调研, 详细调研, 全面调研, 深度研究, 详细检索, 多角度分析, 全面分析, 多个模型, 让多个AI, 分别搜索, 同时搜索, 组建团队, Agent小队, 多Agent.

Its SKILL.md is about 5.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including scripts (for example `README.md`, `_meta.json` and `multiagent_engine.py`).

It sits in Agent Workflows, covering Multi-agent orchestration, Subagents and Deep research. It works with Kimi. The repository describes itself as: 🧠 Curated collection of 1209+ best OpenClaw skills — weekly updated by MyClaw.ai. The licence is MIT.

When your agent uses it

  • Words: multi-agent
  • Parallel agents
  • Spawn multiple agents
  • Parallel research

Example prompts

  • “/claw-multi-agent”

Requirements

  • Python 3

What it can do on your machine

Read from SKILL.md and the folder at commit e5199b5. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Claw Multi Agent loads about 5.5k tokens when it runs. Until then it costs about 132 tokens; SKILL.md has 1,474 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~132
When it runs · the whole SKILL.md, loaded when a task matches
~5.5k

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.

Safety

Auto-check passed

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); the scripts in this folder are not scanned.

SKILL.md

The full file from LeoYeAI/openclaw-master-skills at commit e5199b5, republished under its MIT licence (© LeoYeAI). 1,474 words, ~5,498 tokens.

Download SKILL.mdSave it as .claude/skills/claw-multi-agent/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.
name
claw-multi-agent
description
Multi-agent parallel orchestration for OpenClaw. Spawn AI agents as a team — parallel research, multi-model comparison, code pipelines. Proven 50-65% time savings. Trigger words: multi-agent, parallel agents, swarm, spawn multiple agents, parallel research, compare models, deep research, comprehensive research, detailed investigation, thorough analysis, research multiple topics, 多智能体, 多个Agent, 并行调研, 并行搜索, 同时搜索, 同时调研, 深度调研, 详细调研, 全面调研, 深度研究, 详细检索, 多角度分析, 全面分析, 多个模型, 让多个AI, 分别搜索, 同时搜索, 组建团队, Agent小队, 多Agent.

claw-multi-agent 🐝

Replace one AI with a team of AIs. Turn serial into parallel. Turn hours into minutes.


What can it do?

ScenarioExampleSpeedup
Parallel researchSearch 5 frameworks simultaneously, each writes a report~65% ⚡
Multi-model compareAsk Claude, Gemini, Kimi the same question at the same time~50% ⚡
Code pipelinePlan → Code → Review, auto hand-off in sequenceQuality ↑
Batch processingTranslate / analyze / summarize multiple docs in parallelScales linearly

⚡ Get started in 30 seconds

Just say something like:

  • "Research LangChain, CrewAI, and AutoGen in parallel"
  • "Have multiple agents search these topics and write a combined report"
  • "Compare how Claude and Gemini answer this question"
  • "Use multi-agent mode to do this research"

🎭 Interaction Style — How to Talk to the User

This is the recommended pattern. Every multi-agent run must follow this interaction pattern.

Step 0 — Announce skill activation FIRST

⚠️ Iron rule: The activation announcement must be your FIRST reply after receiving the task — before reading any files, before investigating, before spawning.

Why this matters: Reading files, researching background, and spawning all take time. If you do those first, users see long silence. Worse: context compression can happen during that time, and the announcement will never be sent.

Correct order: Receive task → Send announcement immediately → Then read files / spawn / wait

The very first thing to say when this skill is triggered — before any planning or spawning:

🐝 **claw-multi-agent 已唤醒**
多智能体并行模式启动,我来组建 Agent 小队处理这个任务。

This tells the user the skill is active and sets expectations for what's about to happen.

Before spawning — announce the plan

Right after the activation announcement, present the plan BEFORE calling sessions_spawn:

🚀 [N]个方向同时开搞,全面覆盖你的问题。

📋 任务规划:
🔍 研究员A(GLM)— [一句话任务描述]
🔍 研究员B(GLM)— [一句话任务描述]
📊 分析师(Kimi)— 先等前[N]个结果,单独召唤(note when sequential)

模式:🎯 指挥官模式(联网搜索)
预计耗时:~[X]s([N] Agent 并行[,分析师串行跟进])
正在派出 Agent 小队...

Role emoji reference:

RoleEmojiExample
Researcher🔍🔍 研究员A(GLM)— Research XX
Analyst📊📊 分析师(Kimi)— Deep comparison
Writer✍️✍️ 写作者(Gemini)— Draft the report
Coder💻💻 程序员(Kimi)— Implement the logic
Reviewer🔎🔎 审核员(GLM)— Quality check
Planner📋📋 规划师(Sonnet)— Break down tasks

Key rules:

  • ✅ Always list each agent with: emoji + role + model name + one-line task
  • ✅ State the mode (指挥官/流水线/混合) and estimated time
  • ✅ End announcement with: 正在派出 Agent 小队...
  • ✅ Note sequential agents as: "先等前N个结果,单独召唤"
  • ❌ Never silently call sessions_spawn without announcing
While waiting — brief note

After spawning, say one line:

⏳ 子 Agent 已全部出发,等结果回来...
After results — structured output (not raw dump)

Never paste sub-agent raw output directly. Always digest and restructure by content logic — NOT by agent order.

Recommended output order:

1. 执行统计卡 ← 先让用户知道跑了什么
2. 核心结论(3-5条最重要发现)← 最有价值的放最前面
3. 分主题展开细节(按内容逻辑组织,不按子Agent顺序)← 读起来是一篇完整文章
4. 下一步行动建议 ← 落地结尾

统计卡格式:

## 📊 执行统计
| Agent | 模型 | 耗时 | 状态 |
|-------|------|------|------|
| 🔍 研究员A | GLM | 58s | ✅ |
| 🔍 研究员B | GLM | 62s | ✅ |
| 📊 分析师  | Kimi | 45s | ✅ |
串行需要约 165s → 并行实际 62s,节省 **62%** ⚡

❌ Wrong — agent order:

子Agent1的结果...
子Agent2的结果...
子Agent3的结果...  ← 读者要自己拼图,体验差

✅ Right — content logic:

## 核心结论
1. 最重要发现A(来自多个Agent综合)
2. 最重要发现B
...

## 详细分析:[主题1]
...(整合所有相关Agent的内容)

## 详细分析:[主题2]
...

## 下一步建议
...

The main agent rewrites everything in its own words. Sub-agent outputs are raw material, not the final answer.

After results — deliver the report (channel-aware)

Always save to file first. Then deliver based on the current channel.

python
# Step 1: Always save to file first
write("/workspace/projects/{topic-slug}/report.md", content)

Then choose delivery method by channel:

ChannelDelivery method
feishu + has feishu-all-operations skillCreate Feishu doc → send link (best UX)
feishu + no Feishu skillmessage(filePath=..., filename="report.md") — send as attachment
Discord / Telegram / Slackmessage(message=...) — Markdown renders normally
Other / unknownSave file + tell the user the path

Why this matters: Feishu chat does NOT render Markdown. Sending raw Markdown text shows ##, |---| symbols. Always use attachment or doc link on Feishu.

python
# Feishu (no Feishu doc skill): send as attachment
message(action="send", filePath="/workspace/projects/{topic-slug}/report.md", filename="report.md")

# Discord/Telegram: send markdown directly
message(action="send", message=report_content)

End with one line:

需要调整某个方向,或推送到飞书文档吗?

Rules:

  • ✅ Always save .md file first — regardless of channel
  • ✅ Check current channel before deciding how to send
  • ❌ Never paste >300 words of Markdown text on Feishu — it won't render
  • ❌ Never just say "报告已保存至 /path/xxx" — user can't open server paths
  • ❌ Never ask "要不要我帮你整理成文档?" — just do it
Sequential vs parallel — analyst must wait for researchers

Critical: Agents spawned in the same round run in parallel and share NO context with each other.

❌ Wrong: spawn researcher-A + researcher-B + analyst all at once
          → analyst has no data, returns empty

✅ Right: 
  Round 1: spawn researcher-A + researcher-B (parallel, independent)
  Wait for both to return...
  Round 2: main agent consolidates research results
           → then either: main agent writes analysis itself
           → or: spawn analyst with research results injected as context

Best practice: Any agent that depends on another agent's output should be spawned in a later round, after collecting the dependency.


🤖 Model Selection Guide — Which Model for Which Role

Always pick the right model for each agent. State the model explicitly in the announcement.

Model roster
模型别名特点适合角色
glmGLM便宜、速度快、中文好搜索、简单调研、状态检查
kimiKimi长上下文(128k)、代码强深度分析、代码、长文整合
geminiGemini创意好、多模态写作、文案、图像理解
sonnetClaude Sonnet均衡、工具调用稳复杂推理、规划、审核
opusClaude Opus最强推理极复杂分析、架构设计
Role → Model mapping (default)
角色默认模型原因
🔍 研究员 / ResearcherGLM轻量搜索,够用且便宜
📊 分析师 / AnalystKimi长上下文,处理大量资料
✍️ 写作者 / WriterGemini创意写作效果最好
💻 程序员 / CoderKimi长上下文代码理解
🔎 审核员 / ReviewerGLM简单判断,不需重炮
📋 规划师 / PlannerSonnet结构化规划能力强
🧐 批评者 / CriticSonnet逻辑严谨,挑战假设
When to override defaults
  • 任务很简单 → 降级到 GLM(省成本)
  • 需要最高质量 → 升级到 Opus
  • 用户明确指定模型 → 照用户说的来
  • 多模型对比场景 → 每个 Agent 用不同模型,在公告里说明
Always announce the model

In the pre-spawn announcement, every agent line must include the model:

✅ 这样:🔍 研究员A(GLM)— 调研 LangChain
❌ 这样:🔍 研究员A — 调研 LangChain

Step 0: Always plan first (dynamic agent count)

Never hardcode how many agents to spawn. The right number depends on the task complexity. Always start with a planning step:

1. Analyze the task → identify subtopics / dimensions
2. Decide: how many agents? which roles? which mode?
3. Spawn accordingly (could be 2, could be 10)
4. Consolidate results

Example planning output:

Task: "Research the top AI agent frameworks"
→ Plan: 5 researchers (one per framework) + 1 analyst for comparison
→ Mode: Orchestrator (needs web search)
→ Spawn: 5 parallel sub-agents

The number of agents should match the task, not a template.


Three modes — auto-routed by intent

You don't need to say which mode. Just describe the task. The skill reads these two signals:

  1. Need web search / real-time info? → use sessions_spawn (has tools)
  2. Want multiple draft versions to compare? → spawn parallel writers
User says anything
        ↓
  Wants multiple versions / drafts / angles?
        YES ──→ Also needs web search?
        │              YES → 🔀 Hybrid Mode   (search first, then N drafts)
        │              NO  → 🔄 Pipeline Mode (N drafts in parallel, pure text)
        │
        NO  ──→ Needs web search / file ops?
                       YES → 🎯 Orchestrator Mode (sessions_spawn, parallel)
                       NO  → 🔄 Pipeline Mode     (pure text, faster)

Trigger signals the skill listens for:

SignalExamplesMode triggered
Multi-draft intent"几个版本", "多个角度", "让我挑", "各自写", "different styles"Pipeline or Hybrid
Search intent"搜索", "最新", "调研", "联网", "search", "latest"Orchestrator or Hybrid
Both"搜索后给我几版报告", "research then write multiple drafts"Hybrid
Neither"翻译", "分析", "写作", plain text tasksPipeline

You can also check with the router directly:

bash
python scripts/router.py mode "搜索竞品资料,帮我写3个版本的分析"
# → 🔀 HYBRID
python scripts/router.py mode "调研LangChain并写一份报告"
# → 🎯 ORCHESTRATOR
python scripts/router.py mode "用三个角度分析这个方案"
# → 🔄 PIPELINE

Show full SKILL.md (647 more words)Show less

🎯 Orchestrator Mode (with tools, truly parallel)

Sub-agents launched via sessions_spawn. Each has full OpenClaw tools: web search, file read/write, code execution.

⚡ How parallelism works: Call multiple sessions_spawn in the same tool-call round — OpenClaw executes them simultaneously. All sub-agents run at once; the main agent collects all results when they finish.

Same round → parallel execution:

sessions_spawn(task="Search LangChain...") ──┐
sessions_spawn(task="Search CrewAI...")    ──┤→ all run simultaneously
sessions_spawn(task="Search AutoGen...")   ──┘
sessions_spawn(task="Search LangGraph...") ─┘

↓  (all finish, main agent receives all 4 results)

Main agent consolidates → writes full report

Sequential = spawn one, wait for result, then spawn next. Use this only when a later task depends on an earlier result (e.g. write report AFTER research is done).

How to spawn — always include role, model hint, and what to return:

python
# Parallel research: spawn all 4 in the same round → they run simultaneously
sessions_spawn({
    "task": "[CONTEXT] Comparing AI agent frameworks for a tech team report.\n\n[YOUR TASK] Search LangChain: architecture, pros/cons, GitHub stars, latest version. Return 5 bullet points ≤100 words each. Do NOT write a full report.",
    "label": "🔍 researcher-langchain [model: default]"
})
sessions_spawn({
    "task": "[CONTEXT] Same report.\n\n[YOUR TASK] Search CrewAI: architecture, pros/cons, GitHub stars, latest version. Return 5 bullet points ≤100 words each.",
    "label": "🔍 researcher-crewai [model: default]"
})
sessions_spawn({
    "task": "[CONTEXT] Same report.\n\n[YOUR TASK] Search AutoGen: architecture, pros/cons, GitHub stars, latest version. Return 5 bullet points ≤100 words each.",
    "label": "🔍 researcher-autogen [model: default]"
})
sessions_spawn({
    "task": "[CONTEXT] Same report.\n\n[YOUR TASK] Search LangGraph: architecture, pros/cons, GitHub stars, latest version. Return 5 bullet points ≤100 words each.",
    "label": "🔍 researcher-langgraph [model: default]"
})
# All 4 run in parallel → when all return, main agent consolidates and writes report

Mixed: parallel then sequential (most common pattern):

python
# Phase 1: parallel research (spawn all at once)
sessions_spawn({"task": "[CONTEXT] ...\n\n[TASK] Search LangChain. 5 bullets ≤100 words.", "label": "🔍 researcher-langchain"})
sessions_spawn({"task": "[CONTEXT] ...\n\n[TASK] Search CrewAI. 5 bullets ≤100 words.", "label": "🔍 researcher-crewai"})
sessions_spawn({"task": "[CONTEXT] ...\n\n[TASK] Search AutoGen. 5 bullets ≤100 words.", "label": "🔍 researcher-autogen"})

# Phase 2: after all 3 return → main agent writes report (sequential, depends on research)
# (main agent does this directly, no need to spawn a writer)

Key rules:

  • ✅ Same round = parallel: spawn multiple agents at once for independent tasks
  • ✅ Sequential: spawn one, wait for result, then spawn next — only when tasks depend on each other
  • ✅ Sub-agents return summaries only (≤100 words per point)
  • ✅ Main agent writes the full report (avoids token limit failures)
  • ✅ Label each agent clearly: role + what model it's using
  • ❌ Don't ask a sub-agent to both search AND write a long report

🔄 Pipeline Mode (pure text, any task)

Runs agents via Python CLI. No web search, but works for any pure-text task: writing, analysis, translation, multi-model comparison, brainstorming, code generation.

bash
cd ~/.openclaw/skills/claw-multi-agent

# Parallel: multiple agents tackle different angles simultaneously
python run.py --mode parallel \
  --agents "fast:🔍 researcher:summarize the pros of microservice architecture" \
           "fast:🔍 researcher:summarize the cons of microservice architecture" \
           "fast:🔍 researcher:list real-world companies using microservices and outcomes" \
           "smart:📊 analyst:compare microservices vs monolith for a 10-person startup" \
  --aggregation synthesize

# Sequential: chain agents, each builds on the previous output
python run.py --mode sequential \
  --agents "fast:📋 planner:break down how to build a REST API in Python" \
           "smart:💻 coder:implement the API based on the plan above" \
           "fast:🔎 reviewer:review the code for bugs and security issues" \
  --aggregation last

# Auto-route: router classifies task and picks tiers automatically
python run.py --auto-route --task "write a technical blog post about GRPO vs PPO"

# Dry-run: preview the plan without executing
python run.py --dry-run \
  --agents "fast:researcher:research X" "smart:writer:write report"

Pipeline mode works great for:

  • Multi-angle analysis (spawn one agent per dimension)
  • Multi-model comparison (same task, different models)
  • Code pipeline (plan → code → review)
  • Batch writing (translate/summarize N documents in parallel)

🔀 Hybrid Mode (search + multi-draft)

Best of both worlds: sub-agents search the web (with tools), then multiple writers generate parallel drafts from the research.

When it kicks in: user wants both real-time research AND multiple versions to compare.

Phase 1 (Orchestrator — with tools, parallel):
  sessions_spawn(search topic A) ──┐
  sessions_spawn(search topic B) ──┤ → all run simultaneously
  sessions_spawn(search topic C) ──┘
  ↓ research summaries collected

Phase 2 (Pipeline — pure text, parallel):
  openclaw agent (writer style 1) ──┐
  openclaw agent (writer style 2) ──┤ → all run simultaneously
  openclaw agent (writer style 3) ──┘
  ↓ 3 draft versions returned

Main agent: compare drafts → pick best or synthesize

CLI usage:

bash
# Auto: router detects hybrid intent and runs both phases
python run.py --mode hybrid --task "调研主流AI框架,给我3个不同风格的对比报告" --num-drafts 3

# Auto-mode: let router decide the mode automatically
python run.py --auto-mode --task "搜索竞品资料后写几个版本的分析"

In conversation (sessions_spawn approach):

python
# Phase 1: parallel research (spawn all at once)
sessions_spawn({"task": "[CONTEXT] ...\n\n[TASK] Search LangChain. 5 bullets.", "label": "🔍 research-langchain"})
sessions_spawn({"task": "[CONTEXT] ...\n\n[TASK] Search CrewAI. 5 bullets.", "label": "🔍 research-crewai"})
sessions_spawn({"task": "[CONTEXT] ...\n\n[TASK] Search AutoGen. 5 bullets.", "label": "🔍 research-autogen"})

# After all 3 return → Phase 2: main agent writes 3 draft versions itself
# (or spawn 3 pipeline agents with research as context)

Smart Router

Built-in task classifier. Auto-picks the right tier based on keywords:

bash
python scripts/router.py classify "write a Python web scraper"
# → Tier: CODE  (routes to smart model)

python scripts/router.py classify "research the latest LLM papers"
# → Tier: RESEARCH  (routes to fast model)

python scripts/router.py spawn --json --multi "research X and write a report"
# → splits into 2 tasks: RESEARCH + CREATIVE
TierModelUsed for
FASTdefault (light)Simple queries, status, translation, search
CODEdefault (smart)Programming, debugging, implementation
RESEARCHdefault (light)Research, search, compare, survey
CREATIVEdefault (smart)Writing, articles, documentation
REASONINGdefault (best)Architecture, logic, complex analysis

contextSharing: Give sub-agents background

Sub-agents start as fresh sessions — they don't know your goal. Add a [CONTEXT] block.

Pattern 1: recent (recommended — works for 95% of cases)

[CONTEXT] User is comparing AI agent frameworks for a team report. Audience: engineers.

[YOUR TASK] Search LangChain pros and cons. Return 5 bullet points ≤100 words each.

Pattern 2: summary (sequential tasks — pass prior results forward)

[PRIOR FINDINGS]
- LangChain: richest ecosystem, steep curve
- CrewAI: clean role separation...

[YOUR TASK] Based on above, search AutoGen. Return 3 unique points not covered above.

Pattern 3: full (complex background — let agent read a file)

[CONTEXT FILE] Read /workspace/research/context.md for full background.

[YOUR TASK] Search latest Test-Time Compute Scaling advances. Return 3 summaries.

Reuse context across parallel agents:

python
BG = "Researching RL post-training for ML engineers. Topics: GRPO/DAPO/PPO, veRL."

sessions_spawn({"task": f"[CONTEXT] {BG}\n\n[TASK] Search GRPO vs PPO benchmarks. 5 bullets ≤100 words.", "label": "🔍 researcher-grpo [model: default]"})
sessions_spawn({"task": f"[CONTEXT] {BG}\n\n[TASK] Search DAPO design. 5 bullets ≤100 words.", "label": "🔍 researcher-dapo [model: default]"})
sessions_spawn({"task": f"[CONTEXT] {BG}\n\n[TASK] Search veRL architecture. 5 bullets ≤100 words.", "label": "🔍 researcher-verl [model: default]"})

Execution summary — always output this

After every multi-agent run, print a standard card:

## 📊 Execution Summary

Mode: 🎯 Orchestrator Mode (sessions_spawn, with tools)

| Agent | Role | Model | Time | Status |
|-------|------|-------|------|--------|
| 🔍 researcher-langchain | Researcher | default | 22s | ✅ |
| 🔍 researcher-crewai    | Researcher | default | 19s | ✅ |
| 🔍 researcher-autogen   | Researcher | default | 24s | ✅ |
| 🔍 researcher-langgraph | Researcher | default | 21s | ✅ |
| ✍️ main (consolidate)   | Writer     | default | 38s | ✅ |

Agents spawned: 4  |  Parallel time: ~24s  |  Serial equivalent: ~86s  |  Saved: ~62s (72%)

Always include:

  • Mode (Orchestrator / Pipeline + Sequential/Parallel)
  • Each agent's role emoji + name + model used
  • Actual elapsed time per agent
  • Total parallel time vs serial equivalent

Preset roles

RoleEmojiBest for
researcher🔍Web search, info gathering
writer✍️Reports, documentation, articles
coder💻Code writing, debugging, implementation
analyst📊Data analysis, comparison, statistics
reviewer🔎Code / content review, QA
planner📋Task planning, decomposition
critic🧐Risk analysis, devil's advocate

⚠️ Gotchas

Gotcha 0: Reading files before announcing (most common mistake)

Investigating context before sending the activation announcement causes long silence and risks losing the announcement entirely due to context compression.

  • ❌ Receive task → read operators.py → read README → announce → spawn
  • ✅ Receive task → announce immediately (can say "analyzing task...") → read files → spawn
Gotcha 1: Sub-agent output token limit

Sub-agents have a ~4096 token output cap. Exceeded → tool args truncated → file writes silently fail.

  • ❌ "search AND write a 2000-word report"
  • ✅ Sub-agent returns summaries; main agent writes the report
Gotcha 2: Orchestrator Mode has no tools in Pipeline Mode

python run.py processes have no web_search, exec, etc.

  • ❌ Pipeline mode: "search the latest news on X"
  • ✅ Anything needing real web access → Orchestrator Mode
Gotcha 3: Parallel agents can't depend on each other

Agents spawned in the same round run simultaneously.

  • ❌ Agent-2: "based on Agent-1's results..."
  • ✅ Parallel = independent; sequential = chained
Gotcha 4: Don't hardcode agent count

Match agents to the task, not to a template.

  • ❌ Always spawn exactly 3 agents
  • ✅ Plan first, then decide: simple task → 2 agents, complex → 8+ agents

Pipeline mode quick reference

bash
python run.py
  --mode parallel|sequential
  --agents "tier_or_model:🎭role:task description"   # repeatable, any number
  --aggregation synthesize|compare|concatenate|last
  --timeout 300
  --dry-run          # preview without executing
  --auto-route       # router picks tiers automatically
  --list-models      # show current model config
AggregationEffect
synthesizeMain agent summarizes all outputs (default)
compareSide-by-side of each agent's output
concatenateOutputs joined in order
lastFinal agent's output only (sequential)

© LeoYeAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 10 other files (scripts) in skills/claw-multi-agent of LeoYeAI/openclaw-master-skills.

  • SKILL.md
  • README.md
  • _meta.json
  • multiagent_engine.py
  • orchestrator.py
  • package.json
  • run.py
  • scripts/router.py
  • templates/code_review.json
  • templates/compare_models.json
  • templates/research.json

Open the folder on GitHubat commit e5199b5

Compare with similar skills

Claw Multi Agent 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.

Claw Multi Agent compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Claw Multi Agent this skillLeoYeAI/openclaw-master-skills2.2k—~5.5kAutomated safety check: PassMIT
Kimi Code DelegationCherryHQ/cherry-studio53k—~504Automated safety check: PassAGPL-3.0
Research Trackersundial-org/awesome-openclaw-skills663—~1kAutomated safety check: PassNone
Advanced Swarm Orchestrationruvnet/agentic-flow8185 repos~5.9kAutomated safety check: PassNone
Workflow OrchestrationAnastasiyaW/codex-claude-code-config154—~3.8kAutomated safety check: PassMIT
ULW Deep Researchcode-yeongyu/oh-my-openagent70k—~14kAutomated safety check: PassCustom licence

Similar skills

  • Kimi Code Delegation

    CherryHQ/cherry-studio

    Delegates one bounded repository task to Kimi Code in non-interactive prompt mode and reads back the final result from its JSON event stream.

    53k GitHub stars~504 tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Research Tracker

    sundial-org/awesome-openclaw-skills

    Manage autonomous AI research agents with SQLite-based state tracking.

    663 GitHub stars~1k tokensUpdated 7 mo ago
    Agent WorkflowsAuto-check passed
  • Advanced Swarm Orchestration

    ruvnet/agentic-flow

    Patterns for running multi-agent swarms on research, development and testing work, with four topologies and a four-phase research swarm built on claude-flow MCP tools.

    818 GitHub starsUsed in 5 repos~5.9k tokens
    Agent WorkflowsAuto-check passed
  • Workflow Orchestration

    AnastasiyaW/codex-claude-code-config

    Написание и запуск Claude Code dynamic workflows (JS-оркестратор субагентов).

    154 GitHub stars~3.8k tokensUpdated today
    Business, Finance & HRAuto-check passed
  • ULW Deep Research

    code-yeongyu/oh-my-openagent

    Runs an exhaustive, team-based research session that stands up cooperating agents, debates findings and delivers a report where every claim has a citation or proof.

    70k GitHub stars~14k tokensUpdated today
    Research & ScienceAuto-check passed
  • Deep Research

    XiaomiMiMo/MiMo-Code

    Runs a multi-source investigation with parallel sub-agents and built-in web tools, then writes one cited report. Meant for open-ended topics, not quick lookups.

    14k GitHub stars~1.2k tokensUpdated yesterday
    Research & ScienceAuto-check passed

More from LeoYeAI/openclaw-master-skills

All 1,235 skills in this repo
  • DevOps Pipeline Management

    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.

    2.2k GitHub stars~4.2k tokensUpdated 2 mo ago
    Auto-check: notes
  • Feishu Document Collaboration

    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.

    2.2k GitHub stars~2k tokensUpdated 2 mo ago
    Auto-check passed
  • Files Memory System

    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.

    2.2k GitHub stars~3.8k tokensUpdated 2 mo ago
    Auto-check passed
  • GEO-Claw AI Visibility Agent

    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.

    2.2k GitHub stars~4.7k tokensUpdated 2 mo ago
    Auto-check passed
  • Google Workspace CLI

    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.

    2.2k GitHub stars~2.6k tokensUpdated 2 mo ago
    Auto-check: notes
  • HealthFit Health Advisors

    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.

    2.2k GitHub stars~4.4k tokensUpdated 2 mo ago
    Auto-check passed

Works with

Categories

Questions about Claw Multi Agent

What does Claw Multi Agent do?

Multi-agent parallel orchestration for OpenClaw. An agent skill from LeoYeAI/openclaw-master-skills. Claw Multi Agent is an agent skill from LeoYeAI/openclaw-master-skills. Multi-agent parallel orchestration for OpenClaw.

When should I use Claw Multi Agent?

Claw Multi Agent fits situations like: words: multi-agent; parallel agents; spawn multiple agents; parallel research.

How do I install Claw Multi Agent in Claude Code?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill claw-multi-agent -a claude-code`. Or copy the skill folder (skills/claw-multi-agent in LeoYeAI/openclaw-master-skills) into .claude/skills/claw-multi-agent in your project. Claude Code loads it when a task matches its description.

How do I install Claw Multi Agent in Codex?

Run `npx skills add LeoYeAI/openclaw-master-skills --skill claw-multi-agent -a codex`. Or copy the skill folder (skills/claw-multi-agent in LeoYeAI/openclaw-master-skills) into .agents/skills/claw-multi-agent in your project. Codex loads it when a task matches its description.

Can I use Claw Multi Agent in Cursor, Gemini CLI or GitHub Copilot?

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 claw-multi-agent -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/claw-multi-agent, .gemini/skills/claw-multi-agent, .github/skills/claw-multi-agent and .opencode/skills/claw-multi-agent in your project.

What does Claw Multi Agent need to run?

Going by SKILL.md and its folder, Claw Multi Agent needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Claw Multi Agent access the network?

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.

Is Claw Multi Agent safe to install?

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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Claw Multi Agent use?

Claw Multi Agent is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Claw Multi Agent use?

About 5.5k tokens (SKILL.md is roughly 22k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Claw Multi Agent?

Skills that share tags, products or a category with Claw Multi Agent: Kimi Code Delegation (CherryHQ/cherry-studio, 53k stars), Research Tracker (sundial-org/awesome-openclaw-skills, 663 stars), Advanced Swarm Orchestration (ruvnet/agentic-flow, 818 stars) and Workflow Orchestration (AnastasiyaW/codex-claude-code-config, 154 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Claw Multi Agent?

LeoYeAI (a GitHub user) maintains it in LeoYeAI/openclaw-master-skills, which has 2,161 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.