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 highly actionable, well-sequenced operational skill body with strong validation gates on the risky apply path. Its main improvement lever is moving long-tail operational detail (large-project tuning, apply mechanics, deferred features) into reference files and trimming duplicated safety statements.
Suggestions
Move the large-project performance notes (pool-cap explanation, --ef-search/--merge-timeout guidance, SQL prototype pointer) into a reference file and keep a two-line summary with the pointer in SKILL.md.
Split Phase-2a apply mechanics and the deferred-features list into a separate reference, leaving the overview to state that apply is dry-run-by-default and explicitly gated.
State the no-delete safety rule once in Rules and reference it from the apply section instead of repeating it.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Dense and project-specific throughout — pool caps, phase limitations, learning-type routing — with essentially no filler; the body assumes Claude's competence. Not 5: the large-projects performance paragraph is a digression that could be tightened, and "never deletes the source archival row" is stated twice. | 4 / 5 |
Actionability | Copy-paste-ready commands for the detector, dry-run, and execute paths with all flags documented, plus concrete judgment criteria (read the destination layer, check for prior capture, route ambiguity to the user). Not 4: the commands and decision guidance are complete, with no gaps to fill. | 5 / 5 |
Workflow Clarity | Four clearly sequenced steps with explicit validation checkpoints for a database-touching workflow: dry-run first (always), verify resolved paths, confirm with the user, and a pg_dump backup that aborts the apply on failure, plus idempotent re-apply. Not 4: validation is explicit at every risky step rather than having minor gaps, so the destructive/batch cap does not apply. | 5 / 5 |
Progressive Disclosure | Clear section structure (Usage, Process, Rules) with one-level references to the detector and apply scripts, but all ~115 lines live in SKILL.md. Not 5: operational detail such as the large-project tuning notes and Phase-2a apply mechanics could be split into a reference file to keep the overview lean. | 4 / 5 |
Total | 18 / 20 Passed |