Content
57%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 body is a dense, command-rich reference: runnable invocations, precise exit-code semantics, and a thorough configuration table make it highly actionable. Its weaknesses are structural: no sequenced workflow with explicit validation checkpoints, over-compressed prose with inline version-sensitive detail, and one-level references (CHECKS.md, README.md) that are broken in the shipped bundle.
Suggestions
Ship CHECKS.md and README.md in the bundle (or fix the links) so the "Full check shapes and scopes" and "Setup" pointers resolve locally instead of dead-ending.
Add a short ordered workflow section (install hooks -> `install-git-hooks --check` -> configure keys -> run `commit-guards all --staged` -> interpret exit codes) with explicit validation checkpoints.
Move the jq 1.6/1.7 version handling and malformed-inventory status enumeration out of SKILL.md into CHECKS.md or DEVELOPMENT.md, and split the long pre-push scoping sentences into a small table of scope sources.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body has no padding and assumes git competence, but it carries trimmable minutiae: inline time-sensitive version detail ("jq 1.6 finds a NUL in every string and changes the filter's `20` and `21` statuses under `-e`") and long multi-clause sentences ("the scope is a best-effort local one taken from this repository's refs for the remote, which record a past fetch") that could be tightened or deferred. | 3 / 5 |
Actionability | The opening bash block is copy-paste runnable, exit codes are defined ("`0` clean, `1` violations, `2` usage, configuration, or collection error"), and the configuration table gives concrete keys, defaults, and formats ("`pattern<TAB>reason` per line"); the pre-push scoping rules, however, are dense descriptive prose rather than commands or worked examples. | 4 / 5 |
Workflow Clarity | Content is organized by topic (checks, hooks, configuration) rather than a sequenced install-to-verify workflow, and while validation vocabulary exists (exit codes, `install-git-hooks --check`), checkpoints are implicit; a blocking batch system without an explicit ordered flow with validation steps caps at this level. | 3 / 5 |
Progressive Disclosure | References are clearly signaled but dead-end locally: "Full check shapes and scopes: [CHECKS.md](CHECKS.md)" and "[README.md § Setup](README.md#setup)" link to files absent from the bundle (only scripts/ ships; DEVELOPMENT.md appears only via external GitHub URLs), while deep operational minutiae such as jq-version inventory handling is inlined in SKILL.md rather than deferred. | 3 / 5 |
Total | 13 / 20 Passed |