CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review

Review one pull request for real bugs, regressions, and convention violations. Enumerate candidate issues across the whole diff, verify each against the code, then return structured line-anchored findings and a verdict. Read-only on GitHub; the orchestrator posts the review.

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exceptionally actionable, well-sequenced review methodology with concrete tool examples, an exact output contract, and built-in self-correction loops. Its weaknesses are minor: a few redundant passages that could be tightened, and near-monolithic placement of all policy detail in the single file rather than offloading some to references.

DimensionReasoningScore

Conciseness

The body is dense with task-specific policy and assumes Claude's competence (no explanations of what PRs or code review are), e.g. 'Breadth first, depth second. The two most common ways to fail are...'. Minor trimming is possible — points like 'A flawless implementation of the wrong thing is still the wrong thing' restate the preceding sentence, and the Tests and Comments bullets run long. Not a 5 because of these few redundant passages.

4 / 5

Actionability

Fully executable guidance: concrete tool calls like 'async () => state.readFile({ path: "<diffPath from your inputs>" })' and 'state.searchFiles({ pattern: ... })', an exact output schema with field-level rules ('path (repo-relative ... not prefixed with /repo/)', 'side (RIGHT for additions)'), and explicit severity/verdict calibration. Specific examples cover the common cases, including the re-review branch.

5 / 5

Workflow Clarity

The method is a clearly sequenced six-step process (frame, judge the approach, enumerate, verify, go deep, prioritize) with explicit validation checkpoints and feedback loops: 'Self-correct: drop candidates that turn out fine; do not report hypotheses you couldn't confirm.' The candidate categories and verdict calibration rules act as checklists. Not a 4 because verification and error-recovery loops are explicit throughout, not merely present.

5 / 5

Progressive Disclosure

The file is well-sectioned (## Documentation changes, ## Your only tool, ## Inputs, ## Method, ## Output) with a clearly signaled one-level reference: 'load the writing-emdash-docs skill before reviewing those files.' No bundle files exist and there is no nested-referencing problem. Not a 5 because at ~100 lines some self-contained policy blocks (e.g. the Changesets subsection) could live in a separate reference file, and the single external-skill reference is the only offloading of detail.

4 / 5

Total

18

/

20

Passed

Description

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

A specific, action-rich description that clearly conveys what the skill does and its output shape, weakened only by the complete absence of when-to-use trigger guidance and slightly thin keyword variations. It is easily distinguished from unrelated skills but modestly overlaps the generic code-review category.

Suggestions

Add an explicit trigger clause, e.g. 'Use when asked to review, critique, or check a pull request or PR diff for bugs and convention violations.'

Include common synonyms such as 'code review' and 'PR' among the trigger terms to broaden natural matching.

DimensionReasoningScore

Specificity

The description lists multiple concrete, comprehensive actions: 'Enumerate candidate issues across the whole diff, verify each against the code, then return structured line-anchored findings and a verdict,' plus scoping ('one pull request', 'real bugs, regressions, and convention violations'). Not a 4 because coverage of the task's actions is complete rather than leaving minor gaps.

5 / 5

Completeness

The 'what' is explicit and detailed, but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not a 4 because the 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Natural terms users would say are present: 'review', 'pull request', 'bugs', 'regressions', 'findings', 'verdict'. Not a 5 because common variations like 'code review' or 'PR' are missing; not a 3 since keyword coverage goes beyond a couple of generic terms.

4 / 5

Distinctiveness Conflict Risk

Distinctive elements ('one pull request', 'line-anchored findings', 'a verdict', 'Read-only on GitHub; the orchestrator posts the review') separate it from generic skills, with only minor overlap risk against general code-review skills. Not a 5 because 'review ... for real bugs' shares triggers with any code-review skill.

4 / 5

Total

16

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

emdash-cms/emdash

Path

infra/flue-review/.flue/skills/review/SKILL.md

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.