- name
SKILL.md
El archivo de la skill permanece en el repositorio del publicador.
Pega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add wshobson/agents --skill team-composition-patterns -a cursor -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add wshobson/agents --skill team-composition-patterns -a claude-code -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add wshobson/agents --skill team-composition-patterns -a codex -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add wshobson/agents --skill team-composition-patterns -a grok -yEnvía el mensaje copiado en un chat de Grok Bot. El Bot obtiene este SKILL.md de GitHub y lo añade a las skills que comparten todos tus Bots.
Install this skill: https://github.com/wshobson/agents/tree/HEAD/plugins/agent-teams/skills/team-composition-patternsDel publicador
Best practices for composing multi-agent teams, selecting team sizes, choosing agent types, and configuring display modes for Claude Code's Agent Teams feature.
Rule of thumb: Start with the smallest team that covers all required dimensions. Adding teammates increases coordination overhead.
team-reviewerteam-debuggerteam-lead + 2x team-implementerteam-lead + 1x frontend team-implementer + 1x backend team-implementer + 1x test team-implementergeneral-purposeteam-reviewerteam-lead + 2x team-implementer + 1x team-reviewerWhen spawning teammates with the Agent tool, choose subagent_type based on what tools the teammate needs:
Key distinction: Read-only agents (Explore, Plan) cannot modify files. Never assign implementation tasks to read-only agents.
Configure in ~/.claude/settings.json:
{
"teammateMode": "tmux"
}
When building custom teams:
team-lead or have the user coordinate directlyA teammate was spawned as Explore but needs to write files.
Explore and Plan are read-only agents. Change the subagent_type to general-purpose or an appropriate specialized agent type. Never assign implementation tasks to read-only agents.
The team is growing too large and coordination is slowing everything down. Each additional teammate adds communication overhead. Consolidate roles: can one agent cover two dimensions? A 4-person team doing 6 independent tasks is usually better served by 3 agents covering 2 tasks each.
tmux mode is not showing panes.
Ensure tmux is installed and a session is already running before spawning teammates. The in-process mode works without tmux and is suitable for CI or scripted environments.
Two reviewers are flagging the same issues. The review dimensions overlap. Redefine each reviewer's focus area: one on correctness/logic, one on security, one on performance/scalability. Overlapping coverage wastes tokens and produces duplicate findings.
A team-lead is spawning teammates but they are not receiving tasks.
Verify that the lead is using the Agent tool to spawn teammates and passing complete context in the prompt. Teammates start fresh with no prior conversation history — they need all relevant information in their initial prompt.
Design optimal agent team compositions with sizing heuristics, preset configurations, and agent type selection. Use this skill when deciding how many agents to spawn for a task, when choosing between
---name: team-composition-patternsdescription: Design optimal agent team compositions with sizing heuristics, preset configurations, and agent type…---# plugins/agent-teams/skills/team-composition-patterns/SKILL.mdResumen general
Design optimal agent team compositions with sizing heuristics, preset configurations, and agent type selection. Use this skill when deciding how many agents to spawn for a task, when choosing between a review team versus a feature team versus a debug team, when selecting the correct subagent_type for each role to ensure agents have the tools they need, when configuring display modes (tmux, iTerm2, in-process) for a CI or local environment, or when building a custom team composition for a non-standard workflow such as a migration or security audit.
Preguntas frecuentes
Descarga plugins/agent-teams/skills/team-composition-patterns/SKILL.md desde el publicador, o copia la ruta y abre el repositorio. PlugMCP lista la skill y no aloja el archivo.
El publicador lo mantiene en https://github.com/wshobson/agents.
Claude, Cursor, Codex y Grok Build pueden leer un SKILL.md que añadas desde el repositorio del publicador. Grok Bot lo instala cuando envías en un chat el enlace a la carpeta de la skill en GitHub.