CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

53

Quality

60%

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

70%

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-organized, concise overview that appropriately delegates detailed code to a real one-level reference. Its main weaknesses are repeated vestibular explanation, generic Code Review boilerplate, and in-body guidance that defers all executable examples to the reference.

Suggestions

State the vestibular-mismatch explanation once (e.g., in the intro) and drop its repetition in the Quick Reference bullet and Explain section to tighten the body.

Replace the generic 'Code Review' boilerplate ('Flag exact elements, roles, labels, focus behavior, or keyboard interactions') with parallax-specific review steps, since the current text overlaps the description's generic accessibility language.

Add a brief in-body verification checkpoint (e.g., 'Verify with OS Reduce-motion enabled that parallax is disabled and content stays readable') rather than deferring all verification to references/rule.md.

DimensionReasoningScore

Conciseness

The body is mostly lean, but the vestibular-mismatch point is repeated three times ('Parallax creates a mismatch...' in the intro, a Quick Reference bullet, and the Explain section), and the generic 'Code Review' boilerplate adds little parallax-specific value.

2 / 3

Actionability

The Fix section names concrete techniques ('Wrap parallax effects in @media (prefers-reduced-motion: no-preference) queries,' static fallbacks, a motion toggle) but provides no in-body executable code and hedges with 'Consider adding,' deferring all examples to references/rule.md.

2 / 3

Workflow Clarity

As a simple, single-purpose rule skill it is clearly organized into Check → Fix → Explain → Code Review sections with a concise overview, which per the simple-skills note warrants full marks even without an explicit multi-step workflow.

3 / 3

Progressive Disclosure

The body is a concise overview that clearly signals a single one-level-deep reference — 'see references/rule.md' — which exists and holds the full code examples and framework guidance, matching well-structured progressive disclosure.

3 / 3

Total

10

/

12

Passed

Description

50%

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 a templated, partly misaligned accessibility-review wrapper around a parallax rule: it has an explicit trigger and concrete actions, but those actions describe generic a11y review rather than parallax/motion handling. Trigger phrasing is awkward and missing common motion-related terms.

Suggestions

Rewrite the templated phrase 'patterns related to Provide alternatives to parallax effects' into natural prose naming the actual capability (e.g., 'Audit and disable parallax/motion effects that trigger vestibular discomfort').

Replace the generic accessibility-review actions (native semantics, keyboard behavior, focus flow, accessible names) with parallax-specific actions: checking prefers-reduced-motion handling, static fallbacks, and a user motion toggle.

Add natural trigger terms users would say — 'motion effects,' 'reduced motion,' 'scrolling/parallax,' 'vestibular' — and tighten the broad 'reviewing rendered HTML, interactive components, or design-system patterns' trigger that overlaps other a11y skills.

DimensionReasoningScore

Specificity

It lists concrete review actions — 'Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output' — but these describe generic accessibility review rather than the parallax/motion handling this skill actually performs, so the actions are not comprehensive or on-target for the skill.

2 / 3

Completeness

An explicit 'Use when reviewing rendered HTML...' trigger is present, but the stated 'what' (native semantics, keyboard behavior, focus flow, accessible names) is misaligned with a parallax-effects skill, so the capability description is weak rather than clearly on-target.

2 / 3

Trigger Term Quality

It includes a natural term ('parallax effects') but the trigger is awkwardly templated ('patterns related to Provide alternatives to parallax effects') and omits common variations users would say like 'motion,' 'reduced motion,' or 'vestibular.'

2 / 3

Distinctiveness Conflict Risk

The trigger 'Use when reviewing rendered HTML, interactive components, or design-system patterns' is broad enough to overlap many accessibility/frontend review skills, with only 'parallax effects' giving it a narrow niche.

2 / 3

Total

8

/

12

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.