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 operational skill body: executable commands throughout, a clear sequenced workflow with self-check and validation built into the build step, and well-signaled one-level references verified against the actual bundle. The only room for improvement is trimming the in-body descriptions of page UI and adding an explicit error-recovery loop for failed validation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and operational throughout — commands, paths, and specific behaviors with no padding and no explanation of concepts Claude already knows — but it is long, and passages describing page UI in detail (the overview's four parts, the recommendation card anatomy) could be trimmed or delegated to references. Efficient with minor instances that could be tightened, so anchor 4 rather than 5. | 4 / 5 |
Actionability | The Usage block gives copy-paste-ready commands for every invocation mode (commit, range, PR, --since, --serve, --stdin, -o/--title/--event), the workflow names exact scripts ("node $S/pr-media.cjs --pr <N>", "node $S/review-guides.cjs") and exact files to write, and specific gotchas state what to do instead — fully executable coverage of the common cases. | 5 / 5 |
Workflow Clarity | The six-step workflow (Gather → Load preferences → Read the change → Build → Open → Report) is clearly sequenced, with checkpoints present: the build runs a self-check and guide validation, the report step surfaces the self-check and CI lines, and failures are handled ("Skip captures when the app can't run, and say so in the report"). It stops short of anchor 5 because there is no explicit fix-and-retry feedback loop when validation fails. | 4 / 5 |
Progressive Disclosure | The body is a genuine overview: each topic (gathering, overview format, recommendations, reading guide, page behavior, developing) is a sentence or two that clearly signals a one-level-deep reference, all eight referenced files exist in references/ and cross-link only laterally (no nested reference chains), and a Files section inventories every bundle script and reference. | 5 / 5 |
Total | 18 / 20 Passed |