Agent skill

Multi Agent Orchestration

by mizchi in mizchi/skills

A skill your agent uses when deciding whether to spawn subagents, choosing sequential vs fan-out vs supervisor vs debate vs dynamic DAG, designing a coding-agent workflow with write-scope isolation…

No licenceAuto-check passedAgent Workflows

Install Multi Agent Orchestration

skills CLI
$ npx skills add mizchi/skills --skill multi-agent-orchestration -a claude-code

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

GitHub CLI
$ gh skill install mizchi/skills multi-agent-orchestration --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/mizchi/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/multi-agent-orchestration .claude/skills/multi-agent-orchestration && 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
multi-agent-orchestration
GitHub stars
359
Token cost
~1.9k tokens
SKILL.md length
950 words
Files
5 (incl. references)
Skills in repo
69
Repo updated
First seen
Licence
None found

At a glance

A skill your agent uses when deciding whether to spawn subagents, choosing sequential vs fan-out vs supervisor vs debate vs dynamic DAG, designing a coding-agent workflow with write-scope isolation…

  • Works in 4 steps: Independent parts that can run in… → Agents would have different information,… → Intermediate artifacts checkable… → …
  • Deciding whether to spawn subagents
  • SKILL.md covers When to use, Gate, Topology and Communication, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Multi Agent Orchestration is an agent skill from mizchi/skills. Use when deciding whether to spawn subagents, choosing sequential vs fan-out vs supervisor vs debate vs dynamic DAG, designing a coding-agent workflow with write-scope isolation, or when extra agents may waste tokens without independent evidence. Trigger on multi-agent, orchestration, fan-out, worktree, blackboard, verifier, AgentTask, or "should I parallelize this".

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `README.md`, `SKILL-ja.md` and `references/flue.md`).

It sits in Agent Workflows, covering Multi-agent orchestration and Git worktrees. The repository describes itself as: Agent skills by mizchi, distributed via APM.

When your agent uses it

  • Deciding whether to spawn subagents
  • Choosing sequential vs fan-out vs supervisor vs debate vs dynamic DAG
  • Designing a coding-agent workflow with write-scope isolation
  • Extra agents may waste tokens without independent evidence

Example prompts

  • “should I parallelize this”
  • “/multi-agent-orchestration”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Independent parts that can run in parallel — including parts that become independent after a short frozen contract artifact (types, HTTP…
  2. Agents would have different information, models, tools, or permissions
  3. Intermediate artifacts checkable mechanically (tests, schema, provenance, oracle, lint). For research, schema-valid provenance is enough…
  4. Expected gain of another agent beats its token / latency / error-propagation cost

What it can do on your machine

Read from SKILL.md and the folder at commit 62f5808. 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

    No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).

    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

Multi Agent Orchestration loads about 1.9k tokens when it runs, and up to ~4.7k if it reads all its reference files. Until then it costs about 99 tokens; SKILL.md has 950 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~99
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.7k

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); files beside SKILL.md are not scanned.

SKILL.md

Without a licence we can't republish the file, so here is its outline and opening line. It has 950 words (~1,862 tokens).

“Do not add agents. Add independently verifiable work: a dependency graph, parallel only on independent nodes, integrate through shared state and a verifier.”

— opening of SKILL.md by mizchi
name
multi-agent-orchestration

Read the full SKILL.md on GitHub

Files

SKILL.md and 4 other files (references) in multi-agent-orchestration of mizchi/skills.

  • SKILL.md
  • README.md
  • SKILL-ja.md
  • references/flue.md
  • references/sources.md

Open the folder on GitHubat commit 62f5808

Compare with similar skills

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

Multi Agent Orchestration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Multi Agent Orchestration this skillmizchi/skills359—~1.9kAutomated safety check: PassNone
Orca CLIstablyai/orca88k2 repos~593Automated safety check: PassMIT
ClawTeam Multi-Agent Swarmwin4r/ClawTeam-OpenClaw1.5k1 repos~2.9kAutomated safety check: PassMIT
Agent of Empires Session Manageragent-of-empires/agent-of-empires3.3k—~2.5kAutomated safety check: PassMIT
Agent of Empires Session Manageragent-of-empires/agent-of-empires3.3k—~2.1kAutomated safety check: PassMIT
Clawteamwin4r/ClawTeam-OpenClaw1.5k—~3.1kAutomated safety check: PassMIT

