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.
The body is an exemplary conventions skill: lean, non-obvious gotchas (Google Translate crash), executable patterns, and concrete validation. Its one real defect is that the entire progressive-disclosure layer is dangling — all seven referenced files are absent from the bundle.
Suggestions
Ship the seven referenced files (forms.md, ui-components.md, responsive-design.md, testing.md, code-quality.md, performance.md, permissions.md) alongside SKILL.md, or remove the dead links — as written, every 'See X for details' pointer leads nowhere.
Add a fix-and-retry loop around `npm run deps:validate` (read the dependency-cruiser report, fix the import, re-run) so the single validation checkpoint is a true feedback loop.
Resolve the ambiguous link paths — the body links bare `forms.md` while conventions usually place these under references/; align the hrefs with wherever the files actually live.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence: no explanation of what React or TanStack Query is, just decisions ("TanStack Query (never raw fetch/useEffect)"), ❌/✅ pairs, and rules. The one long section — Browser Translation Safety — earns its tokens with genuinely non-obvious failure mechanics and a tracked issue reference. Every token earns its place. | 5 / 5 |
Actionability | Guidance is fully executable: copy-paste TypeScript patterns for useQuery/useMutation with invalidation, Zustand selectors, memoization rules, a runnable validation command (`npm run deps:validate`), and a concrete crash fix (`<span>{label}</span>`, ref'd textContent, `translate="no"`). The common cases (fetching, mutating, selecting store slices, memoizing) are all covered with concrete examples. | 5 / 5 |
Workflow Clarity | As a conventions/gotchas reference rather than a linear process, the per-topic guidance is unambiguous and includes one explicit validation checkpoint ("After modifying imports: `npm run deps:validate`") plus hard boundary rules ("v1/ CANNOT import from v2/"). It stops short of anchor 5: there is no end-to-end sequence, and deps:validate has no fix-and-retry loop explaining what to do on failure — a minor validation gap for a change workflow. | 4 / 5 |
Progressive Disclosure | The Reference Files section is well-signaled with one-line descriptions — anchor-5 structure on paper — but none of the seven linked files (forms.md, ui-components.md, responsive-design.md, testing.md, code-quality.md, performance.md, permissions.md) exist in the bundle (no references/ directory or sibling files), so every link is dead. Clearly-signaled references pointing at missing files break navigation, matching anchor 3's 'references present but not clearly signaled' level of organization defect. | 3 / 5 |
Total | 17 / 20 Passed |