Content
22%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 effectively empty — a single heading that restates the skill name. It contains no actionable guidance, no workflow, and nothing that would let Claude (or a user) understand what reviewing a change actually involves, making the skill unusable as written.
Suggestions
Add concrete instructions for the core task: how to obtain the change (e.g., git diff of the working tree or a PR number), what to look for, and how to report findings.
If the review targets code changes, include a short sequenced workflow with an explicit validation step (e.g., re-run checks on the diff, verify each finding against the actual changed lines before reporting).
Either fill the body with the actual review procedure or, if detail lives elsewhere, add the missing reference files and link them clearly from the body.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body ("# Review change") contains no padded explanations or over-explanation, but its only content — a heading that duplicates the name field — provides no instructional value; genuine token efficiency requires lean content that actually conveys guidance. It is not 4-5 because the tokens present do not earn their place, and not 1-2 because there is no verbosity to trim. | 3 / 5 |
Actionability | The body provides no concrete code, commands, or steps — it does not even describe the task, let alone instruct how to perform it. This matches (and undershoots) the anchor 1 case of only describing rather than instructing. | 1 / 5 |
Workflow Clarity | Steps are entirely missing — no sequence, no checkpoints, no validation — matching anchor 1 ("Steps missing or incoherent; no sequence"). The simple-skill exception does not apply because "Review change" is not an unambiguous single action: what kind of change and how to review it are undefined. | 1 / 5 |
Progressive Disclosure | The body has no structural defects — no monolithic text, no buried or nested references, and no bundle files are misused — but it also has no organized sections or content to navigate. The simple-skill 5 exception requires well-organized sections, which a bare heading with zero body content is not; it is not a 2 because nothing inlined here belongs in a separate file. | 3 / 5 |
Total | 8 / 20 Passed |