CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

77%

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/parallax-effects/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 lean, well-structured overview that gives concrete, actionable CSS-level guidance and correctly pushes code examples and framework details into a single real, clearly-signaled reference file. Its only real flaws are a triple-stated vestibular rationale and verification guidance that names no specific tooling. It is a solid example of an instruction-only skill with appropriate progressive disclosure.

DimensionReasoningScore

Conciseness

The body is tight and lean with well-scoped sections, but the vestibular rationale is stated three times — the intro ("Parallax creates a mismatch between what the eyes see and what the inner ear senses"), the Quick Reference bullet ("Parallax creates depth mismatch triggering vestibular disorders"), and the Explain section. That minor repetition keeps it below the 'every token earns its place' anchor, but nothing explains concepts Claude already knows.

4 / 5

Actionability

The Fix section gives concrete, executable instruction ("Wrap parallax effects in @media (prefers-reduced-motion: no-preference) queries. Provide static fallbacks that convey the same content. Consider adding a user toggle"), and full code examples live one reference away in references/rule.md. Not 5 because the body itself contains no inline code or command — the anchor-5 example includes copy-paste ready snippets covering common cases.

4 / 5

Workflow Clarity

A simple single-purpose skill with an unambiguous Check → Fix → Explain flow and an embedded verification step ("Verify these effects are disabled when prefers-reduced-motion is set, and essential content is accessible without the effect"). Not 5 because the verification guidance in Code Review is vague ("verify the fix with browser accessibility tooling or assistive tech") with no concrete tool or command named.

4 / 5

Progressive Disclosure

A short, well-organized overview body with 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 (CSS good/bad examples, JavaScript parallax control). Content is appropriately split between overview and detail file, making navigation easy.

5 / 5

Total

17

/

20

Passed

Description

67%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 clause and names concrete review actions, but the core capability is conveyed only through an awkwardly embedded rule title, and the natural trigger vocabulary (reduced motion, vestibular, motion sensitivity) is thin. The templated inspection boilerplate (keyboard behavior, focus flow, screen-reader output) only weakly matches the skill's actual subject matter. It reads as generated from a template rather than written for this specific rule.

Suggestions

State the core capability as an action in the description, e.g. "Identify parallax and motion effects and provide prefers-reduced-motion alternatives and static fallbacks" instead of embedding the rule title mid-sentence.

Add natural trigger terms users would actually say: "reduced motion", "prefers-reduced-motion", "motion sickness", "vestibular disorders", "scrolling effects".

Replace the generic inspection boilerplate (keyboard behavior, focus flow, accessible names) with actions specific to this rule — verifying background-attachment/transform-based parallax is gated behind a no-preference media query and that a motion toggle exists.

DimensionReasoningScore

Specificity

Lists several concrete actions ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output"), matching the anchor for several specific actions with minor gaps. Not 5 because the core capability (providing reduced-motion alternatives to parallax) is never stated as an action — only as an embedded rule title.

4 / 5

Completeness

Both elements are explicitly present: an explicit "Use when reviewing rendered HTML, interactive components, or design-system patterns related to parallax effects" clause and a stated what (reviewing parallax alternatives, checking semantics and assistive behaviors). Not 5 because the 'what' is a rule title wedged mid-sentence ("related to Provide alternatives to parallax effects") rather than a clear capability statement, and the listed inspection actions only loosely match the skill's actual CSS/motion focus.

4 / 5

Trigger Term Quality

"parallax effects" is a strong natural keyword, but common variations users would say — "reduced motion", "prefers-reduced-motion", "vestibular", "motion sensitivity" — are absent. The remaining trigger terms ("rendered HTML", "interactive components", "design-system patterns") are broad generic preamble rather than natural user phrases, fitting the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

"parallax effects" carves out a clear niche with minimal conflict risk. Not 5 because the generic review boilerplate ("reviewing rendered HTML, interactive components, or design-system patterns... check native semantics... inspect keyboard behavior") appears designed to be shared across a whole family of accessibility rules, so within such a bundle only the single keyword distinguishes it from siblings.

4 / 5

Total

15

/

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/parallax-effects/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.