Content
40%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 appropriately lean but offers almost no actionable, screen-reader-specific guidance and relies entirely on a referenced playbook that does not exist in the bundle. Workflow sequencing is generic and lacks validation checkpoints.
Suggestions
Provide concrete, executable guidance inline — e.g., named screen readers (NVDA, VoiceOver, JAWS), keyboard-only navigation steps, and how to capture the announcement/ARIA output.
Add a real validation checkpoint workflow (e.g., navigate by region/heading, verify focus order, confirm dynamic announcements) instead of generic "apply best practices" steps.
Create the referenced `resources/implementation-playbook.md` (or move it under references/) so the deferred detailed patterns actually resolve, or remove the dangling reference and inline the essential content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence without explaining what screen readers are. The only minor trim is the opening line restating the description verbatim. It is efficient with a minor redundant instance, fitting the level-4 anchor rather than the fully lean level-5 anchor. | 4 / 5 |
Actionability | The Instructions are generic boilerplate ("Clarify goals", "Apply relevant best practices", "Provide actionable steps") with no concrete commands, named tools, or executable steps — and the only concrete pointer is to an external playbook. This matches the anchor for minimal concrete guidance missing specific steps to execute. | 2 / 5 |
Workflow Clarity | The Instructions give a rough generic sequence (clarify → apply → verify) with no screen-reader-specific steps and no validation checkpoints for a testing workflow. It fits the level-2 anchor of a rough sequence with poorly defined steps and absent validation, not the level-3 anchor which requires an actual concrete sequence. | 2 / 5 |
Progressive Disclosure | The body defers all detail to `resources/implementation-playbook.md`, but no such file exists — neither the standard bundle directories (references/, scripts/, assets/) nor a resources/ directory is present — so the one signaled reference is dangling and navigation fails. This fits the level-2 anchor of minimal structure with a problematic reference rather than the level-3 anchor where references are present and usable. | 2 / 5 |
Total | 10 / 20 Passed |