Similar skills

  • Orca CLI

    stablyai/orca

    Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser…

    88k GitHub starsUsed in 2 repos~593 tokens
    Agent WorkflowsAuto-check passed
  • ClawTeam Multi-Agent Swarm

    win4r/ClawTeam-OpenClaw

    Launches a swarm of specialist Hermes agents in git-worktree-isolated tmux windows with a kanban board and file-based inboxes, using built-in templates like hedge-fund and code-review.

    1.5k GitHub starsUsed in 1 repo~2.9k tokens
    Agent WorkflowsAuto-check passed
  • Agent of Empires Session Manager

    agent-of-empires/agent-of-empires

    Launches, monitors and organizes AI coding agent sessions such as Claude Code or Codex inside tmux, tracking status, capturing output and managing git worktrees for parallel branches.

    3.3k GitHub stars~2.5k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Agent of Empires Session Manager

    agent-of-empires/agent-of-empires

    Starts, monitors and organizes coding agent sessions that run in tmux through the aoe command, including groups, profiles and worktree-based parallel work.

    3.3k GitHub stars~2.1k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Clawteam

    win4r/ClawTeam-OpenClaw

    Multi-agent swarm orchestration. An agent skill from win4r/ClawTeam-OpenClaw.

    1.5k GitHub stars~3.1k tokensUpdated 3 mo ago
    Agent WorkflowsAuto-check passed
  • Huashu Agent Swarm

    alchaincyf/huashu-skills

    多Agent蜂群并行协作,纯git自组织,适合大型项目开发。当用户提到"蜂群模式"、"多agent"、"并行开发"、"agent swarm"时使用。

    1.7k GitHub stars~576 tokensUpdated 16 days ago
    Agent WorkflowsAuto-check passed

More from mizchi/skills

All 69 skills in this repo
  • Publish Agent Skill

    mizchi/skills

    Package, publish, verify and update an agent skill through a Claude Code plugin marketplace, APM or the npx skills CLI.

    359 GitHub stars~1.7k tokensUpdated 7 days ago
    Auto-check passed
  • AI Index

    mizchi/skills

    Method and tooling for measuring how AI-generated a piece of prose reads, in Japanese or English.

    359 GitHub stars~3.6k tokensUpdated 7 days ago
    Auto-check passed
  • Cloudflare Deploy

    mizchi/skills

    Deploy applications and infrastructure to Cloudflare with the cf CLI and typed cloudflare.config.ts.

    359 GitHub stars~2.9k tokensUpdated 7 days ago
    Auto-check: notes
  • Review Image

    mizchi/skills

    Review screenshots or other images with OpenRouter vision models via bundled Deno scripts.

    359 GitHub stars~1.3k tokensUpdated 7 days ago
    Auto-check passed
  • Post-generation safety checks for sqlc-gen-moonbit + Cloudflare D1.

    359 GitHub stars~995 tokensUpdated 7 days ago
    Auto-check passed
  • Apm Usage

    mizchi/skills

    Reference for APM (Agent Package Manager) — apm.yml syntax, install / uninstall / update commands, target detection, lockfile workflow.

    359 GitHub stars~1.9k tokensUpdated 7 days ago
    Auto-check passed

Categories

Questions about Multi Agent Orchestration

What does Multi Agent Orchestration do?

A skill your agent uses when deciding whether to spawn subagents, choosing sequential vs fan-out vs supervisor vs debate vs dynamic DAG, designing a coding-agent workflow with write-scope isolation…. Multi Agent Orchestration is an agent skill from mizchi/skills. Use when deciding whether to spawn subagents, choosing sequential vs fan-out vs supervisor vs debate vs dynamic DAG, designing a coding-agent workflow with write-scope isolation, or when extra agents may waste tokens without independent evidence.

When should I use Multi Agent Orchestration?

Multi Agent Orchestration fits situations like: deciding whether to spawn subagents; choosing sequential vs fan-out vs supervisor vs debate vs dynamic DAG; designing a coding-agent workflow with write-scope isolation; extra agents may waste tokens without independent evidence.

How do I install Multi Agent Orchestration in Claude Code?

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

How do I install Multi Agent Orchestration in Codex?

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

Can I use Multi Agent Orchestration 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 mizchi/skills --skill multi-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/multi-agent-orchestration, .gemini/skills/multi-agent-orchestration, .github/skills/multi-agent-orchestration and .opencode/skills/multi-agent-orchestration in your project.

What does Multi Agent Orchestration need to run?

SKILL.md names no scripts, command-line tools or credentials: Multi Agent Orchestration is instructions for the agent only.

Does Multi Agent Orchestration 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 Multi Agent Orchestration 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. Review the folder before installing.

What licence does Multi Agent Orchestration use?

No licence was found for Multi Agent Orchestration or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Multi Agent Orchestration use?

About 1.9k tokens (SKILL.md is roughly 7.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.9k tokens, read only when the agent opens those files.

What are the alternatives to Multi Agent Orchestration?

Skills that share tags, products or a category with Multi Agent Orchestration: Orca CLI (stablyai/orca, 88k stars), ClawTeam Multi-Agent Swarm (win4r/ClawTeam-OpenClaw, 1.5k stars), Agent of Empires Session Manager (agent-of-empires/agent-of-empires, 3.3k stars) and Agent of Empires Session Manager (agent-of-empires/agent-of-empires, 3.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Multi Agent Orchestration?

mizchi (a GitHub user) maintains it in mizchi/skills, which has 359 GitHub stars. The repository holds 69 skills in this directory. The repository was last updated on October 2, 2026.

Source: mizchi/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.