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.
An exemplary router/index skill: dense, fluff-free, with precise conditional routing, a precedence order, and explicit per-conflict resolution rules. The weaknesses are confined to the Validate step, which names check categories rather than commands and omits an error-recovery loop.
Suggestions
Make the Validate step concrete: name the lint/type/test commands per tree (or point to the package.json scripts that define them) instead of "the smallest relevant lint, type, and test checks".
Add an explicit failure-handling loop in the Validate step — run checks, fix failures, re-run before reporting — so error recovery is prescribed rather than implied.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence: it never explains what React, Tailwind, or shadcn/ui are, and every section carries non-obvious routing or precedence information. Even the Notes section earns its tokens by defusing a real hazard (inert frontmatter on bundled reference files), so nothing reads as padding. | 5 / 5 |
Actionability | Routing guidance is fully concrete — exact file paths with load conditions, a numbered precedence order, per-overlap resolutions naming exact files (../shadcn/rules/icons.md vs polish/icons.md), and a state-coverage checklist. The one soft spot is the Validate step's "Run the smallest relevant lint, type, and test checks", which stays at category level rather than naming or locating executable commands, a minor gap against anchor 5's copy-paste-ready standard. | 4 / 5 |
Workflow Clarity | The five-step workflow (Understand → Select → Implement → Validate → Report) is clearly sequenced with validation checkpoints — lint/type/test, rendered-behavior verification, and resolving blocking polish findings. It falls short of anchor 5 because the checks are generic rather than command-specific and there is no explicit fix-and-re-run loop if validation fails; it stays above anchor 3 because checkpoints are present, not merely implied. | 4 / 5 |
Progressive Disclosure | The reference map is a well-signaled, condition-gated table ("Read this / When") with one-level-deep entries, and the body enumerates each entry's supporting files upfront so nothing is buried. Explicit negative guardrails ("do not load rules-compiled.md by default", "Do not load motion references for work with no motion concern") make navigation and discovery easy; note the referenced bundle files were not present in the provided review bundle, so this scores the structure as written. | 5 / 5 |
Total | 18 / 20 Passed |