team-composition-patterns
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.
82
78%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/agent-teams/skills/team-composition-patterns/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly articulates specific capabilities (team sizing, preset configurations, agent type selection, display mode configuration) and provides comprehensive trigger guidance with five distinct use-case scenarios. The description is well-structured, uses third-person voice, and includes enough domain-specific terminology to be both discoverable and distinctive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: designing agent team compositions, sizing heuristics, preset configurations, agent type selection, configuring display modes, and building custom team compositions. Very detailed and actionable. | 3 / 3 |
Completeness | Clearly answers both 'what' (design optimal agent team compositions with sizing heuristics, preset configurations, and agent type selection) and 'when' with an explicit 'Use this skill when...' clause listing five distinct trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes many natural trigger terms users would say: 'how many agents to spawn', 'review team', 'feature team', 'debug team', 'subagent_type', 'tmux', 'iTerm2', 'CI', 'migration', 'security audit', 'team composition'. Good coverage of both general and specific terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused on agent team composition, subagent types, and multi-agent orchestration. The specific mentions of tmux/iTerm2 display modes, subagent_type, and team presets (review/feature/debug) make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a solid reference guide for team composition patterns with good use of tables and clear preset definitions. Its main weaknesses are the lack of executable examples showing actual Agent tool invocations for spawning teams, and the absence of validation/verification steps in the workflow. The content would benefit from being more actionable with concrete usage examples rather than purely descriptive tables.
Suggestions
Add a concrete example of an Agent tool invocation showing how to actually spawn a team (e.g., a complete example of spawning a review team with specific prompts and subagent_type values)
Add a brief workflow with validation checkpoints: e.g., 1) Assess complexity → 2) Select preset or custom composition → 3) Verify agent types match roles → 4) Spawn and confirm teammates are active → 5) Define boundaries
Remove the 'When to Use This Skill' section since it duplicates the frontmatter description and wastes tokens
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is generally well-structured with tables that convey information efficiently, but includes some unnecessary sections like 'When to Use This Skill' (which duplicates the description) and the troubleshooting section contains explanations that are somewhat verbose for Claude's level of understanding. The 'Custom Team Guidelines' section states fairly obvious coordination principles. | 2 / 3 |
Actionability | The skill provides concrete team compositions, agent type mappings, and a specific JSON config example, which is good. However, it lacks executable examples of actually spawning a team — there are no concrete Agent tool invocations showing how to compose a team in practice. The guidance is more descriptive/tabular than copy-paste executable. | 2 / 3 |
Workflow Clarity | The custom team guidelines provide a numbered list of considerations, but there's no clear step-by-step workflow for actually composing and launching a team. There are no validation checkpoints — e.g., verifying teammates spawned correctly, checking that file ownership boundaries don't overlap, or confirming all dimensions are covered before proceeding. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear sections, uses tables effectively for reference material, and includes well-signaled one-level-deep references to related skills (parallel-feature-development, team-communication-protocols). The structure supports quick scanning and discovery. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- wshobson/agents
- Commit
27a7ed9
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.