CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

focus-order

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

Quality

82%

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

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.

A compact, well-structured review skill whose body stays lean while delegating implementation detail to a real, clearly signaled reference file. Actionability and validation are solid, with the only gaps being repeated advice across sections and unnamed verification tooling.

Suggestions

Name specific verification tools or techniques (e.g., browser DevTools accessibility pane, tab-through inspection) in the Check or Code Review section instead of 'browser accessibility tooling'.

Deduplicate the positive-tabindex guidance between Quick Reference and Fix so each token earns its place.

Tighten the Explain section to avoid restating the intro sentence about disoriented keyboard users.

DimensionReasoningScore

Conciseness

Lean, well-sectioned body with no concept over-explanation, but the positive-tabindex advice repeats between Quick Reference and Fix, and the intro rationale sentence overlaps with the Explain section.

4 / 5

Actionability

Concrete guidance with real attribute values ('Never use positive tabindex values (1, 2, 3)', 'Use tabindex=0... tabindex=-1') and specific modal focus-trap/focus-return checks; only 'browser accessibility tooling' stays unnamed and generic.

4 / 5

Workflow Clarity

Clear Check → Fix → Explain → Code Review sequence where the Check section acts as validation, but verification guidance ('browser accessibility tooling or assistive tech') lacks named tools or commands, leaving minor validation gaps.

4 / 5

Progressive Disclosure

Under 50 lines with well-organized sections and a single clearly-signaled, one-level-deep reference ('For full implementation details... see references/rule.md') that exists and contains the promised code examples and framework guidance.

5 / 5

Total

17

/

20

Passed

Description

80%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 strong description that explicitly covers both what the skill does and when to use it, with mostly concrete actions and good keyword coverage. Main weaknesses are missing common trigger synonyms (tab order, tabindex, keyboard navigation) and overlap risk with sibling accessibility skills due to broadly shared trigger terms.

Suggestions

Add natural trigger synonyms such as 'tab order', 'tabindex', and 'keyboard navigation' so users' common phrasings match the description.

Rewrite the embedded rule title ('related to Ensure logical focus order') into natural language, e.g. 'related to logical focus and tab order', to improve readability and scoping.

Trim terms that belong to sibling accessibility rules (e.g. 'accessible names') or scope them explicitly to focus order to reduce conflict risk.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output') but coverage is check-only with no fixing/reporting actions, and the embedded rule title 'related to Ensure logical focus order' reads awkwardly.

4 / 5

Completeness

Explicitly answers both 'what' (check native semantics, inspect keyboard behavior, focus flow, accessible names, screen-reader output) and 'when' ('Use when reviewing rendered HTML, interactive components, or design-system patterns related to Ensure logical focus order') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural terms like 'focus order', 'keyboard behavior', 'focus flow', and 'screen-reader output', but misses common user phrasings such as 'tab order', 'tabindex', and 'keyboard navigation'.

4 / 5

Distinctiveness Conflict Risk

Broad trigger phrases like 'interactive components', 'accessible names', and 'screen-reader output' overlap with sibling accessibility rule skills; only the awkward 'related to Ensure logical focus order' clause scopes it to this specific rule.

3 / 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/focus-order/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.