Content
71%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 well-organized, appropriately-sized body with excellent progressive disclosure and a clear check-fix-review flow. The main weaknesses are redundancy across the Quick Reference, opening line, Explain, and Code Review sections, and verification guidance that names 'browser accessibility tooling' without any concrete tool or procedure.
Suggestions
Remove the duplication between the opening sentence and the Explain section, and trim the Quick Reference bullets that restate the Check and Fix sections verbatim — one authoritative statement of each point is enough.
Make the verification step concrete: name a specific check such as a keyboard-only Tab test on page load, or a specific tool (e.g. axe DevTools, VoiceOver/NVDA) instead of the generic 'browser accessibility tooling or assistive tech'.
Either include a minimal inline example of the recommended JavaScript focus pattern (e.g. focus set in a click handler) or explicitly note that the code example for it is in references/rule.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is compact overall but contains real redundancy: the opening line ('Autofocus teleports screen reader users to mid-page without context...') is nearly duplicated by the Explain section ('Explain how autofocus moves screen reader users to mid-page without context...'), the Quick Reference bullets restate the Check/Fix content, and the Code Review paragraph restates the frontmatter description. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than 4, where over-explanation would be only minor. | 3 / 5 |
Actionability | As an instruction-only skill the guidance is concrete and specific: 'Search for autofocus attributes on form elements', 'Remove autofocus attributes from form elements. If focus management is needed, use JavaScript to set focus after user interaction rather than automatically on page load.' It stops short of 5 because the JavaScript focus alternative is named but never shown or pointed to inline (the code example lives only in references/rule.md). | 4 / 5 |
Workflow Clarity | The Check → Fix → Explain → Code Review sections form a coherent review workflow with a named verification checkpoint ('note how to verify the fix with browser accessibility tooling or assistive tech'), matching 'clear sequence with most checkpoints present; minor validation gaps'. Not 5 because the verification step names no concrete tool or procedure (e.g. keyboard-only tab test, a specific screen reader, or axe DevTools). | 4 / 5 |
Progressive Disclosure | The body is under 50 lines, cleanly sectioned (Quick Reference, Check, Fix, Explain, Code Review), and points to a single one-level-deep reference that exists (references/rule.md) with its contents clearly labeled ('For full implementation details, code examples, and framework-specific guidance'). This matches 'clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation'. | 5 / 5 |
Total | 16 / 20 Passed |