CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%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.

A well-structured, lean skill body: concrete quick-reference bullets, an unambiguous check/fix/explain workflow with a validation step, and a clean handoff to a real one-level-deep reference. The only minor improvements are trimming the one why-it-matters restatement and surfacing a minimal inline code example.

DimensionReasoningScore

Conciseness

The body is lean and directive with only minor trimmable content: the opening "Skip links save keyboard and screen reader users from tabbing through 50+ navigation items" sentence and the "Explain" section restate a concept Claude already knows. Everything else — Quick Reference, Check, Fix, Code Review — earns its tokens.

4 / 5

Actionability

As an instruction-only skill the absence of inline code is not penalized, and the guidance is concrete: "first focusable element", "id='main-content'", "Hide visually but show on focus with CSS", "Test by pressing Tab immediately after page load". It is not a 5 because the executable HTML/CSS specifics are deferred entirely to the reference rather than having even a minimal inline example.

4 / 5

Workflow Clarity

This is a simple single-purpose skill under 50 lines with an unambiguous Check → Fix → Explain sequence and an explicit validation step ("Test by pressing Tab immediately after page load"). The simple-skill exception applies and no destructive/batch-operation cap is relevant.

5 / 5

Progressive Disclosure

The body is a clear overview with a well-signaled, one-level-deep reference — "For full implementation details, code examples, and framework-specific guidance, see references/rule.md" — and the referenced file exists and contains exactly that material. Content is appropriately split between overview and reference.

5 / 5

Total

18

/

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 that explicitly names a specific accessibility rule and enumerates concrete inspection actions with an explicit Use-when clause. Its main weaknesses are the missing natural trigger synonyms ("skip link", "skip to main content") and the awkward rule-title insertion into the when-clause.

Suggestions

Add natural trigger synonyms users would actually say, e.g. "...related to skip navigation links (skip links, 'skip to main content', bypass navigation)."

Rewrite the awkward title embedding so the when-clause reads naturally, e.g. "Use when reviewing rendered HTML, interactive components, or design-system patterns for a skip navigation link (skip link)."

Briefly mention the fix/explain side of the skill's work (e.g. "...and guide the fix with HTML/CSS examples") so the what-coverage is comprehensive.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output" — matching the anchor for several specific actions with minor gaps. It is not a 5 because it covers only the review/inspection side and omits the fix and explain actions the skill also performs.

4 / 5

Completeness

Both what ("Check native semantics... inspect keyboard behavior, focus flow, accessible names, and screen-reader output") and when ("Use when reviewing rendered HTML, interactive components, or design-system patterns") are explicitly present. It falls short of 5 because the when-clause is awkwardly phrased ("related to Include a skip navigation link") and lacks concrete user-mention triggers.

4 / 5

Trigger Term Quality

Good keyword coverage including "skip navigation link", "rendered HTML", "keyboard behavior", "focus flow", and "screen-reader output", but common variations users would naturally say — "skip link", "skip to main content", "bypass navigation", "a11y/accessibility" — are missing. Not a 3 because the core natural terms are present and well-chosen.

4 / 5

Distinctiveness Conflict Risk

The "skip navigation link" trigger carves out a clear niche with minimal conflict risk, but the broad generic framing ("reviewing rendered HTML... Check native semantics... keyboard behavior, focus flow, accessible names") overlaps with other accessibility-review skills. Mostly distinct with minor overlap risk, rather than the clean niche of a 5.

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/skip-navigation/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.