CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

64

Quality

76%

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

78%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, concise overview that points cleanly to a single reference file for depth. It scores high on progressive disclosure and actionability, with only minor conciseness redundancy and no destructive-operation concerns to validate.

DimensionReasoningScore

Conciseness

The body is lean—Quick Reference bullets plus short Check/Fix/Explain/Code Review sections—assuming Claude's competence; the only redundancy is mild overlap between Quick Reference and the Check/Fix sections.

4 / 5

Actionability

Concrete, actionable directives are present ('Use @media (prefers-reduced-motion: reduce) to disable animations', 'no flashing exceeds 3 flashes/second'); full code examples are deferred to the reference file, which is appropriate for an instruction-oriented skill.

4 / 5

Workflow Clarity

A clear review sequence (Check → Fix → Explain → Code Review) with an explicit verification checkpoint ('note how to verify the fix with browser accessibility tooling or assistive tech').

4 / 5

Progressive Disclosure

An under-50-line overview with well-organized sections and a single, clearly signaled one-level-deep pointer to references/rule.md (verified to exist), keeping navigation simple.

5 / 5

Total

17

/

20

Passed

Description

75%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 is well-formed with an explicit trigger clause and concrete actions, scoring consistently across dimensions. Its main weakness is that the enumerated inspection actions are generic accessibility checks rather than reduced-motion-specific ones.

Suggestions

Tighten the description so the listed actions are reduced-motion-specific (e.g., 'Check that non-essential animations are disabled under prefers-reduced-motion and that no content flashes more than 3 times per second') rather than generic a11y checks.

Add natural synonyms users would say such as 'animations', 'prefers-reduced-motion', 'flashing', or 'parallax' to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain (reduced motion, rendered HTML, interactive components) and lists several concrete inspection actions ('Check native semantics', 'inspect keyboard behavior, focus flow, accessible names, and screen-reader output'), with only minor coverage gaps.

4 / 5

Completeness

Explicitly answers both halves: a 'Use when reviewing…' trigger clause (when) and concrete inspection actions (what), with the trigger being fairly specific rather than vague.

4 / 5

Trigger Term Quality

Includes natural terms users would say ('reduced motion preferences', 'rendered HTML', 'interactive components', 'design-system patterns'), though it omits common synonyms like 'animations', 'prefers-reduced-motion', or 'flashing'.

4 / 5

Distinctiveness Conflict Risk

'Respect reduced motion preferences' carves a clear niche, but the listed actions (keyboard behavior, focus flow, accessible names, screen-reader output) are generic accessibility concerns that overlap with sibling a11y skills.

4 / 5

Total

16

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.