CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

72%

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%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 well structured with exemplary progressive disclosure — a lean overview correctly deferring detail to a single clearly-signaled reference file. It is dragged down by verbatim duplication of the harm statement across three sections, absence of any detection/verification detail in the body itself, and no explicit verification checkpoint in the Check/Fix workflow.

Suggestions

Delete the Explain section (or the intro paragraph) — the sentence "Scrolljacking breaks user expectations, interferes with assistive technologies, and creates unpredictable experiences..." is repeated verbatim in both, and near-verbatim in the Quick Reference bullet.

Move at least one concrete detection method from references/rule.md into the Check section (e.g., the console wheel-event defaultPrevented test) so the body's guidance is executable without opening the reference.

Add an explicit verification step to the Check/Fix flow (e.g., "Verify: scroll with mouse wheel and keyboard Page Up/Down; confirm movement feels native and all content including the footer is reachable") rather than only instructing to "note how to verify the fix".

DimensionReasoningScore

Conciseness

The harm statement "Scrolljacking breaks user expectations, interferes with assistive technologies, and creates unpredictable experiences..." appears verbatim in both the intro and the Explain section, and near-verbatim again as a Quick Reference bullet — the entire Explain section restates the intro and could be cut. It is not a 2 because the body is brief overall with no explanation of concepts Claude already knows.

3 / 5

Actionability

The Fix section gives concrete direction ("Remove JavaScript that overrides default scroll behavior... respect prefers-reduced-motion") and Check names specific things to inspect, but the body contains no method, command, or detection snippet for how to test or verify — all executable detail is deferred to the reference. This is incomplete concrete guidance rather than the minor gaps of a 4.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections imply a recognizable sequence, but no verification checkpoint exists in the body; Code Review only says to "note how to verify the fix with browser accessibility tooling" without an actual verification step (manual checks live only in the reference). Sequence present with implicit/missing checkpoints matches the anchor.

3 / 5

Progressive Disclosure

The body is a concise, well-sectioned overview under 50 lines that cleanly splits implementation detail, code examples, and framework guidance into references/rule.md — a real file, one level deep, clearly signaled with an explicit "For full implementation details... see references/rule.md" pointer. This matches the clear-overview, well-signaled one-level-deep reference pattern.

5 / 5

Total

14

/

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.

A solid description with an explicit "Use when" trigger, several concrete inspection actions, and a distinct niche topic. Its main weaknesses are a generic broad opening phrase, missing natural synonyms for the scroll-hijacking concept, and a "what" that is woven into the trigger clause rather than stated crisply.

DimensionReasoningScore

Specificity

Lists several concrete actions ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output"), but the opening "reviewing rendered HTML, interactive components, or design-system patterns" is generic, leaving minor gaps in coverage rather than comprehensive specificity.

4 / 5

Completeness

Both elements are present: an explicit "Use when reviewing rendered HTML..." trigger clause and a what consisting of concrete check/inspect actions. It is not a 5 because the what is embedded in the trigger clause and phrased as instructions rather than a clear, standalone statement of the skill's capability.

4 / 5

Trigger Term Quality

Includes the natural terms users would say ("scrolljacking", "custom scroll behavior", "rendered HTML", "interactive components") but misses common synonyms and variations such as "scroll hijacking", "hijacked scroll events", "scroll snap", or "one page per scroll", so it falls short of comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

"scrolljacking and custom scroll behavior" is a clear niche with distinct triggers, but the broad opener "reviewing rendered HTML, interactive components, or design-system patterns" creates minor overlap risk with sibling accessibility-review skills in the same category.

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.

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/scrolljacking/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.