CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

reduced-motion

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Respect reduced motion preferences. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/reduced-motion/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews 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, appropriately scoped overview that delegates code and verification detail to a real, clearly-labeled reference file. Its main weakness is redundancy — Quick Reference, Check, and Fix restate the same three facts, and the Explain and Code Review sections add templated direction rather than new value.

Suggestions

Consolidate the overlapping Quick Reference, Check, and Fix sections into one section — prefers-reduced-motion, the 3-flashes/second limit, and motion warnings are each stated two to three times.

Trim the Explain section's direction to explain concepts Claude already knows (vestibular disorders, why motion controls matter) down to a single line or fold it into Check.

Inline a minimal @media (prefers-reduced-motion: reduce) snippet in the Fix section so the core remedy is visible without opening the reference file.

DimensionReasoningScore

Conciseness

The body is short and on-topic, but the same facts are repeated across sections — prefers-reduced-motion, the 3-flashes/second limit, and motion warnings each appear in Quick Reference, Check, and Fix — and the Explain section directs Claude to explain concepts it already knows ("Explain how motion affects users with vestibular disorders..."). Mostly efficient but could be meaningfully tightened, fitting anchor 3 rather than 4.

3 / 5

Actionability

The guidance is concrete and executable: a named mechanism ("Use @media (prefers-reduced-motion: reduce) to disable animations"), a measurable threshold ("Never flash content more than 3 times per second"), and specific substitution strategies ("Replace motion with opacity/color transitions"), with complete code one clearly-signaled hop away in references/rule.md. Minor gaps — no inline snippet and soft directives like "Provide motion warnings for immersive experiences" — keep it below anchor 5.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections give a coherent review sequence, and verification is addressed ("note how to verify the fix with browser accessibility tooling" plus the Verification section in rule.md). It falls short of anchor 5 because steps are prose paragraphs rather than explicit checkpoints, and validation guidance lives mostly in the reference file instead of being an inline step.

4 / 5

Progressive Disclosure

The ~45-line body is well-sectioned and defers all implementation detail to a single one-level-deep reference that exists in the bundle and is clearly signaled with its contents described ("For full implementation details, code examples, and framework-specific guidance, see references/rule.md" — verified present). This matches anchor 5: clear overview, well-signaled shallow reference, easy navigation.

5 / 5

Total

16

/

20

Passed

Description

58%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description correctly follows the 'Use when...' pattern and answers both what and when, but its substance is templated accessibility-review boilerplate that doesn't reflect the skill's actual reduced-motion content. Key domain trigger terms (prefers-reduced-motion, animations, flashing) are missing, weakening both specificity and distinctiveness.

Suggestions

Replace the generic inspection list (keyboard behavior, focus flow, accessible names, screen-reader output) with the skill's actual actions: verifying prefers-reduced-motion support, checking flash rates against the 3-per-second threshold, and providing motion alternatives.

Add the natural trigger terms users would say — 'prefers-reduced-motion', 'animations', 'parallax', 'vestibular' — to the when-clause so the skill triggers on real user phrasing.

Lead with the reduced-motion niche instead of burying it at the end of the when-clause, so the description is distinguishable from sibling accessibility-rule skills that share this template.

DimensionReasoningScore

Specificity

The description lists several concrete inspection actions ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output"), but these are generic accessibility-review steps that omit the skill's core actions — nothing about prefers-reduced-motion handling, animation disabling, or flash-rate limits. It names the domain plus concrete actions, yet the coverage gap is larger than 'minor', fitting anchor 3 better than 4.

3 / 5

Completeness

Both questions are explicitly answered: the when ("Use when reviewing rendered HTML, interactive components, or design-system patterns related to Respect reduced motion preferences") and the what ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output"). It falls short of anchor 5 because the 'what' describes templated accessibility checks rather than the skill's actual motion-specific actions, and the 'when' lacks natural trigger phrases users would say.

4 / 5

Trigger Term Quality

It includes some relevant natural terms ("reduced motion", "rendered HTML", "interactive components", "design-system patterns"), but misses the most common variations users would actually say: "prefers-reduced-motion", "animations", "parallax", or "motion sickness". This matches anchor 3 ('some relevant keywords but missing common variations') rather than 4, since the single most important technical trigger term is absent.

3 / 5

Distinctiveness Conflict Risk

The phrase "related to Respect reduced motion preferences" establishes a real niche marker, but the surrounding templated framing ("reviewing rendered HTML, interactive components, or design-system patterns... keyboard behavior, focus flow, accessible names") would equally match sibling accessibility skills like focus-order or alt-text rules. Somewhat specific, but notable overlap risk with similar skills — anchor 3.

3 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/reduced-motion/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.