CtrlK
BlogDocsLog inGet started
Tessl Logo

keyboard-navigation

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

59

Quality

68%

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/keyboard-navigation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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 competently structured review skill: a concise overview with clear sections and a clean one-level reference into rule.md. It is held back by redundancy across Quick Reference/Check/Fix, motivational padding, and verification steps that live only in the reference rather than the body.

Suggestions

Collapse the Check/Fix/Explain sections into the Quick Reference or move them into references/rule.md to remove paraphrase redundancy and tighten conciseness.

Add an explicit in-body verification checkpoint (e.g. 'run axe/Lighthouse on a representative rendered state; confirm Tab traverses all interactive elements in visual order') so the workflow has a concrete validation step.

Drop the '15% of users rely on keyboard navigation' motivational opener — it explains a concept Claude already knows and earns no token budget.

DimensionReasoningScore

Conciseness

The Quick Reference bullets are lean, but the Check/Fix/Explain sections largely paraphrase them and the "15% of users rely on keyboard navigation" opener is motivational padding Claude does not need; could be tightened. Not verbose enough to drop to 2.

3 / 5

Actionability

Concrete rules appear (tabindex='-1', no positive tabindex, Tab reachability), but the actual verification tooling and code examples are deferred to references/rule.md, leaving the body's guidance incomplete for execution. Not minimal enough for 2, not complete enough for 4.

3 / 5

Workflow Clarity

A loose Check → Fix → Explain → Code Review sequence is present, but there is no explicit validation/verification checkpoint in the body (verification lives only in the reference), so checkpoints are implicit rather than stated.

3 / 5

Progressive Disclosure

The body is a well-sectioned overview with a clearly signaled, one-level-deep pointer to the real references/rule.md for full details and code; minor gap is mild redundancy between Quick Reference and Check/Fix rather than a fully clean split.

4 / 5

Total

13

/

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.

A well-constructed description with an explicit Use-when trigger and a concrete list of review actions; it is specific, actionable, and clearly scoped to keyboard-navigation accessibility. Main weakness is slightly broad review framing that risks overlap with adjacent a11y skills.

DimensionReasoningScore

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; not a fully comprehensive action list so it stops short of 5.

4 / 5

Completeness

Explicitly answers both: the "what" (check semantics, inspect keyboard behavior/focus/accessible names/screen-reader output) and the "when" via a concrete "Use when reviewing rendered HTML, interactive components, or design-system patterns..." trigger clause.

5 / 5

Trigger Term Quality

Strong natural terms a reviewer would say ("rendered HTML", "interactive components", "design-system patterns", "keyboard navigation", "screen-reader"), though a few common synonyms (e.g. "a11y", "focus order") are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear keyboard-navigation accessibility niche with distinct triggers, but the broad "reviewing rendered HTML / interactive components / design-system patterns" framing could overlap with sibling accessibility review skills.

4 / 5

Total

17

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.