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.
A tightly engineered procedural skill: executable commands with variables defined, explicit validation and recovery for every risky operation (identity checks, duplicate-block check, failure branches), and dense repo-specific rationale rather than padding. Weaknesses are stylistic verbosity and a monolithic structure with no progressive-disclosure layer.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Nearly all content is repo-specific constraint knowledge Claude cannot infer ("a tracker number on a card is a disclosure", "Stage the one card, never the directory") rather than explanations of known concepts, but the ornate prose style ("That reading is the point of the exercise, and this skill throws it away") and sections restating the description could be tightened — efficient with minor trimmable passages, not the lean-every-token-earns-its-place of anchor 5. | 4 / 5 |
Actionability | Fully executable, copy-paste-ready bash throughout: the pre-flight probe block, the BRANCH/SLUG/PR/BASE setup, both `bun run --cwd tools/pr-metrics card` invocations, the commit and `gh pr edit --body-file` sequence, and specific recovery flags (`--pr <n>`, `--resolve-issue`) for each failure mode. | 5 / 5 |
Workflow Clarity | Clear pre-flight → Step 1 → Step 2 → Finish sequence with explicit validation checkpoints and feedback loops: "Check the issue the card names... run both commands again with `--issue <n>` added", the duplicate-block grep (with the reason tag-matching fails), and the "When a step here cannot run" error-recovery branches. The commit/push/body-edit operations are all guarded, so no validation cap applies. | 5 / 5 |
Progressive Disclosure | Well-organized sections (pre-flight, two steps, finish) with appropriate deferral of edge cases to `retro` Step 1 ("a tracker-only branch, a branch closing several issues and a reused branch name do instead"); however it is a single ~220-line file with no reference split — the five rules block is dense enough that it could live one level deep — so it stops short of the well-signaled reference structure of anchor 5. | 4 / 5 |
Total | 18 / 20 Passed |