Content
75%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 a well-organized, prioritized constraint checklist that is lean, assumes Claude's competence, and gives concrete reviewable rules with specific aria attributes and verification commands. The main gaps are minor: some redundancy between sections, no example before/after fixes, and no feedback loop for the NO-GO verification case. It is a strong single-file instruction skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is a lean constraint checklist ("icon-only buttons must have aria-label or aria-labelledby", "invalid fields must set aria-invalid") that assumes Claude's competence and never explains what accessibility is. Not 5 because of minor redundancy: the priority table repeats the category headers, "quote the exact snippet, state the failure, propose a small fix" duplicates the how-to-use output format, and "Prefer minimal, targeted fixes" repeats tool boundaries' "prefer minimal changes". | 4 / 5 |
Actionability | Concrete, checkable rules with specific attributes and elements ("aria-describedby", "aria-expanded and aria-controls", "tabindex greater than 0") plus executable verification commands (`pnpm lint`, `pnpm test`, `pnpm build`, `pnpm verify`) — 'Mostly executable guidance; concrete code or commands with minor gaps'. Not 5 because no example fixes (before/after snippets) are shown, leaving the 'code-level suggestion' output to be constructed from scratch. | 4 / 5 |
Workflow Clarity | A clear sequence is present: prioritized rule categories ("fix critical issues first (names, keyboard, focus, tool boundaries)"), a defined review output format (snippet + why + fix), and an explicit validation checkpoint ("If code touched: run pnpm lint, pnpm test, pnpm build, pnpm verify; report GO or NO-GO with evidence"). Not 5 because there is no feedback loop after a NO-GO result and the dual mode (apply constraints during UI work vs. file review) is not crisply sequenced. | 4 / 5 |
Progressive Disclosure | No bundle files exist (references/, scripts/, assets/ are absent) and the body references none, so this is a single-file skill with good structure: how to use, when to apply, a priority table, and per-category quick reference sections. Not 5 because at ~120 lines it exceeds the under-50-line simple-skill threshold, and the rule catalog could arguably live in a referenced file; it fits 'Good structure; most content is appropriately placed; minor organization gaps'. | 4 / 5 |
Total | 16 / 20 Passed |