team-assembly

Select the minimum complete reviewer team for a Fallow change based on touched paths, contracts, integrations, and risk.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/team-assembly/SKILL.md

Quality

Content

72%Weight 40%Scale 1-3

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

The body is concise and well-structured as a short, single-purpose skill with an appropriate inline doc reference. It would benefit from a more concrete mapping method and an explicit verification checkpoint before synthesizing verdicts.

Suggestions

Make step 2 concrete: specify how to map paths to domains, e.g. by listing domain categories or pointing to the routing table in review-routing.md.

Add an explicit validation checkpoint before step 6, such as confirming each touched domain has a reviewer assigned before synthesizing verdicts.

Dimension	Reasoning	Score
Conciseness	The body is a lean six-step list with a one-line guardrail and no padding or explanation of concepts Claude already knows, matching the anchor for lean, efficient content where every token earns its place.	3 / 3
Actionability	Steps name concrete artifacts (the diff, `docs/development/review-routing.md`, controlling plan, primary source files), but the core instruction "Map touched paths and behavioral effects to reviewer domains" is abstract about how to perform the mapping, fitting the anchor for some concrete guidance that is incomplete.	2 / 3
Workflow Clarity	A clear numbered 1–6 sequence exists with a conditional guardrail, but there are no explicit validation checkpoints or feedback loops, matching the anchor for steps listed with implicit or missing checkpoints.	2 / 3
Progressive Disclosure	At under 50 lines with a single well-organized numbered list and one inline project-doc reference (`docs/development/review-routing.md`), it fits the simple-skill note allowing a 3 when content is clear and well-organized.	3 / 3
	Total	10 / 12 Passed

Description

67%Weight 40%Scale 1-3

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 is specific and distinctive, clearly conveying what the skill does and the criteria it weighs. Its main weakness is the absence of an explicit "Use when..." trigger, leaving the activation condition implied rather than stated.

Suggestions

Add an explicit trigger clause, e.g. "Use when preparing to review a Fallow change or when the user asks who should review a diff."

Include more natural user-facing phrasings (e.g. "assign reviewers", "who should review this change") alongside the technical terms.

Dimension	Reasoning	Score
Specificity	"Select the minimum complete reviewer team for a Fallow change based on touched paths, contracts, integrations, and risk" names a concrete action plus multiple specific selection criteria, matching the anchor that lists multiple specific concrete actions.	3 / 3
Completeness	It clearly states what the skill does but provides no explicit "Use when..." trigger clause, so the "when" is only implied; per the guidelines a missing trigger clause caps completeness at 2.	2 / 3
Trigger Term Quality	Terms like "reviewer team", "touched paths", "contracts", and "integrations" are relevant but skew technical ("Fallow change") and omit common natural variations a user would say, fitting the anchor for some relevant keywords with missing variations.	2 / 3
Distinctiveness Conflict Risk	The "minimum complete reviewer team for a Fallow change" framing anchored to touched paths, contracts, integrations, and risk is a clear niche unlikely to fire for unrelated skills, matching the distinct-trigger anchor.	3 / 3
	Total	10 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: fallow-rs/fallow
Path: .agents/skills/team-assembly/SKILL.md
Commit: 55944e8

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

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.