Content
33%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The SKILL.md body is an empty stub — a single heading with no guidance, commands, examples, workflow, or supporting files. While it wastes zero tokens, it provides zero actionable content, so the skill cannot function as written. The what/when must be authored, not inferred.
Suggestions
Add the actual review procedure as concrete, executable guidance — e.g. the commands to obtain the diff ("git diff", "gh pr diff <n>"), what to inspect, and how to report findings.
Add a sequenced workflow with a validation checkpoint (e.g. re-run the diff after fixes, confirm findings against the actual code), which is essential since reviewing changes is a multi-step, error-prone process.
Either write enough body content to make the skill self-contained or split detail into a references/ file and link it clearly from the body — currently there is nothing to navigate to.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is a single heading ("# Review change") with zero padding and no explanation of concepts Claude already knows — nothing to trim. It matches anchor 5 ("Lean and efficient; every token earns its place") on the token-waste axis, though only because there is almost no content. | 5 / 5 |
Actionability | The body contains no code, no commands, no steps, and no instructions of any kind — only a title. This matches anchor 1 ("Entirely vague or abstract; no concrete code or commands; only describes rather than instructs") in its most extreme form: it doesn't even describe the task. | 1 / 5 |
Workflow Clarity | No steps, no sequence, and no validation are present — the body is empty of any process guidance, matching anchor 1 ("Steps missing or incoherent; no sequence; no validation for risky operations"). The simple-skill exception does not apply because even the single action is unstated, not merely unambiguous. | 1 / 5 |
Progressive Disclosure | There is minimal structure: one bare heading, no sections, no overview, and no referenced files (the references/, scripts/, assets/ directories do not exist). This matches anchor 2 ("Minimal structure") rather than anchor 1, since there is no monolithic wall of text or nested-reference chain to navigate. | 2 / 5 |
Total | 9 / 20 Passed |