agentsop-agent-topology-selection
Cross-framework enhancement overlay for choosing a multi-agent topology BEFORE writing any agent. A binary-question rubric — is single-agent + tools enough? do agents need to know about each other? does the output need one voice? — maps the answer to single-agent / supervisor / swarm / sequential / hierarchical. Activates when a coder agent is tempted to "split the work into roles" or reaches for a multi-agent framework. Encodes the *selection rubric* that the per-framework skills assume but never surface. Search keywords: when to use multi-agent, single vs multi agent, do I need multiple agen
npx skills add agentsope/SkillAlchemy --skill agentsop-agent-topology-selection --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Multi-Agent Topology Selection · SOP (ENHANCE overlay) > Overlay posture: this skill decides *whether and which* topology. It does not > teach the API — descend to `[[crewai]]` or `[[agentsop-langgraph]]` for that. Every > load-bearing claim carries an inline source tag resolving in > `references/R1-source-evidence.md`. --- ## 1. 何时激活 (When to Activate) Activate when **any** of the following fire: - The task description contains "team of agents", "researcher + writer + reviewer", "manager agent", "agents that hand off", "split this into roles", or "multi-agent". - A coder agent is about to instantiate ≥2 agents (CrewAI `Agent(...)` × N, LangGraph supervisor/swarm, OpenAI Swarm handoffs) and has **not yet** justified why a single agent with tools is insufficient. - Someone is choosing between CrewAI `Process.sequential` vs `Process.hierarchical`, or LangGraph supervisor vs swarm vs hierarchical-teams, and wants the *rubric*, not the syntax. - A multi-agent system is over budget on tokens/latency and the question is "can we collapse agents back into one?". Do **not** activate for: a single LLM call, a one-shot RAG query, or a fixed tool-call pipeline with no role separation. Those
- 1. 何时激活 (When to Activate)
- 2. 核心心智模型 (Core Mental Model)
- The selection rubric (three binary questions)
- 3. SOP 工作流 (Selection Protocol)
- Step 1 · Defend the single-agent baseline first
- Step 2 · If splitting, decide static vs dynamic routing
- Step 3 · Coordinator (supervisor) vs peers (swarm)
- Step 4 · Apply the supervisor-default caveat (read this twice)
- Step 5 · Verify the chosen topology can terminate
- Step 6 · Reconsider before scaling agents up
- 4. 操作模型 (Operation Models)
- OP-1 · Defend the single-agent baseline
- OP-2 · Single-vs-multi gate
- OP-3 · Static-order gate (→ sequential)
What does the agentsop-agent-topology-selection skill do?
Cross-framework enhancement overlay for choosing a multi-agent topology BEFORE writing any agent. A binary-question rubric — is single-agent + tools enough? do agents need to know about each other? does the output need one voice? — maps the answer to single-agent / supervisor / swarm / sequential / hierarchical. Activates when a coder agent is tempted to "split the work into roles" or reaches for a multi-agent framework. Encodes the *selection rubric* that the per-framework skills assume but never surface. Search keywords: when to use multi-agent, single vs multi agent, do I need multiple agen
How do I install it?
Run `npx skills add agentsope/SkillAlchemy --skill agentsop-agent-topology-selection --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From agentsope/SkillAlchemy, a repository with 255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.