Menu

Individual skill

swarm-pattern

0upvotes

Orchestrate lightweight multi-agent workflows where agents hand off to each other with routines and context variables.

skills/swarm-pattern/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 8, 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)
56
Repository last updated
Oct 10, 2026
License
MIT

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

## Overview

The swarm pattern structures multi-agent work as handoffs between small,
single-purpose agents. Each agent has a name, instructions, a narrow toolset, and
the ability to transfer control to another agent — returning which agent should
act next, optionally with updated context variables. There's no central
orchestrator reasoning over everything; the workflow emerges from the handoff
graph. A triage agent routes to a specialist, the specialist does its job and
hands back or onward.

The power is in the constraints: agents are routines, not general intelligences.
Each does one thing with the minimal tools it needs, which makes behavior
predictable, debuggable, and cheap. The pattern fits workflows that are naturally
staged — intake → specialist → review — better than it fits open-ended
Back to top