CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

reviewer

Load when reviewing a diff, classifying findings, or returning a verdict.

Quality

76%

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 ./.agents/skills/reviewer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 disciplined instruction skill: dense, unpadded prose with concrete executable commands and explicit validation loops. Its main weaknesses are bundle integrity — four referenced files absent and one orphaned — which leaves the end-to-end workflow and the artifact schema unreachable from this file alone.

Suggestions

Ship the missing referenced files (workflows/review.md, workflows/codebase-review.md, workflows/qa-review.md, schemas/review-finding.md) in the bundle, or inline the minimal artifact-schema skeleton so the output contract is self-contained.

Link references/perf-qa.md from SKILL.md (e.g., from the workflows table or QA-review section) so the bundle file is discoverable.

Move the heavily procedural detail of the mutation-stability wait loop (the verbatim sh -c poll snippet, timeout handling, self-matching pgrep caveat) into the mutation-stability script's --help or a dedicated reference, keeping the pairing rationale in the body.

DimensionReasoningScore

Conciseness

Lean and dense with zero padding: no concept explanations Claude already knows, detail delegated to references ("Read references/finding-disposition.md before classifying findings. It owns verification, dispositions, recurrence and the filing bar"), and sibling-skill rules cited rather than restated. Every clause encodes a rule the reviewer cannot derive on its own.

5 / 5

Actionability

Concrete, copy-paste-ready commands throughout: the two review-artifact-check invocations with the fix-until-ok loop, the full mutation-stability flag list, the verbatim sh -c foreground-poll snippet, and the git archive/mktemp/df extraction recipe. It stops short of 5 because the central output format (the findings JSON) is delegated to ./schemas/review-finding.md, which is missing from this bundle, so the artifact shape is not actionable from what is here.

4 / 5

Workflow Clarity

Sequences are explicit with real validation checkpoints and feedback loops: capture starting fields, write the artifact, then "Fix until this prints \"ok\": true"; re-review rounds define suppression and re-report rules; mutation-stability bounds runs by budget and timeout. Not 5 because the top-level diff-to-findings-to-verdict flow lives in workflows/review.md, which is absent from this bundle, leaving the end-to-end sequence only partially visible.

4 / 5

Progressive Disclosure

References are one level deep and clearly signaled, and finding-disposition.md, review-depth, and mutation-stability all exist in the bundle — but four referenced paths are missing (./schemas/review-finding.md and all three workflows/*.md in the workflow table), and references/perf-qa.md is an orphan no path in SKILL.md reaches. Navigation is partly broken, which is more than a minor organization gap.

3 / 5

Total

16

/

20

Passed

Description

67%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 terse, third-person description with an explicit Load-when trigger and three concrete actions. Its main weaknesses are thin capability coverage relative to what the body actually does and missing high-frequency trigger phrases like "code review", "PR", and "QA".

Suggestions

Add the missing high-frequency trigger phrases ("code review", "pull request"/"PR", "QA") to the trigger clause.

Mention the skill's concrete outputs in the description (a findings JSON artifact and a pass/blocker verdict) so the "what" is not merely a restatement of the "when".

Name the additional workflows the body covers (whole-codebase audit, QA-label review) so the description's coverage matches the skill's scope.

DimensionReasoningScore

Specificity

The description lists several concrete actions ("reviewing a diff, classifying findings, or returning a verdict") with no vague filler, but coverage has gaps: codebase audits, QA-label review, and mutation-stability measurement go unmentioned, so it is not comprehensive.

4 / 5

Completeness

Both halves are present: an explicit trigger clause ("Load when reviewing a diff...") and a what expressed as three concrete actions. It falls short of 5 because the what is thin and near-circular with the when — the skill's actual product (a JSON findings artifact per a schema) lives in the separate summary field rather than in the description.

4 / 5

Trigger Term Quality

"reviewing a diff", "findings", and "verdict" are natural terms, but the most common phrasings a user would say are absent: "code review", "pull request"/"PR", "QA", "audit". Relevant keywords exist, yet common variations and synonyms are missing.

3 / 5

Distinctiveness Conflict Risk

Triggers are mostly distinct — finding classification and verdict rendering separate it from generic helpers — but "reviewing a diff" overlaps closely with any generic code-review skill, leaving minor conflict risk.

4 / 5

Total

15

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 3 missing, 16 suspicious

Warning

Total

13

/

16

Passed

Repository

vanillagreencom/kendex

Path

.agents/skills/reviewer/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.