CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

80%

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

78%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 lean, well-structured review workflow that gives concrete rules and remediation values while correctly delegating code, framework guidance, and verification detail to a single clearly signaled reference file. Minor redundancy between Quick Reference and the Check/Fix sections, and the absence of inline verification checkpoints, keep conciseness, actionability, and workflow clarity just short of top marks. The bundle structure itself is exemplary progressive disclosure.

Suggestions

Consolidate the overlap between Quick Reference, Check, and Fix — e.g. merge Check and Fix into one section keyed to the five rules so each point appears once.

Mention verification in the reference pointer (e.g. "see references/rule.md for code examples, framework guidance, and automated/manual verification steps") so the checklist there is discoverable from the body.

DimensionReasoningScore

Conciseness

The ~40-line body is lean with no concept padding and assumes competence ("15% of users rely on keyboard navigation—broken focus order or keyboard traps make your site completely unusable"). Minor trim opportunity: the Check ("Test that all interactive elements are keyboard accessible, focus order matches visual/reading order...") and Fix ("Avoid positive tabindex values") sections restate the Quick Reference bullets, which keeps it below the every-token-earns-its-place 5 anchor but above the 3 anchor's unnecessary explanation.

4 / 5

Actionability

Gives concrete, specific guidance — "tabindex='-1'", "Never use positive tabindex values", "Ensure off-screen or display:none content cannot receive focus", "working Escape path" — so the absence of inline code in this instruction-only skill is not penalized. It sits below the 5 anchor only because no inline tooling commands or snippets are provided (they are delegated to references/rule.md).

4 / 5

Workflow Clarity

A clear Quick Reference → Check → Fix → Explain → Code Review sequence covers detection, remediation, communication, and reporting, with verification required ("note how to verify the fix with browser accessibility tooling or assistive tech"). Not the 5 anchor because the explicit step-by-step verification checklist lives only in references/rule.md rather than being surfaced as checkpoints in the workflow; not a destructive/batch skill, so no cap applies.

4 / 5

Progressive Disclosure

The body is a well-organized overview (rules, check, fix, explain, review) and delegates details via a single, clearly signaled, one-level-deep reference: "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — a file that exists in the bundle and contains exactly that (code examples, keyboard key table, verification steps). This matches the clear-overview with well-signaled one-level references pattern.

5 / 5

Total

17

/

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.

The description explicitly answers both what the skill does and when to use it, with several concrete inspection actions and good natural trigger terms centered on keyboard navigation. Its main weaknesses are the awkwardly embedded rule title inside the trigger clause and missing common synonyms like "a11y", "tab order", and "focus trap". Voice is imperative/neutral, consistent with the model examples, so no person-penalty applies.

Suggestions

Rewrite the trigger clause so the rule title reads naturally, e.g. "Use when reviewing rendered HTML, interactive components, or design-system patterns for keyboard navigation and focus behavior."

Add natural synonyms users would actually say — "a11y", "accessibility", "tab order", "focus trap" — to broaden trigger coverage.

Narrow "accessible names, and screen-reader output" to contexts where keyboard focus is directly affected, reducing overlap with sibling accessibility skills.

DimensionReasoningScore

Specificity

"Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output" lists several concrete inspection actions with only minor gaps (tab-order testing and trap detection are merely implied). It names more than the 1-2 actions of the 3 anchor but is not the comprehensive coverage of the 5 anchor.

4 / 5

Completeness

Both parts are explicit: what ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output") and when ("Use when reviewing rendered HTML, interactive components, or design-system patterns"). It falls short of the 5 anchor because the trigger clause embeds the rule title verbatim ("related to Enable keyboard navigation for all elements"), making the triggers less crisp and natural than the model example.

4 / 5

Trigger Term Quality

Includes strong natural terms users would say — "keyboard navigation", "rendered HTML", "interactive components", "focus flow", "screen-reader" — but misses common synonyms and variations such as "a11y", "accessibility", "tab order", and "focus trap". Coverage is good with a few natural terms missing, matching the 4 anchor rather than the comprehensive 5.

4 / 5

Distinctiveness Conflict Risk

The keyboard-navigation review niche is clear and distinct, but "accessible names, and screen-reader output" overlap with sibling accessibility rule skills, creating minor conflict risk. It is more distinct than the somewhat-overlapping 3 anchor but does not have the minimal-conflict clarity of the 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/keyboard-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.