CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/agent-teams/skills/team-composition-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-organized, actionable decision guide with concrete tables, presets, and configuration examples, and no significant verbosity problems. Its main weakness is progressive disclosure: two substantial reference files exist in the bundle but receive no navigation from SKILL.md, which instead inlines condensed versions of their content.

Suggestions

Link the existing bundle files from the relevant sections, e.g. under Preset Team Compositions add 'See [references/preset-teams.md](references/preset-teams.md) for task templates and member variations' and under Agent Type Selection add a pointer to references/agent-type-selection.md for the decision matrix and common mistakes.

Trim the duplicated advice: state 'Never assign implementation tasks to read-only agents' once (in Agent Type Selection) and drop the repeated coordination-overhead guidance from either the rule of thumb, custom guideline 5, or the troubleshooting entry.

Add a short end-to-end example of composing one team (a spawn snippet with subagent_type and an initial task prompt) so the decision path from complexity assessment to spawning is fully executable from the body.

DimensionReasoningScore

Conciseness

Largely efficient tables and terse prose, but 'Never assign implementation tasks to read-only agents' is repeated in both Agent Type Selection and Troubleshooting, and the coordination-overhead advice appears three times (rule of thumb, custom guideline 5, and troubleshooting), so minor trimming is possible.

4 / 5

Actionability

Concrete guidance throughout: exact sizing table, exact agent-type strings per preset, and a copy-paste settings.json snippet for teammateMode. Not a 5 because example spawn prompts and task templates exist only in the unlinked reference files, leaving minor gaps in the body itself.

4 / 5

Workflow Clarity

As a decision guide with no destructive or batch operations, no validation checkpoints are required, and the material is well organized into a coherent decision path (complexity, size, preset, agent types, display mode). However, that path is never laid out as an ordered procedure, so minor gaps remain versus the explicit-sequence anchor.

4 / 5

Progressive Disclosure

The body inlines preset-team and agent-type detail while references/preset-teams.md (265 lines with task templates and variations) and references/agent-type-selection.md (84 lines with a decision matrix) exist but are never linked or mentioned anywhere in the body, leaving the references unsignaled and their content partly duplicated inline.

3 / 5

Total

15

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states what the skill does and provides explicit, varied trigger conditions covering sizing, preset selection, agent type choice, display modes, and custom compositions. Minor deductions for the 'optimal' over-claim, a few missing natural synonyms, and slight overlap risk with sibling team-related skills.

DimensionReasoningScore

Specificity

Names the domain plus several concrete actions ('sizing heuristics, preset configurations, and agent type selection', 'configuring display modes (tmux, iTerm2, in-process)'), but 'optimal' is a mild over-claim and 'preset configurations' is generic phrasing, leaving minor gaps versus the comprehensive 5 anchor.

4 / 5

Completeness

Explicitly 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 concrete trigger conditions, matching the top anchor.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('how many agents to spawn', 'review team versus a feature team versus a debug team', 'tmux, iTerm2', 'migration or security audit'), but misses common variations such as 'teammates', 'multi-agent', and the feature name 'Agent Teams'.

4 / 5

Distinctiveness Conflict Risk

Clear niche (team sizing, composition, and display-mode configuration) with distinct triggers like 'how many agents to spawn', but it can overlap with the sibling parallel-feature-development skill, which also triggers on team-spawning language.

4 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 2 suspicious

Warning

Total

14

/

16

Passed

Repository

wshobson/agents

Path

plugins/agent-teams/skills/team-composition-patterns/SKILL.md

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.