Content
86%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.
An exemplary content structure: a lean overview that pushes all detail to real, one-level-deep, well-signaled reference files, with a sequenced workflow and an explicit validation step. The remaining improvements are small — an explicit feedback loop for failed validation and a concrete command for identifying changed files.
Suggestions
Add a feedback loop for the Validate step (e.g., 'If a suggested fix is not actionable, revise it before posting the review') so validation failures have explicit recovery guidance.
Make step 1 concrete (e.g., 'gh pr diff --name-only' or 'git diff --name-only main') instead of relying solely on the error-handling fallback for how to identify changed files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 44-line body is lean throughout — a one-line purpose statement, five trigger bullets, a six-step workflow that links out to references instead of inlining them, and a two-row error table. It assumes Claude's competence (no concept explanations, no padded prose) and every token earns its place, matching the top anchor. Not a 4 because there is no over-explanation to trim; the only repetition (the References list) serves navigation. | 5 / 5 |
Actionability | Each workflow step names its concrete artifact and source ("Run each category from the review checklist", "Assign severity per the severity guide", "Write the review per the output format"), and the error table gives a concrete fallback ("Estimate at ~4 chars per token") — mostly executable guidance with minor gaps, matching anchor 4. Not a 5 because step 1 ("Identify all changed skill files") gives no command or method, deferring entirely to the fallback error row; not a 3 because nothing is pseudocode or abstract. | 4 / 5 |
Workflow Clarity | The six steps are clearly sequenced and end with an explicit validation checkpoint ("Validate — Verify suggested fixes are actionable with accurate file/line references"), and the error-handling table covers two failure modes — matching anchor 4's 'clear sequence with most checkpoints present; minor validation gaps'. Not a 5 because there is no feedback loop for what to do when step 6 validation fails (the error table only covers collection/token-counting failures); not a 3 because a validation checkpoint is explicitly present. | 4 / 5 |
Progressive Disclosure | The body is a pure overview: all detail lives in four references, every one of which exists in references/, is linked with explicit markdown links in both the workflow and a References section, and is exactly one level deep (no nested pointers). All bundle files are linked and none are orphaned, matching the 'clear overview with well-signaled one-level-deep references' anchor. Not a 4 because there are no organization gaps — each reference maps to a distinct workflow step. | 5 / 5 |
Total | 18 / 20 Passed |