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

82%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 content is a tight, well-sequenced instruction workflow with one clearly signaled external reference and no padding. Its main weakness is the absence of explicit validation checkpoints confirming reviewer coverage before parallelization.

Suggestions

Add an explicit validation step, e.g. 'Before briefing, verify every affected domain has an owner and no reviewer's files overlap.'

Surface the routing reference as a dedicated pointer (e.g. 'See docs/development/review-routing.md for the domain map') to improve navigation.

Include a short feedback loop for when a verdict is ambiguous, e.g. re-brief the missing domain and re-review.

Dimension	Reasoning	Score
Conciseness	The body is a lean nine-line workflow that assumes Claude's competence and adds no concept explanations or padding; every token earns its place.	5 / 5
Actionability	Steps are concrete and reference a specific path (`docs/development/review-routing.md`) and artifacts (diff, controlling plan, primary source files), but how to map paths to domains is delegated to the referenced doc rather than spelled out.	4 / 5
Workflow Clarity	A clear numbered sequence runs from reading the diff to synthesizing verdicts, with an implicit checkpoint in step 5 ('where their files do not overlap') and a guard note, though explicit validation of coverage before briefing is missing.	4 / 5
Progressive Disclosure	The body is a concise overview that signals a single one-level-deep reference (`docs/development/review-routing.md`), with routing detail appropriately externalized; navigation could be more prominently signaled.	4 / 5
	Total	17 / 20 Passed

Description

58%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.

The description is specific and names a clear niche, but it lacks an explicit 'when to use' trigger clause, which caps completeness and limits trigger-term coverage. Adding a 'Use when...' sentence with natural synonyms would raise the score.

Suggestions

Append a 'Use when...' clause naming natural triggers, e.g. 'Use when reviewing a Fallow change or selecting reviewers for a pull request.'

Add common synonyms users would say, such as 'code review', 'PR review', or 'review routing'.

Clarify the 'when' alongside the 'what' so both are explicitly answered in one sentence.

Dimension	Reasoning	Score
Specificity	The single action 'Select the minimum complete reviewer team' is enriched with four concrete selection criteria (touched paths, contracts, integrations, risk), placing it noticeably above the midpoint but short of multiple distinct actions.	4 / 5
Completeness	It clearly states what the skill does but provides no 'Use when...' trigger clause, so per the rubric completeness is capped at 3.	3 / 5
Trigger Term Quality	Relevant terms like 'reviewer team', 'change', and 'risk' appear, but common user variations such as 'code review', 'pull request', or 'PR review' are missing.	3 / 5
Distinctiveness Conflict Risk	The 'Fallow change' qualifier gives it a clear niche with minimal conflict risk, though it could still overlap with generic code-review skills.	4 / 5
	Total	14 / 20 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: 7e1e075

Reviewed: 3 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.