CtrlK
BlogDocsLog inGet started
Tessl Logo

aria-hidden-focus

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Remove focusable elements from aria-hidden containers. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

68

Quality

83%

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 concise, well-organized review skill body that defers detail appropriately to a real one-level reference and gives concrete attribute-level guidance. Minor redundancy and the lack of inline code examples keep it just short of top marks on conciseness and actionability.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, with only minor redundancy (the Quick Reference bullets restate the Check and Fix sections) and one brief motivational sentence; not a 5 because that redundancy could be trimmed.

4 / 5

Actionability

Gives concrete, executable guidance ('Add tabindex="-1"…or use the inert attribute', 'Flag exact elements, roles, labels, focus behavior') with specific attribute names; not a 5 because inline code examples are deferred to the reference rather than shown for the common cases.

4 / 5

Workflow Clarity

A clear Check → Fix → Explain → Code Review sequence is present and unambiguous; not a 5 because there are no explicit validation/feedback checkpoints, though this non-destructive review skill does not strictly require them.

4 / 5

Progressive Disclosure

The body is a well-organized overview with clearly signaled, one-level-deep navigation to references/rule.md ('see references/rule.md' for full details, code examples, and framework-specific guidance), and that reference file exists and is substantive.

5 / 5

Total

17

/

20

Passed

Description

87%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, well-structured description that gives concrete review actions and an explicit 'Use when' trigger tied to a distinct accessibility niche. Its only weakness is a slightly garbled phrase where the rule title is embedded as a noun clause.

DimensionReasoningScore

Specificity

Lists several concrete review actions ('Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output'); falls short of 5 because the embedded title phrase 'related to Remove focusable elements from aria-hidden containers' slightly muddies the action list.

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…') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good coverage of natural terms a reviewer would say ('rendered HTML', 'interactive components', 'design-system patterns', 'aria-hidden', 'keyboard behavior', 'screen-reader'); not a 5 because a few common synonyms (e.g., 'tab order', 'focusable') are absent.

4 / 5

Distinctiveness Conflict Risk

Targets a clear, narrow accessibility niche (focusable elements inside aria-hidden containers) with distinct triggers, making conflict with unrelated skills unlikely.

5 / 5

Total

18

/

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.

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.