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 written, well-structured instruction skill: concrete commands, explicit safety rules, a sensible dry-run checkpoint, and project-specific edge-case knowledge (the squash-merge ancestry caveat) that genuinely adds value. The main gap is external: the script the whole procedure depends on is not part of the reviewed bundle, and the diary/report outputs lack worked examples.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes competence: it never explains what git worktrees or fast-forwarding are, and every section carries project-specific information Claude could not infer (hard rules, the two-test merged predicate, env vars and where to persist them). The few rationale sentences (e.g., the merge-reconciliation tax) justify the constraints rather than pad, matching the 'every token earns its place' anchor. | 5 / 5 |
Actionability | The procedure gives copy-paste-ready commands ("sh scripts/worktree-cleanup.sh --dry-run", "sh scripts/worktree-cleanup.sh") plus concrete instructions for the diary edit and report contents. It stops short of the top anchor because the diary row edit and the report step are described but not exemplified (no sample row or summary block format), and the referenced script is not present in the reviewed bundle to confirm executability. | 4 / 5 |
Workflow Clarity | The sequence is explicit with validation checkpoints appropriate to a destructive batch operation: dry-run preview shown to the operator first, an error-recovery path ("If the script reports the root as dirty, surface that to the operator; don't stash or commit"), the script's own skipping of dirty/unmerged worktrees, and a closing report of base before → after, removed, and kept-and-why. This satisfies the feedback/checkpoint expectations the rubric reserves for the top anchor. | 5 / 5 |
Progressive Disclosure | Sections are well organized and the git mechanics are appropriately split into a one-level-deep, clearly signaled reference ("The git mechanics live in `scripts/worktree-cleanup.sh`") with no nested reference chains. It does not reach 5 because the referenced script (and any references/ or scripts/ files) is absent from the bundle as provided, so the primary external reference cannot be verified, and cross-references point to project files outside the skill bundle. | 4 / 5 |
Total | 18 / 20 Passed |