skip-link

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Implement 'Skip to Content' links. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

Quality

77%

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/skip-link/SKILL.md

Quality

Content

71%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 appropriately offloads detailed code and examples to a real one-level reference. Its weakest area is actionability: the inline guidance is high-level and lacks concrete examples or flagged-element detail in the body itself.

Suggestions

Add one minimal inline HTML/CSS snippet (a skip link targeting #main-content and the :focus reveal rule) so the body is actionable without requiring the reference.

Tighten the opening sentence to a one-line purpose statement instead of explaining what skip links are and why they matter.

In the Code Review section, list 2-3 concrete failure signals to flag (e.g., skip link absent, not first focusable element, target id missing or non-focusable) rather than only describing what to review.

Dimension	Reasoning	Score
Conciseness	The body is lean and sectioned, with only minor over-explanation such as the opening 'Skip links allow keyboard and screen reader users to bypass repetitive navigation links, saving them significant time and effort' which restates a concept Claude already knows; it is efficient rather than fully token-optimized.	4 / 5
Actionability	The Quick Reference gives concrete high-level steps ('Add a skip link as the first focusable element', 'visible when focused', 'Link it to the main content container ID') but no executable code or flagged-element examples appear inline — those are delegated to the reference — leaving guidance incomplete in the body itself.	3 / 5
Workflow Clarity	Clear Check / Fix / Explain / Code Review sequence with a verify-the-fix checkpoint ('note how to verify the fix with browser accessibility tooling or assistive tech') for this simple single-purpose skill; not a level-5 explicit validate-fix-retry loop, but above the implicit-checkpoint level 3.	4 / 5
Progressive Disclosure	The body is a concise overview that signals a single one-level-deep reference ('see references/rule.md', verified to exist) for full implementation details, code examples, and framework-specific guidance, matching the clear-overview-with-well-signaled-references anchor.	5 / 5
	Total	16 / 20 Passed

Description

83%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 is strong: it opens with an explicit 'Use when' trigger, names a concrete accessibility niche, and lists specific review actions. Its main weakness is slight breadth in the trigger framing that risks overlap with sibling accessibility review skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete review actions ('Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output') with only minor coverage gaps, fitting the 'lists several specific actions' anchor rather than the fully comprehensive level 5.	4 / 5
Completeness	An explicit 'Use when reviewing rendered HTML, interactive components, or design-system patterns related to Implement Skip to Content links' trigger pairs with a clear 'what' of checking/inspecting behaviors, satisfying the both-what-and-when-with-concrete-triggers anchor.	5 / 5
Trigger Term Quality	Natural a11y-review terms like 'rendered HTML', 'interactive components', 'design-system patterns', 'Skip to Content links', 'focus flow', and 'screen-reader output' give good keyword coverage, though a few common synonyms are missing so it stops short of level 5.	4 / 5
Distinctiveness Conflict Risk	The 'Skip to Content links' niche is distinct, but the broad 'reviewing rendered HTML, interactive components, or design-system patterns' framing creates minor overlap risk with neighboring accessibility review skills, so it is mostly distinct rather than minimal-conflict level 5.	4 / 5
	Total	17 / 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/skip-link/SKILL.md
Commit: 30756a7

Reviewed: 23 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.