Content
63%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 compact, well-structured overview that appropriately delegates detail to a real one-level-deep reference file. Weaknesses are redundancy between the intro, Quick Reference, and 'Explain' sections, and a Check step that says what to look for but not how to detect it.
Suggestions
Add a concrete detection method to the Check section (e.g., inspect document.body.getAttribute('aria-hidden') in the rendered DOM or the browser accessibility tree, or run axe/Lighthouse) instead of the unactionable 'at any point in the lifecycle'.
Remove the 'Explain' section and the Quick Reference bullet that duplicate the opening paragraph's point about silencing the page for screen readers.
Merge the overlapping Check, Explain, and Code Review sections into one review sequence that ends with a verification step in the body.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is short, but the Quick Reference bullet 'Hiding the body makes the entire page invisible to assistive technologies' duplicates the opening paragraph, and the 'Explain' section ('Explain the catastrophic impact...') restates it a third time without adding guidance. This is more than minor trimmable padding, so anchor 3 rather than 4. | 3 / 5 |
Actionability | The Fix is concrete ('Remove aria-hidden="true" from the <body> and use it only on specific background containers when modals are open'), but the Check gives no detection method for 'at any point in the lifecycle' (no command, snippet, or tooling pointer in the body), and 'Explain'/'Code Review' describe rather than instruct. Missing key details, so anchor 3 rather than 4. | 3 / 5 |
Workflow Clarity | A simple single-task skill with an unambiguous Check-then-Fix sequence. Not 5 because the Check, Explain, and Code Review sections overlap in content and no verification step appears in the body itself (it lives in references/rule.md); not a destructive/batch operation, so no cap applies. | 4 / 5 |
Progressive Disclosure | The body is a concise overview under 50 lines with well-organized sections, and it clearly signals a single one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md') that exists in the bundle. Content is appropriately split between overview and detail file. | 5 / 5 |
Total | 15 / 20 Passed |