CtrlK
BlogDocsLog inGet started
Tessl Logo

anchor-smooth-scroll

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Provide instant anchor scroll option. 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/anchor-smooth-scroll/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 well-structured and appropriately uses progressive disclosure with a real one-level reference, with a clear Check-to-Fix workflow for a simple rule; its main weaknesses are redundant content between sections and the lack of an executable code example.

Suggestions

Remove the overlap between the Quick Reference bullets and the Fix section, and drop the duplicate vestibular-disorder rationale that already appears in the intro and the Explain section.

Add a concrete, copy-paste-ready CSS snippet in the Fix section, e.g. the '@media (prefers-reduced-motion: no-preference) { html { scroll-behavior: smooth; } }' pattern, so the guidance is executable rather than descriptive.

DimensionReasoningScore

Conciseness

The body is largely lean, but the Quick Reference bullets duplicate the Fix section (e.g., 'scroll-behavior: smooth' with a prefers-reduced-motion check appears in both) and the vestibular-disorder rationale is restated in both the intro and the Explain section, so it could be tightened.

2 / 3

Actionability

The Fix section names concrete specifics ('scroll-behavior: smooth only within a prefers-reduced-motion media query check', 'focus moves to the anchor target'), but provides no copy-paste-ready CSS snippet, leaving the guidance descriptive rather than executable.

2 / 3

Workflow Clarity

This is a simple single-rule skill with an unambiguous action and an explicit verification step in the Check section ('verify smooth scrolling is disabled when prefers-reduced-motion is set'), satisfying the simple-skill allowance for a top score.

3 / 3

Progressive Disclosure

A short, well-organized overview points to a clearly signaled, one-level-deep reference ('see references/rule.md'), and that file exists, matching the clear-overview-with-well-signaled-references anchor.

3 / 3

Total

10

/

12

Passed

Description

77%

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 well-formed with explicit what/when structure and concrete actions, but its trigger terms are templated and awkward rather than natural, and its generic accessibility-review framing risks overlapping with other accessibility skills.

Suggestions

Replace the embedded rule title 'Provide instant anchor scroll option' with natural trigger terms users would actually say, such as 'smooth scroll', 'anchor links', 'jump links', or 'prefers-reduced-motion'.

Narrow the generic 'reviewing rendered HTML, interactive components, or design-system patterns' trigger to smooth-scroll and reduced-motion scenarios specifically, reducing overlap with sibling accessibility skills.

Align the stated 'what' actions (keyboard behavior, focus flow, accessible names, screen-reader output) with the skill's actual smooth-scroll / prefers-reduced-motion focus, since the current actions describe a generic a11y review rather than this rule.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output" — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

It explicitly states both what ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output") and when ("Use when reviewing rendered HTML, interactive components, or design-system patterns related to Provide instant anchor scroll option"), with an explicit Use-when trigger clause.

3 / 3

Trigger Term Quality

It includes some relevant keywords ("anchor scroll option", "rendered HTML") but omits natural variations a user would actually say such as "smooth scroll", "jump links", or "prefers-reduced-motion", and the phrase "Provide instant anchor scroll option" is an awkward embedded rule title rather than a natural trigger.

2 / 3

Distinctiveness Conflict Risk

The broad trigger "reviewing rendered HTML, interactive components, or design-system patterns" could overlap with many sibling accessibility review skills; only the "anchor scroll" phrase narrows it, leaving it somewhat generic.

2 / 3

Total

10

/

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.