skip-navigation

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Include a skip navigation link. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

Quality

70%

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

Quality

Content

72%

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

The body is concise and well-structured with correct progressive disclosure to a real, well-organized references/rule.md. Its weaknesses are mild: the body offers specific but non-executable guidance (code lives only in the reference) and the review workflow's verification loop is implied rather than an explicit checkpoint sequence.

Suggestions

Add a short inline verification checklist in the body (e.g. '1. Press Tab on load → link appears; 2. Activate → focus reaches main; 3. Screen reader announces main region') so the workflow has an explicit validate loop without bloating the overview.

Include a minimal inline markup snippet (the anchor link + main id) so the body is executable on its own, keeping full framework examples in the reference.

Dimension	Reasoning	Score
Conciseness	The body is lean: a one-line rationale, a four-bullet quick reference, and tight Check/Fix/Explain/Code Review sections with no padding or explanation of concepts Claude already knows; every section earns its place and detail is correctly deferred to references/rule.md.	3 / 3
Actionability	The Quick Reference gives concrete anchors ("first focusable element", "id='main-content'", "press Tab after page load") and Code Review gives a clear review framing, but the body itself contains no executable code or copy-paste markup — that lives only in the referenced file — so guidance is specific but not fully self-contained/executable.	2 / 3
Workflow Clarity	Sections are sequenced (Check → Fix → Explain → Code Review) and the Quick Reference implies a Tab-after-load test, but there is no explicit ordered workflow with validation/verification checkpoints in the body; for a destructive/batch context this would cap at 2, and even for a review task the verification loop is implied rather than stated inline.	2 / 3
Progressive Disclosure	The body is a concise overview that explicitly and clearly signals one-level-deep detail via 'see references/rule.md', the referenced file exists and is well-structured (Code Example, CSS, Framework Examples, Verification), and navigation is easy with no nested/deep references.	3 / 3
	Total	10 / 12 Passed

Description

67%

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 grammatically complete with an explicit 'Use when' trigger and a list of review actions, but the actions are generic accessibility-review steps rather than skip-link-specific guidance, and the trigger surface ('rendered HTML, interactive components, design-system patterns') is broad enough to risk overlap with sibling accessibility skills.

Suggestions

Replace the generic a11y actions with skip-link-specific ones, e.g. 'Check that a Skip to main content link is the first focusable element, is visually hidden until focused, and moves focus to the main landmark on activation.'

Narrow the trigger surface from broad 'rendered HTML, interactive components, or design-system patterns' to skip-link-specific contexts to reduce conflict with sibling accessibility skills.

Add natural trigger variations users say, such as 'skip link', 'skip to main content', or 'bypass navigation'.

Dimension	Reasoning	Score
Specificity	Names the domain (accessibility/skip links) and a list of concrete inspection actions ('inspect keyboard behavior, focus flow, accessible names, and screen-reader output'), but the actions are generic a11y-review verbs rather than the specific skip-link checks this rule targets, so it stops short of listing multiple distinct concrete actions for this skill.	2 / 3
Completeness	It explicitly answers 'when' ('Use when reviewing rendered HTML... related to Include a skip navigation link') and 'what' ('Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output'), satisfying both halves with an explicit trigger clause.	3 / 3
Trigger Term Quality	Phrase 'Use when reviewing rendered HTML, interactive components, or design-system patterns' covers natural review triggers, and 'skip navigation link' is a term users would say, but common variations like 'skip link', 'skip to content', or 'bypass navigation' are absent, leaving coverage partial.	2 / 3
Distinctiveness Conflict Risk	The phrase 'rendered HTML, interactive components, or design-system patterns' is broad and could trigger for many accessibility skills in the same family, though tying it to 'skip navigation link' narrows it; the overlap with sibling a11y skills keeps it from being fully distinctive.	2 / 3
	Total	9 / 12 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-navigation/SKILL.md
Commit: 48405aa

Reviewed: about 8 hours 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.