Essaim — Development skill for Claude Code
Spawn N coordinated Claude Code agents — orchestrator + behavior catalog.
How to install Essaim
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open swoofer/essaim and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Essaim does
Spawn N coordinated Claude Code agents — orchestrator + behavior catalog. Pairs with @swoofer/promptweave + mcp-coordinator.
Alternatives in Development
- n8n Validation Expert — Fix n8n validation errors with error catalog 3.6k ★
- 05 Coordinator System Prompt — Coordinator System Prompt 2.3k ★
- Obsidian Init — Scan your vault and generate a _CLAUDE.md operating manual, index.md catalog, and log.md 277 ★
README
essaim
**Spawn N coordinated Claude Code agents on your repo. Pick a preset, the orchestrator does the rest.**
[](LICENSE) [](https://www.npmjs.com/package/essaim) [](https://github.com/swoofer/essaim/actions)
[Problem](#the-problem) · [How it works](#how-it-works) · [Quickstart](#quickstart) · [Architecture](#architecture) · [BCE](#bce--behavior-composition-engine) · [Phases](#work-stealing-phases) · [Effort](#effort-profiles) · [CLI](#cli) · [Templates](#portable-templates) · [Quota](#anthropic-quota-pre-flight) · [Config](#configuration) · [Related](#related-projects)
The Problem
When multiple developers each use an AI coding agent in parallel on the same repo, things break:
- Regressions — Agent A rewrites a module that Agent B was depending on
- Duplicated work — Two agents implement the same feature from different directions
- Architectural drift — Agents make local decisions that conflict with each other's designs
- Wasted reconciliation time — Developers spend hours untangling what the agents did
Each agent works in isolation. None of them know what the others are doing.
essaim fixes this by giving agents a **shared nervous system** — they announce intentions before coding, conflicts are detected before a single line is written, and agents see each other's actions in real-time to agree on an approach.
How It Works
Developer A Developer B
| |
| announce_work | announce_work
v v
+--------------+ +--------------+
| Agent α | <-- MQTT -->| Agent β |
| (essaim) | push-based | (essaim) |
+--------------+ +--------------+
| MCP HTT
Related Skills
Validate Team
Spawn coordinated validation agents across platforms with evidence handoff
OmniHarness
Pixel-office viewer + harness pattern for running Claude Code as a coordinated team of subagents. Orchestrator
Claude Code Skills Collection
8 Claude Code Agent Skills from ChinaSiro/claude-code-sourcemap — adversarial-verification, smart-memory-guard
Bug Health Check
Execute the bug-health-inline skill for inline orchestration. You ARE the orchestrator. Do not spawn a separat
Cleanup Health Check
Execute the cleanup-health-inline skill for inline orchestration. You ARE the orchestrator. Do not spawn a sep
Cmux Did Spawn
Orient yourself as orchestrator over a full-stack team that was just scripted into its own cmux window. Reads
Related Agents
QA MCP Server Validation
QA subagent for mcp server validation. Use during code review passes coordinated by /dev-tools:qa-orchestrator
Claude Code MCP Behavior Analysis
Results from 15 tests against a minimal Cord MCP server. Tested: Claude Code 2.1.37, 2026-02-18. Note: These t
Agy Runner
Drives one delegated task through the agy MCP server and reports back, so the orchestrator is not blocked whil