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.

75

Quality

93%

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

87%

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 tight, well-organized overview that delegates detail to a single one-level-deep reference, with concrete actionable rules. The only gap is workflow clarity: the review sequence lacks explicit inline validation checkpoints, which are instead pushed to the reference file.

Suggestions

Add a short explicit numbered review sequence with verification checkpoints in the body (e.g., 1. Tab through all interactive elements in visual order, 2. Confirm hidden elements are not focusable, 3. Verify modal Escape paths) so the validation loop is visible without opening the reference.

Surface a one-line pointer to the verification tooling (axe/Lighthouse/manual checks) directly in the Check section rather than only in references/rule.md, so the feedback loop is discoverable from the overview.

DimensionReasoningScore

Conciseness

The body is lean and efficient — terse bullet Quick Reference and compact Check/Fix/Explain/Code Review sections with no padding or re-explanation of basic concepts Claude already knows, matching the score-3 anchor.

3 / 3

Actionability

Concrete, specific rules ('Never use positive tabindex values', 'removed from tab sequence with tabindex=-1', 'traps acceptable only inside active modals with a working Escape path') give directly actionable guidance; per scoring_notes the absence of inline code in this instruction-only skill is not penalized since the guidance is actionable.

3 / 3

Workflow Clarity

The Check section provides an implicit review sequence but lacks explicit validation checkpoints in the body itself (those are deferred to references/rule.md), matching the score-2 anchor of 'sequence present but checkpoints missing or implicit'.

2 / 3

Progressive Disclosure

Concise overview with a clearly signaled one-level-deep reference to references/rule.md (verified to exist, no nested references), matching the score-3 anchor for well-split content with easy navigation.

3 / 3

Total

11

/

12

Passed

Description

100%

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 strong: it gives concrete actions, natural trigger terms, an explicit 'Use when' clause, and a clearly scoped niche. It is concise without padding and reads in the correct third-person voice.

DimensionReasoningScore

Specificity

Lists multiple concrete review actions — 'Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output' — matching the score-3 anchor for several specific actions rather than a single domain mention.

3 / 3

Completeness

Explicitly answers both what (check semantics, inspect keyboard behavior/focus flow/accessible names/screen-reader output) and when via an explicit 'Use when reviewing rendered HTML...' trigger, satisfying the score-3 anchor.

3 / 3

Trigger Term Quality

Covers natural terms an accessibility reviewer would say ('rendered HTML, interactive components, design-system patterns', 'keyboard behavior, focus flow, accessible names, screen-reader output'), matching the good-coverage anchor.

3 / 3

Distinctiveness Conflict Risk

Scoped to keyboard-navigation accessibility review with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.