CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tabs-accessibility

Use when reviewing templates, rendered HTML, or shared components related to Make tabs keyboard navigable. Validate the final browser-facing markup, not just the source framework abstraction.

Quality

75%

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/tabs-accessibility/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 well-structured, efficient overview with concrete ARIA and keyboard-interaction criteria and a clean one-level-deep pointer to a real reference file. Its only weaknesses are minor repetition between the Check/Fix/Quick Reference sections and the absence of an explicit post-fix re-validation step.

DimensionReasoningScore

Conciseness

The body is lean with no explanation of concepts Claude already knows, but there is minor redundancy — "Verify tabs use tablist/tab/tabpanel roles, aria-selected state..." in Check restates the Fix section's "role='tablist', role='tab', role='tabpanel', aria-selected...". Not 5 because that repetition could be trimmed.

4 / 5

Actionability

Concrete, attribute-level guidance ("roving tabindex", "Arrow keys navigate between tabs, Tab moves to panel", "aria-controls/aria-labelledby") with executable code in references/rule.md. Not 5 because details like arrow-key directions and Home/End handling are left implicit in the body.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sequence is clear and each phase is unambiguous for this single-purpose, non-destructive review skill. Not 5 because there is no re-check/validation step after applying a fix, leaving the loop implicit.

4 / 5

Progressive Disclosure

SKILL.md is a concise overview and full implementation details, code examples, and framework guidance are clearly signaled one level deep in references/rule.md, which exists in the bundle and contains the promised code examples. Content is appropriately split with easy navigation.

5 / 5

Total

17

/

20

Passed

Description

62%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 has an explicit and well-targeted "Use when" clause plus a useful validation directive, but it under-describes what the skill does and omits the accessibility/ARIA vocabulary users would most naturally use when invoking it. It is distinguishable from generic skills yet shares trigger phrasing with sibling frontend rules.

Suggestions

Add the natural accessibility vocabulary users say for this domain — e.g. "keyboard navigation", "ARIA", "accessibility", "tablist", "screen readers" — so the description triggers on those phrasings.

State the full capability set explicitly, e.g. "Check rendered markup for tablist/tab/tabpanel roles and roving tabindex, flag violations with exact elements and routes, and fix them" rather than only the validation directive.

Tighten the awkward embedded title ("related to Make tabs keyboard navigable") into a grammatical clause such as "related to making tabs keyboard navigable".

DimensionReasoningScore

Specificity

Names the domain and two concrete actions ("reviewing templates, rendered HTML, or shared components", "Validate the final browser-facing markup") but is not comprehensive — the body's fix/explain/code-review capabilities are absent. Not 4 because fewer than several specific actions are listed.

3 / 5

Completeness

An explicit "Use when reviewing..." clause answers "when" concretely, and "Validate the final browser-facing markup, not just the source framework abstraction" partially answers "what". Not 5 because the full capability set (check, fix, explain, review) is not stated; not 3 because "when" is explicit rather than weakly implied.

4 / 5

Trigger Term Quality

Relevant keywords ("templates", "rendered HTML", "shared components", "tabs", "keyboard navigable") are present, but the most natural phrasings for this domain — "accessibility", "ARIA", "a11y", "arrow keys", "tabindex", "screen reader" — are missing. Not 4 because the missing terms are central synonyms, not a few edge variations.

3 / 5

Distinctiveness Conflict Risk

The tabs-keyboard-navigability niche is clearly distinct with specific triggers, but the generic "reviewing templates, rendered HTML, or shared components" phrase overlaps with the whole family of frontend HTML review rules. Not 5 because of this minor overlap risk with closely related accessibility skills.

4 / 5

Total

14

/

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/tabs-accessibility/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.