CtrlK
BlogDocsLog inGet started
Tessl Logo

review-validation

Validate review findings from specialist agents by reading the actual repo file content and checking each finding for accuracy, applicability, and false positives.

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.flue/.agents/skills/review-validation/SKILL.md
SKILL.md
Quality
Evals
Security

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 body is a tight, highly actionable instruction-only skill with a clear sequenced validation procedure and concrete tool calls plus a complete result schema. Its only soft spots are minor conciseness trims and the absence of an explicit error-recovery feedback loop, which keep workflow clarity and progressive disclosure at 4 rather than 5.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence — it never explains what a PR or finding is — with only minor instances that could be trimmed (e.g. the repeated 'Do not write prose output / Do not narrate your work' directives), placing it just below the fully lean level 5.

4 / 5

Actionability

It names exact tools (read_repo_file, search_repo, submit_review_validation), gives per-step concrete checks, and provides a copy-paste-ready JSON result shape with worked examples — fully executable guidance for an instruction-only skill.

5 / 5

Workflow Clarity

The five-step Validation procedure is clearly sequenced with explicit checkpoints (rule applicability short-circuit, evidence, suggestion, false-positive/pre-existing checks); it stops short of 5 because there is no error-recovery feedback loop, though for a non-destructive classification task that gap is minor.

4 / 5

Progressive Disclosure

Content is appropriately contained in a single well-sectioned file (Inputs, Security, Tools, Validation procedure, Default behavior, Result shape) with no nested references and no external bundle files needed; it is just over the ~50-line simple-skill threshold, so it sits at 'good structure, minor organization gaps' rather than 5.

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 clearly states concrete capabilities and carves out a distinct niche, but it omits any 'when to use' / trigger guidance, which limits its completeness and trigger-term quality. Adding an explicit 'Use when...' clause with natural user phrases would lift the two capped dimensions.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when validating review findings from specialist agents, checking for false positives, or verifying finding accuracy.'

Include natural user-facing trigger terms and synonyms such as 'review findings', 'false positives', 'finding accuracy', and 'verify review results' alongside the technical language.

Consider mentioning the supported finding streams ('code', 'style', 'conventions') in the description to sharpen distinctiveness.

DimensionReasoningScore

Specificity

Names several concrete actions — 'reading the actual repo file content', 'checking each finding for accuracy, applicability, and false positives' — with only minor coverage gaps, fitting the 'lists several specific actions' anchor rather than the fully comprehensive level 5.

4 / 5

Completeness

It gives a clear 'what' (validate findings by reading repo content and checking accuracy/applicability/false positives) but provides no 'when' / trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Terms like 'review findings', 'specialist agents', and 'false positives' are relevant but skew technical and omit common natural synonyms; there is no explicit 'Use when...' trigger phrase, so it sits at 'some relevant keywords but missing common variations' rather than the fuller level 4.

3 / 5

Distinctiveness Conflict Risk

The niche — suppressing false positives in findings produced by specialist review agents — is mostly distinct from general review skills, with only minor overlap risk, matching the 'mostly distinct; minor overlap risk' anchor.

4 / 5

Total

14

/

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
cloudflare/cloudflare-docs
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.