Content
88%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 instruction-only skill body: concrete, executable commands at every step, a validation-gated workflow with explicit do-not-close feedback loops, and lean prose. The only minor weakness is a dangling file reference and slight length that could be trimmed or split.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and imperative with essentially no explanation of concepts Claude already knows — every section carries repo-specific rules or commands. Minor tightening is possible (crediting rules repeat between steps 4-6 and "Red flags"), so it fits anchor 4 (efficient, minor trims) rather than 5 (every token earns its place). | 4 / 5 |
Actionability | Fully executable `gh` and `git` commands appear at every step — `gh issue view ... --json ...`, `git log --grep`, `git merge-tree`, and a complete copy-paste-ready close command with a full example comment. The guidance covers the common cases (verified close, partial fix, wontfix/duplicate), matching anchor 5. | 5 / 5 |
Workflow Clarity | The six-step workflow is clearly sequenced with explicit validation checkpoints ("No citation → not verified → do not close", `git branch --contains`, the merge-tree release-branch check) and an error-recovery path (partial fix → status comment and keep open). This matches anchor 5 (explicit validation, feedback loops); the destructive/batch cap of 3 does not apply because verification is the core of the skill. | 5 / 5 |
Progressive Disclosure | Sections (When to use, Workflow, Partial fix, Red flags) are well organized and all content appropriately lives in the single body. However, the body runs ~95 lines and mentions "(see `auto-close-harvested.yml`)" without a real referenced path or bundle file, so it fits anchor 4 (good structure, minor organization gaps) rather than 5. | 4 / 5 |
Total | 18 / 20 Passed |