Content
65%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-structured, token-efficient overview body that correctly pushes implementation detail to a single one-level-deep reference. Its weaknesses are in execution guidance: the Check step lacks any concrete method, and no explicit validation/verification step is built into the workflow.
Suggestions
Make the Check section instructive rather than descriptive: name the concrete method (e.g., keyboard-only pass: open/close each modal and confirm focus moves in and returns to the trigger; Tab through SPAs after route change), instead of "Verify that focus is properly managed".
Add an explicit validation checkpoint to the workflow, e.g., a final step "Re-test with keyboard only and confirm focus moves to new content and returns on close — using axe/Lighthouse or manual keyboard pass" — turning the advisory verify mention into a sequenced step.
Drop or merge the "Explain" section and the duplicated Check/Code Review prose; fold their unique content (flag exact elements/roles, note verification approach) into a single tighter review step to raise conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean with no over-explanation of concepts Claude already knows, but the "Explain" section and the motivational opener ("Poor focus management leaves keyboard users stranded…") are tokens Claude doesn't need, and "Check" duplicates part of "Code Review". Not 5 for these redundancies; not 3 because nothing is noticeably verbose. | 4 / 5 |
Actionability | Concrete specifics exist ("Use tabindex='-1' to make non-interactive elements focusable", "tabindex, focus(), and focus trapping for modal dialogs", "Move focus to modal when opened, return to trigger when closed"), but the Check section ("Verify that focus is properly managed…") describes rather than instructs and no executable example appears inline — key details are deferred to the reference. Matches "some concrete guidance but incomplete". | 3 / 5 |
Workflow Clarity | Check → Fix → Explain gives a coherent sequence, but validation checkpoints are implicit: "note how to verify the fix with browser accessibility tooling" is advisory prose rather than a step, and there is no explicit re-test step. This is a review skill, so the destructive/batch cap does not apply. Not 4 because checkpoints are missing rather than mostly present. | 3 / 5 |
Progressive Disclosure | The body is a concise overview and the single reference (references/rule.md, verified to exist) is one level deep and clearly signaled with its purpose stated ("For full implementation details, code examples, and framework-specific guidance"). The reference itself contains no nested references, and content is appropriately split between overview and detail. | 5 / 5 |
Total | 15 / 20 Passed |