CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

74%

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

Quality

Content

63%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 lean, well-structured overview with excellent progressive disclosure to a real, appropriately-scoped reference file. The main weaknesses are internal redundancy — Quick Reference, Check, Fix, and Explain restate the same points — and thin in-body actionability that defers all concrete code and verification tooling to the reference file. It also promises 'framework-specific guidance' in rule.md that the reference does not actually contain.

Suggestions

Merge the redundant Quick Reference, Check, and Fix sections into a single concise checklist (one line each for existence, position as first focusable element, visibility on focus, and target container ID) instead of restating the same guidance three times.

Add one minimal in-body code snippet (e.g. `<a href="#main-content" class="skip-link">Skip to main content</a>` plus the `:focus` reveal) so the Fix guidance is executable without opening the reference, or at least name the concrete verification tools (axe, Lighthouse, keyboard-only walkthrough) rather than 'browser accessibility tooling'.

Drop the 'Explain' section — it duplicates the intro sentence — and correct the reference pointer to only promise content rule.md actually delivers (code examples and details, not framework-specific guidance).

DimensionReasoningScore

Conciseness

The body is short but restates the same guidance three times: "Add a skip link as the first focusable element" (Quick Reference), "Verify if a skip link exists and is the first focusable element" (Check), and "Add a skip link that becomes visible on focus" (Fix), while the Explain section ("Explain how skip links benefit users who navigate via keyboard") duplicates the intro sentence. This fits 'mostly efficient but could be tightened' (3) — it is not severely or noticeably padded with concept explanations (2), but the redundancy is more than minor trimming (4).

3 / 5

Actionability

The body gives concrete-but-high-level review instructions ("Verify if a skip link exists and is the first focusable element", "Link it to the main content container ID") but contains no executable artifact — no markup example, selector, or verification command — deferring all code and tooling specifics (axe, Lighthouse, keyboard-testing steps) to references/rule.md. As an instruction-only skill the guidance is actionable in direction but incomplete in the body itself, matching the score-3 anchor 'some concrete guidance but incomplete' rather than the mostly-executable score-4 anchor.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review structure lays out a coherent review sequence, and verification is explicitly mentioned ("note how to verify the fix with browser accessibility tooling or assistive tech"), with full validation steps in references/rule.md. This is a non-destructive, simple review skill, so the feedback-loop cap does not apply; it sits at 4 because verification specifics are only implied/deferred and the repetitive Quick Reference/Check/Fix sections blur the sequence rather than making the single action unambiguously clear (5).

4 / 5

Progressive Disclosure

The body is a concise overview with one clearly 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 the code examples promised. This matches the score-5 anchor: clear overview, well-signaled single reference, easy navigation, no nested references.

5 / 5

Total

15

/

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 with an explicit 'Use when' clause and a sequence of concrete accessibility-review actions. Its main weaknesses are the awkward template-inserted phrase "related to Implement 'Skip to Content' links", generic trigger contexts that overlap with sibling accessibility skills, and missing common synonyms like 'skip navigation' or 'WCAG'.

DimensionReasoningScore

Specificity

The description lists several concrete review actions — "Check native semantics first", "inspect keyboard behavior, focus flow, accessible names, and screen-reader output" — with only minor coverage gaps (it never states what to do with findings, e.g. fix or flag). It names more than 1-2 concrete actions, fitting the score-4 anchor better than score 3, but is not comprehensive enough for score 5.

4 / 5

Completeness

Both parts are present: an explicit "Use when reviewing rendered HTML, interactive components, or design-system patterns..." trigger clause and a clear 'what' ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output"). It falls short of score 5 because the trigger contexts are broad and the embedded phrase "related to Implement 'Skip to Content' links" is awkward template phrasing rather than the crisp concrete triggers of the score-5 example; it is clearly above score 3 since 'when' is explicit, not weakly implied.

4 / 5

Trigger Term Quality

It includes natural phrases users would say such as "Skip to Content", "keyboard", "screen reader", "focus", and "interactive components". Common synonyms like "skip navigation", "bypass blocks", "a11y", or "WCAG" are missing, which fits 'good keyword coverage; a few natural terms missing' (4) rather than comprehensive synonym coverage (5) or sparse keywords (3).

4 / 5

Distinctiveness Conflict Risk

The embedded "Skip to Content" topic carves out a clear niche that is unlikely to trigger for unrelated skills. However, the generic trigger clause "reviewing rendered HTML, interactive components, or design-system patterns" would be shared verbatim by sibling accessibility checklist skills, creating more than minimal overlap risk with closely related skills — fitting 'mostly distinct; minor overlap risk' (4) rather than the fully distinct score-5 anchor.

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-link/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.