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.
A tight, well-structured instruction-only skill: concrete budgets, an explicit slicing order, and a disciplined handoff format with no wasted tokens. The gaps are illustrative — one worked example slice packet and one concrete verification command would make the guidance fully copy-paste ready, and an explicit failure/retry path would complete the workflow.
Suggestions
Add one filled-in example slice packet (goal, owned files, out of scope, risk level, an actual verification command with its expected pass condition, rollback plan) to make the template concrete.
Specify what "project gate checks" means or give an example (e.g. 'the repo's CI test/lint target') so verification is executable rather than inferred.
Add an explicit failure path, e.g. 'If a slice exceeds budget or verification fails, re-split it before proceeding', to close the feedback loop.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and entirely prescriptive — budgets, ordered steps, template fields, rules, and output format with zero padding and no explanation of concepts Claude already knows (what a PR is, why small reviews help beyond one goal line). Level 4 would require minor over-explanation to trim, which is absent. | 5 / 5 |
Actionability | Concrete, executable guidance dominates: specific budgets ("<= 400 changed lines", "<= 10 changed files", "1-4 commits"), a slicing order, and a packet template with defined fields. It falls short of level 5 because verification guidance stays generic ("Run project gate checks" with no example command) and no filled-in example slice packet is provided. | 4 / 5 |
Workflow Clarity | The Slicing Order gives a clear 4-step sequence, and Verification Discipline plus the packet's risk level and rollback plan supply most checkpoints. It does not reach level 5 because there is no explicit feedback loop (what to do when a slice's verification fails or a budget is exceeded) and no complete checklist. | 4 / 5 |
Progressive Disclosure | The body is under 50 lines with no external references needed and clean, well-labeled sections in a logical order (goal, budgets, order, template, rules, verification, handoff). Per the simple-skill guideline this earns the top anchor; the body is short enough that no file split is warranted. | 5 / 5 |
Total | 18 / 20 Passed |