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.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/anchor-smooth-scroll/SKILL.md

Quality

Content

65%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 well-organized, concise overview that defers implementation detail to a single clearly-signaled reference file, appropriate for a simple accessibility rule skill. The main weakness is actionability: the body gives conceptual steps but no executable code, relying entirely on the reference for the copy-paste-ready CSS/JS/React examples.

Suggestions

Inline one minimal executable snippet (the prefers-reduced-motion media query around scroll-behavior: smooth) so the skill is actionable without opening the reference.

Avoid repeating the vestibular-disorders rationale in both the intro and the Explain section to tighten token use.

Verify the 'Exceptions' content in references/rule.md, which discusses data-table markup that appears unrelated to anchor smooth scroll.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-sectioned (Quick Reference, Check, Fix, Explain, Code Review) with almost no padding of concepts Claude already knows; the only minor slack is the repeated 'vestibular disorders' rationale appearing in both intro and Explain.	4 / 5
Actionability	The body itself gives high-level actionable steps (disable smooth scroll under prefers-reduced-motion, move focus to target) but no executable code; concrete CSS/JS/React code lives only in references/rule.md, so the inline guidance is incomplete on its own.	3 / 5
Workflow Clarity	The Check -> Fix -> Explain -> Code Review sequence is clear and the Check section includes verification (confirm with keyboard and screen readers); this is a simple, non-destructive single-purpose skill so a 4-level sequence with verification checkpoints is appropriate, though no explicit validate-retry loop exists.	4 / 5
Progressive Disclosure	SKILL.md is an overview that cleanly points to references/rule.md (a real, one-level-deep file) for full implementation details, code, and framework guidance; the reference is clearly signaled, though only a single reference file exists so coverage is narrow.	4 / 5
	Total	15 / 20 Passed

Description

58%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 includes an explicit 'Use when' trigger and names concrete inspection actions, but it reads as a generic accessibility-review description bolted onto a specific rule title, with the rule name awkwardly interpolated mid-sentence. Trigger-term coverage and distinctiveness are moderate rather than strong.

Suggestions

Lead with the specific capability (e.g., 'Provide an instant anchor scroll option that respects prefers-reduced-motion') instead of embedding the rule title inside a generic accessibility-review framing.

Add natural user-facing trigger terms such as 'smooth scroll', 'same-page navigation', 'vestibular disorders', and 'motion sickness'.

Sharpen the 'when' clause so it clearly triggers on anchor-link / same-page navigation and smooth-scroll work rather than broad HTML/component review.

Dimension	Reasoning	Score
Specificity	Names the domain (reviewing rendered HTML/components/design-system patterns for anchor scroll) and several concrete actions (inspect keyboard behavior, focus flow, accessible names, screen-reader output), but the actions are framed as inspection tasks rather than the actual fix work the skill performs.	3 / 5
Completeness	Has a clear 'Use when...' clause stating when to invoke it and a reasonable 'what' (reviewing accessibility patterns), but the 'what' is somewhat generic and the when could be more explicit about the anchor-scroll trigger.	4 / 5
Trigger Term Quality	Includes some natural terms (anchor scroll, prefers-reduced-motion, focus, screen readers) but is missing common synonyms and phrasings a user would naturally say (e.g., 'smooth scroll', 'vestibular', 'motion sickness', 'same-page navigation').	3 / 5
Distinctiveness Conflict Risk	Narrowed to anchor smooth scroll within accessibility review, but the 'reviewing rendered HTML, interactive components, or design-system patterns' framing overlaps broadly with other accessibility/design-system review skills.	3 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/anchor-smooth-scroll/SKILL.md
Commit: 30756a7

Reviewed: 15 days ago

Table of Contents

Discovery Implementation Validation

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.