CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tabindex

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Use appropriate tabindex values. 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/tabindex/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.

A well-structured, lean skill body: concrete tabindex rules in a scannable Quick Reference, a coherent check/fix/explain/review workflow, and a correctly delegated one-level reference file that exists and delivers the promised code examples. Weaknesses are minor: some redundancy between Quick Reference and the Check/Fix sections, and verification specifics left entirely to the reference file.

Suggestions

Merge the "Check" and "Fix" sections into the Quick Reference (or drop the prose restatement) to eliminate duplicated guidance.

Add one concrete detection step in the body, e.g. `grep -rnE 'tabindex="[1-9]'` or "run axe/Lighthouse", so the Check step is executable without opening the reference.

Surface one in-body verification checkpoint (e.g., "re-test tab order with keyboard-only navigation after fixing") instead of deferring all verification details to references/rule.md.

DimensionReasoningScore

Conciseness

The body is lean with no concept over-explanation, but the "Check" and "Fix" sections restate the Quick Reference bullets in prose form ("Avoid positive values... break natural tab order" vs "Remove positive tabindex values"), a minor trim opportunity that fits anchor 4 rather than anchor 5's 'every token earns its place'.

4 / 5

Actionability

Concrete guidance throughout: exact values (`tabindex="0"`, `tabindex="-1"`), explicit prohibition of positive values, and direct fix instructions, with code examples correctly delegated to references/rule.md (verified to exist and contain executable HTML). It stops short of anchor 5 because no method is given for finding violations (e.g., a grep pattern or axe/Lighthouse check) in the body itself.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sequence is clearly ordered and unambiguous, and the Code Review section signals verification ("note how to verify the fix with browser accessibility tooling or assistive tech"). Concrete verification steps live only in the reference file rather than the body, so it matches anchor 4 ('most checkpoints present; minor validation gaps') rather than anchor 5's explicit in-body validation steps.

4 / 5

Progressive Disclosure

A concise overview body with a single 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 with that content. Nothing that belongs in a separate file is inlined, matching anchor 5's clear overview with well-signaled references.

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.

A solid description with an explicit 'Use when' clause and several concrete inspection actions anchored to a specific accessibility niche. Its main flaws are a template-garbled trigger phrase ("related to Use appropriate tabindex values"), missing common synonyms like "tab order" and "keyboard navigation", and inspection-only actions with no fix/report verbs.

Suggestions

Fix the garbled template phrase "related to Use appropriate tabindex values" to read naturally, e.g. "related to tabindex usage" or "where tabindex values matter".

Add natural synonyms users would say, such as "tab order", "keyboard navigation", or "focus management", to broaden trigger matching.

Mention an outcome action beyond inspection (e.g., "flag and fix incorrect tabindex values") so the 'what' covers the full capability.

DimensionReasoningScore

Specificity

"Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output" names several specific inspection actions with concrete objects. It falls short of anchor 5 because the actions are all inspection verbs — no fix or reporting actions are stated — but exceeds anchor 3's '1-2 concrete actions'.

4 / 5

Completeness

Both a concrete 'what' ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output") and an explicit 'when' ("Use when reviewing rendered HTML, interactive components, or design-system patterns") are present. The trigger phrase "related to Use appropriate tabindex values" is grammatically garbled template text, keeping the 'when' from the fully concrete phrasing anchor 5 requires.

4 / 5

Trigger Term Quality

Strong natural keywords: "rendered HTML", "interactive components", "tabindex values", "keyboard behavior", "focus flow", "screen-reader". Missing common synonyms like "tab order", "keyboard navigation", and "accessibility", so it matches anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The tabindex/keyboard-focus niche is narrow with distinct triggers ("tabindex values", "focus flow", "screen-reader"), so conflict risk is low. Minor overlap remains with closely related accessibility skills (focus management, accessible names), matching anchor 4 rather than the minimal-conflict anchor 5.

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