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.
The body is a well-structured, concise overview with a clear check/fix/explain workflow and exemplary progressive disclosure to a single verified reference file. Its main weakness is actionability: the concrete thresholds are present, but no specific measurement tool or command is named in the body itself, and there is minor duplication between the Quick Reference and Check sections.
Suggestions
Name a concrete measurement method instead of "animation tools" — e.g. a specific tool or a quick way to compute flash frequency from an animation-duration value (0.2s duration = 5 flashes/second).
Remove the duplication between Quick Reference and Check (the GIF/video/CSS-animation testing line and the 3-60 Hz fact each appear twice in ~35 lines).
Inline one small executable example (e.g. the dangerous vs. safe CSS animation snippet) so the body is actionable without opening the reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and well-organized, but the Quick Reference bullets are repeated nearly verbatim in the Check section ("Test animated GIFs, videos, and CSS animations for rapid flashing" appears twice), and the 3-60 Hz / photosensitive-epilepsy fact is stated in both the intro and the Explain section. | 4 / 5 |
Actionability | Concrete numeric criteria are given ("no content flashes more than 3 times per second", "less than 25% of the viewport"), but the body contains no executable code or commands, and "Use animation tools to measure flash frequency" names no specific tool, leaving key details to the reference file. | 3 / 5 |
Workflow Clarity | A clear Check → Fix → Explain → Code Review sequence is present with verification mentioned ("note how to verify the fix with browser accessibility tooling or assistive tech"), but the verification checkpoint is not concrete — no specific tool or command is named, a minor validation gap. | 4 / 5 |
Progressive Disclosure | The skill is under 50 lines with well-organized sections and a single clearly signaled, one-level-deep reference: "For full implementation details, code examples, and framework-specific guidance, see references/rule.md" — and that file exists with exactly that content (203 lines including CSS examples and framework guidance). | 5 / 5 |
Total | 16 / 20 Passed |