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 instructional skill: lean prose, concrete enumerations of what to delete and what smells to hunt, and a five-step sweep with re-grep and verification checkpoints. The only gaps are minor — a concrete rg invocation and an explicit recovery path when post-removal verification fails.
Suggestions
Show a concrete rg command form in the Sweep (e.g., `rg -l 'featureName|oldAlias' --type-not md` after deletion) so step 4 is copy-paste ready.
Add one recovery line to the Sweep for failed verification, e.g., "If verification fails, check whether you deleted shared code another feature still uses; restore the minimum and re-sweep."
Name what "narrowest honest verification" means concretely (typecheck, test suite subset, or build) so the final step is executable rather than judgmental.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes competence throughout — e.g., "If removal exposes adjacent dead code, keep cutting until the graph is clean" — with zero concept explanations or padding; every line instructs. | 5 / 5 |
Actionability | Guidance is concrete (enumerated surfaces, a literal `throw new Error("Not implemented")` smell example, the named `rg` tool), but there are minor gaps: no copy-paste `rg` command form, and "Run the narrowest honest verification" gives direction without a how. This matches anchor 4 rather than fully executable anchor 5. | 4 / 5 |
Workflow Clarity | The 5-step Sweep has a clear sequence with validation checkpoints (step 4 re-grep for stragglers, step 5 verification for the surviving product), so the destructive-operation cap at 3 does not apply. It falls short of anchor 5 only in lacking an explicit feedback loop for when verification fails — e.g., what to do if the surviving build breaks after deletion. | 4 / 5 |
Progressive Disclosure | This is a short single-purpose skill with no bundle files, and the body is organized into clean sections (Rules, Sweep, Smells, Bias) with no content that belongs in a separate file — per the rubric's simple-skill exception this warrants a 5. | 5 / 5 |
Total | 18 / 20 Passed |