parallax-effects

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

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/parallax-effects/SKILL.md

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 content is a well-structured, lean review skill with a clear Check/Fix/Explain/Code Review sequence and a clean single-level reference to rule.md; its main weakness is mild redundancy of the vestibular-disorder framing.

Suggestions

State the vestibular-disorder rationale once (in Explain) and reference it rather than repeating it in the intro and Quick Reference.

Add one inline minimal code snippet for the prefers-reduced-motion media query so the Fix section is copy-paste ready without opening the reference.

Make the verification step an explicit checkpoint (e.g., 'Verify: confirm motion is static under prefers-reduced-motion: reduce') rather than a general instruction to 'note how to verify'.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight, but the vestibular-disorder explanation recurs three times (intro, Quick Reference bullet, Explain section) and the intro explains a concept Claude already knows; it could be consolidated.	3 / 5
Actionability	The Fix section gives concrete, executable guidance ('Wrap parallax effects in @media (prefers-reduced-motion: no-preference) queries. Provide static fallbacks...'), with only the minor gap that inline code examples are deferred to references/rule.md.	4 / 5
Workflow Clarity	The Check / Fix / Explain / Code Review sections form a clear review sequence and the Code Review section names verification ('verify the fix with browser accessibility tooling or assistive tech'), though the validation checkpoint is described rather than prescribed as a loop.	4 / 5
Progressive Disclosure	The body is a concise overview with a single, clearly signaled one-level-deep pointer ('see references/rule.md' for full implementation details and code examples), and that referenced file exists.	5 / 5
	Total	16 / 20 Passed

Description

63%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 has an explicit trigger and concrete actions, but it frames the skill as a generic accessibility review rather than the parallax/motion-specific task it actually is, weakening trigger quality and distinctiveness.

Suggestions

Lead with the parallax-specific action (e.g., 'Disable or replace parallax motion effects that trigger vestibular disorders') instead of generic accessibility-review verbs.

Add natural trigger terms users would say: 'parallax', 'motion sickness', 'prefers-reduced-motion', 'vestibular', 'dizziness'.

Trim the generic review checklist ('native semantics, keyboard behavior, focus flow, accessible names, screen-reader output') which overlaps with broad accessibility skills and dilutes distinctiveness.

Dimension	Reasoning	Score
Specificity	Lists several concrete review actions ('Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output') but these are generic accessibility-review actions rather than parallax-specific fixes, leaving minor gaps.	4 / 5
Completeness	Both 'what' (the inspection actions) and 'when' (an explicit 'Use when reviewing rendered HTML...' clause) are present, but the 'what' is misaligned toward generic review rather than the parallax-specific task.	4 / 5
Trigger Term Quality	The natural keyword 'parallax effects' appears, but the surrounding triggers ('rendered HTML, interactive components, design-system patterns') are awkward design-system jargon and miss common variations users would say like 'motion', 'prefers-reduced-motion', or 'vestibular'.	3 / 5
Distinctiveness Conflict Risk	Only 'parallax effects' is distinctive; the rest ('reviewing rendered HTML, interactive components... check native semantics, keyboard behavior, focus flow, accessible names') describes nearly any accessibility review skill, creating real overlap risk.	3 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/parallax-effects/SKILL.md
Commit: 30756a7

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.