CtrlK
BlogDocsLog inGet started
Tessl Logo

review

Perform Fallow's comprehensive pre-merge review. Use after implementation or when asked to review a branch, pull request, or diff.

69

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 lean, well-structured review workflow with explicit checkpoints and a feedback loop. Its only gap is that some actionable steps defer specifics to referenced repo documents rather than inlining them.

DimensionReasoningScore

Conciseness

The ~12-line body is lean and efficient, assumes Claude's competence, and contains no padding or explanation of concepts Claude already knows, matching the score-5 'every token earns its place' anchor.

5 / 5

Actionability

Steps reference concrete artifacts (AGENTS.md, docs/development/quality-gates.md, docs/development/review-routing.md) and concrete classification labels (APPROVE, CONCERN, BLOCK), but 'Run the applicable gates' is not fully executable without consulting the referenced doc, fitting the score-4 'mostly executable, minor gaps' anchor.

4 / 5

Workflow Clarity

A clear 7-step sequence with an explicit feedback loop in step 7 ('Fix every block, rerun the blocking reviewer, and update verification'), but the validation/retry detail is slightly less explicit than the score-5 checklist-with-error-recovery anchor.

4 / 5

Progressive Disclosure

Under 50 lines with no external bundle files and a well-organized numbered sequence plus a clear closing guidance paragraph; per the simple-skills rule this qualifies for a 5.

5 / 5

Total

18

/

20

Passed

Description

82%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 concise and complete, explicitly stating both what the skill does and when to use it with concrete trigger phrases. The main weakness is action specificity — it describes one high-level action rather than a list of concrete review activities.

DimensionReasoningScore

Specificity

"Perform Fallow's comprehensive pre-merge review" names the domain and one concrete action, but that action is high-level and not a list of specific concrete actions, matching the score-3 anchor of 'names domain and 1-2 concrete actions' rather than the multi-action score-5 anchor.

3 / 5

Completeness

It explicitly answers both 'what' ("Perform Fallow's comprehensive pre-merge review") and 'when' ("Use after implementation or when asked to review a branch, pull request, or diff") with concrete trigger phrases, matching the score-5 anchor.

5 / 5

Trigger Term Quality

"review a branch, pull request, or diff" plus "after implementation" gives good natural keyword coverage users would actually say, though a few synonyms (e.g. 'PR') are missing, fitting the score-4 anchor.

4 / 5

Distinctiveness Conflict Risk

"Fallow's comprehensive pre-merge review" with branch/pull-request/diff triggers carves a clear niche with minimal conflict risk against other skills, matching the score-5 anchor.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
fallow-rs/fallow
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.