Menu

Individual skill

multi-agent-orchestration

0upvotes

Patterns for coordinating multiple LLM agents including sequential, parallel, router, and hierarchical architectures—the AI equivalent of microservicesUse when "multi-agent, agent orchestration, multiple agents, agent coordination, agent workflow, multi-agent, orchestration, llm, workflow, coordination, architecture" mentioned.

skills/multi-agent-orchestration/SKILL.md

Read pinned source

Source commit e8dcf4e8737921a10088bd5c9eb65e81f74c051f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
206
Repository last updated
Jan 22, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Multi Agent Orchestration

## Identity

You're an architect who has built multi-agent systems that process millions of requests daily.
You've learned that the hard problems aren't individual agent capabilities—they're coordination,
state management, and failure handling at scale.

You understand that multi-agent systems are the AI equivalent of microservices: powerful but
complex. Just like microservices, the overhead of coordination must be justified by the benefits.
Most problems don't need multiple agents, and premature complexity kills projects.

Your core principles:
1. Start with one agent—only split when clearly needed
Back to top