CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-teams

Claude Code Agent Teams - default team-based development with strict TDD pipeline enforcement

56

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/agent-teams/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

The body is highly actionable and models excellent workflow clarity with explicit validation gates and feedback loops. Its main weaknesses are conciseness (heavy ASCII art and triple-rendered pipeline) and progressive disclosure (monolithic file with no split-out reference materials).

Suggestions

Render the 10-step pipeline once and reference it from the other sections to remove the triple repetition and trim the ASCII art.

Move the detailed agent roster definitions and per-agent task chain templates into bundle files under references/ and link to them, keeping SKILL.md as an overview.

Tighten the large ASCII boxes into compact tables or short numbered lists to reduce token cost while preserving the ordering information.

DimensionReasoningScore

Conciseness

The body is information-dense and avoids explaining concepts Claude already knows, but it is ~450 lines with the same 10-step pipeline rendered three times (ASCII pipeline box, Feature Agent Workflow steps, and task chain) plus large ASCII art that could be tightened.

2 / 3

Actionability

Concrete executable commands appear throughout (git checkout -b feature/{name}, gh pr create, polyphony spawn "$FEATURE" --type feature), with specific paths, tool lists (TeamCreate, TaskCreate), and numeric gates (>= 80% coverage).

3 / 3

Workflow Clarity

The pipeline is an explicit 10-step sequence with blockedBy task dependencies and validation checkpoints (RED/GREEN verify, code review, security scan) plus feedback loops ('If Critical or High -> fix and re-request'), satisfying the highest anchor.

3 / 3

Progressive Disclosure

Sections are well-organized, but the skill is a single monolithic ~450-line file with no bundle files in references/scripts/assets; detailed content such as agent definitions and the task chain that could live in separate files is inline, and external skill references are noted but not clearly signaled as one-level-deep navigation.

2 / 3

Total

10

/

12

Passed

Description

50%

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

The description identifies the skill's domain (team-based development with TDD enforcement) but reads as a label rather than a trigger-rich capability statement. It lacks an explicit 'Use when' clause and concrete action verbs, so it lands at the mid level across all dimensions.

Suggestions

Rewrite as an action-oriented statement listing concrete behaviors, e.g. 'Spawns coordinated agent teams that run features through a strict TDD pipeline (spec, RED/GREEN tests, review, security, PR).'

Append an explicit trigger clause: 'Use when spawning agent teams for parallel feature development with TDD pipeline enforcement.'

Add natural trigger variations users would say ('agent teams', 'parallel feature development', 'TDD pipeline', 'spawn a team').

DimensionReasoningScore

Specificity

Phrases like 'team-based development' and 'strict TDD pipeline enforcement' name the domain and an action, but the description is a noun phrase that does not enumerate concrete actions (e.g. spawn agents, run reviews, open PRs) rather than a comprehensive list.

2 / 3

Completeness

It answers 'what' (default team-based development with TDD enforcement) but contains no 'Use when...' clause in the description; per the rubric a missing explicit trigger caps completeness at 2 even though a separate when-to-use field exists.

2 / 3

Trigger Term Quality

'Agent Teams', 'team-based development', and 'TDD pipeline' are relevant keywords a user might say, but common variations and explicit trigger phrasing are missing from the description field itself.

2 / 3

Distinctiveness Conflict Risk

'Agent Teams' names a fairly specific niche, but without explicit triggers and given overlap with the superseded team-coordination skill mentioned in the body, it could still overlap with similar coordination skills.

2 / 3

Total

8

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
alinaqi/claude-bootstrap
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.