CtrlK
BlogDocsLog inGet started
Tessl Logo

aria-hidden-body

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Do not use aria-hidden on the document body. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

76

Quality

96%

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

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-structured, lean overview for a simple single-rule skill: concise, actionable guidance with concrete values, a clear review/fix sequence, and an appropriately signaled one-level reference to the verified references/rule.md bundle file.

DimensionReasoningScore

Conciseness

The body is lean — a single-sentence rationale, tight Quick Reference bullets, and short Check/Fix/Explain/Code Review sections — with no padding of concepts Claude already knows, so every token earns its place.

3 / 3

Actionability

Gives concrete, specific guidance with exact attribute/element values ("Check if the <body> element has aria-hidden=\"true\"", "Remove aria-hidden=\"true\" from the <body> and use it only on specific background containers"); for an instruction-only skill the absence of code is not penalized since the guidance is actionable.

3 / 3

Workflow Clarity

As a simple single-purpose skill under 50 lines, it is clearly organized with a logical Check → Fix → Explain → Code Review sequence and no destructive/batch operation that would demand explicit validation checkpoints.

3 / 3

Progressive Disclosure

The body is a concise overview that signals a single one-level-deep reference — "see references/rule.md" — which exists in the bundle, with detail appropriately split out (code examples, why-it-matters, verification) into that file.

3 / 3

Total

12

/

12

Passed

Description

92%

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: concrete actions, natural trigger terms, and an explicit 'Use when' clause that answers both what and when. Its main weakness is distinctiveness, since the review trigger phrasing is generic across the accessibility-rule skill family and only the rule name narrows it.

Suggestions

Add a more distinctive trigger tied specifically to the rule, e.g. 'Use when you see aria-hidden on the <body> or when auditing modal/dialog focus management for screen-reader visibility.'

Lead with the specific violation (aria-hidden="true" on <body>) so the description is distinguishable from sibling accessibility-rule skills that share the generic 'reviewing rendered HTML' trigger.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output" — matching the anchor for several specific actions rather than vague language.

3 / 3

Completeness

Explicitly answers both what (check native semantics, inspect keyboard/focus/accessible-name/screen-reader output) and when ("Use when reviewing rendered HTML, interactive components, or design-system patterns..."), satisfying the explicit-trigger bar.

3 / 3

Trigger Term Quality

Uses natural phrasing a user would say — "reviewing rendered HTML, interactive components, or design-system patterns" and "aria-hidden on the document body" — giving good coverage of likely trigger terms.

3 / 3

Distinctiveness Conflict Risk

The trigger condition is shared across sibling accessibility rule skills (rendered HTML / interactive components / design-system patterns); differentiation relies mainly on the appended rule name, so it could still overlap with similar skills.

2 / 3

Total

11

/

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.