CtrlK
BlogDocsLog inGet started
Tessl Logo

scrolljacking

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

62

Quality

73%

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/scrolljacking/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A clean, well-structured single-purpose rule skill that delegates detail to references/rule.md. It would score higher by removing the duplicated explanatory sentence, naming concrete verification tools, and adding an explicit validation checkpoint.

Suggestions

Remove the near-verbatim duplicate of the opening sentence in the Explain section to tighten conciseness.

Replace 'verify it feels native' / 'browser accessibility tooling' with named checks (e.g., specific keyboard/screen-reader tests or DevTools panels) to improve actionability.

Add an explicit validation step in the Check/Fix loop (e.g., 'After removing the override, re-test keyboard scroll and reduced-motion to confirm native behavior is restored').

DimensionReasoningScore

Conciseness

Mostly lean with no concept padding, but the opening sentence and the 'Explain' section repeat the same phrase about disrupting navigation and assistive technologies nearly verbatim, which is unnecessary duplication.

2 / 3

Actionability

Concrete, specific guidance ('Remove JavaScript that overrides default scroll behavior', 'respect prefers-reduced-motion') is appropriate for an instruction-only skill, but 'verify it feels native' and 'browser accessibility tooling' are vague without named tools or commands.

2 / 3

Workflow Clarity

Check/Fix/Explain sections give a clear sequence for this simple skill, but there is no explicit validation checkpoint to confirm a fix actually restores native scrolling.

2 / 3

Progressive Disclosure

Concise overview with clearly signaled one-level-deep pointer to the verified references/rule.md, and well-organized sections — appropriate for a short single-purpose skill.

3 / 3

Total

9

/

12

Passed

Description

90%

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

A strong, third-person description with an explicit 'Use when' trigger and a concrete sequence of inspection actions. Minor specificity gap keeps it just below maximal, but it is clear, complete, and distinct.

DimensionReasoningScore

Specificity

Names the accessibility domain and lists several concrete inspection actions ('keyboard behavior, focus flow, accessible names, and screen-reader output'), but is not a comprehensive list of distinct concrete actions like the top anchor.

2 / 3

Completeness

Explicitly answers both what ('Check native semantics first, then inspect...') and when ('Use when reviewing rendered HTML, interactive components, or design-system patterns').

3 / 3

Trigger Term Quality

Good natural coverage of terms users would say — 'scrolljacking', 'custom scroll behavior', 'rendered HTML', 'keyboard behavior', 'screen-reader output' — though a few common variations are absent.

3 / 3

Distinctiveness Conflict Risk

A clear niche (scrolljacking/custom scroll behavior in accessibility) with distinct, rule-specific triggers unlikely to fire for unrelated skills.

3 / 3

Total

11

/

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.