Individual skill

multi-agent-architect

Design multi-agent systems — communication topologies, coordination protocols, shared state, consensus, and failure handling across agents. Use when one agent isn't enough and you need several to collaborate reliably.

skills/multi-agent-architect/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Instructions only
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): 53
Repository last updated: Oct 10, 2026
License: MIT

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

agent-skills Repository topic
ai-agents Repository topic
ai-agents-automation Repository topic
ai-skills Repository topic
awesome Repository topic
awesome-list Repository topic
chatgpt Repository topic
claude-skills Repository topic
meta-ai Repository topic
muse-ai Repository topic
design Derived category

Files and excerpt

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

Browse files

SKILL.mdcore · 4,147 bytes

Read excerpt


# Multi-Agent Architect

Multi-agent systems trade simplicity for capability: specialists collaborate on work no single 
agent handles well. The architecture decisions — how agents talk, who decides, what happens when 
one fails — determine whether you get a team or a traffic jam.

## Overview

Design along four dimensions. Topology: how agents connect (star, mesh, hierarchy, pipeline). 
Coordination: how work is assigned and sequenced (central planner, auctions, emergent). 
Communication: what messages agents exchange (structured task objects, not free prose). State: 
what's shared vs. private, and how consistency is maintained. Get these right and the team scales; 
get them wrong and you get deadlock, duplication, and blame diffusion.