CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aria-dialog-name

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

Quality

76%

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/aria-dialog-name/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-organized, concise overview with concrete role/attribute guidance and an exemplary one-level-deep pointer to the verified references/rule.md bundle file. Its main weaknesses are internal redundancy between Quick Reference, Check, and Fix sections, a filler Explain section, and generic verification guidance that never names a specific accessibility tool.

Suggestions

Collapse the redundant Quick Reference, Check, and Fix sections into one statement-plus-remediation block, and drop or merge the filler Explain section to tighten conciseness.

Name a concrete verification step, e.g., "Confirm the fix by inspecting the element's accessible name in the browser DevTools accessibility tree or with a screen reader," to close the workflow gap.

Inline one minimal correct/incorrect HTML snippet (e.g., role='dialog' with aria-labelledby vs. an unnamed dialog) in the body so the fix is executable without opening the reference.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence ("Verify that every element with role=dialog or role=alertdialog has an accessible name"), but the Check and Fix sections largely repeat the Quick Reference bullets, and the Explain section ("Explain why naming dialogs is crucial...") adds little actionable content. These minor redundancies fit the anchor for efficient content with trimmable over-explanation, not the 5 where every token earns its place.

4 / 5

Actionability

For an instruction-only skill the guidance is concrete: exact roles ("role='dialog' or role='alertdialog'"), exact remediation attributes ("aria-labelledby (pointing to the header) or aria-label"), and a clearly signaled pointer to executable code examples in references/rule.md (verified to exist, 58 lines with correct/incorrect HTML examples). Not a 5 because the body itself contains no code snippet and verification guidance stays generic ("browser accessibility tooling") without naming a specific tool.

4 / 5

Workflow Clarity

As a simple single-task review skill under 50 lines, the Check → Fix → Explain → Code Review structure gives an unambiguous sequence with the check and remediation clearly ordered. Not a 5 because the verification step is vague ("browser accessibility tooling or assistive tech" without naming e.g. the DevTools accessibility tree or axe), leaving a minor checkpoint gap.

4 / 5

Progressive Disclosure

The body is a concise overview with a single well-signaled, one-level-deep reference ("For full implementation details, code examples, and framework-specific guidance, see references/rule.md") whose path matches the actual bundle file. Content is appropriately split between the overview and the reference, and navigation is easy — matching the clear-overview anchor with correctly structured references.

5 / 5

Total

17

/

20

Passed

Description

63%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 answers both what and when with an explicit Use-when clause and several concrete review actions, but suffers from awkward template phrasing and missing high-frequency natural terms like "modal", "aria", and "role=dialog". Its generic review-skill trigger framing creates real conflict risk with sibling accessibility-rule skills sharing the same boilerplate.

Suggestions

Rewrite the when-clause to use natural phrasing, e.g., "Use when reviewing HTML or rendered components containing dialogs, modals, alertdialogs, or role='dialog' elements that may lack an accessible name (aria-labelledby / aria-label)."

Add the natural synonyms users actually say — "modal", "popup", "aria-labelledby", "aria-label", "role=dialog" — to improve trigger-term coverage and distinctiveness.

Differentiate this skill from sibling aria/accessibility rules by front-loading the dialog-specific trigger instead of the shared "rendered HTML, interactive components, or design-system patterns" boilerplate.

DimensionReasoningScore

Specificity

The description lists several concrete actions ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output"), with minor gaps such as the grammatically awkward phrase "related to Ensure dialogs have an accessible name". It is not a comprehensive 5 because the actions are generic review activities rather than a complete enumeration of the skill's capabilities.

4 / 5

Completeness

Both what ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output") and when ("Use when reviewing rendered HTML, interactive components, or design-system patterns related to...") are explicitly present. Not a 5 because the when-clause is awkwardly phrased ("related to Ensure dialogs have an accessible name") and the what-side actions are generic; not a 3 because the Use-when trigger is explicit rather than weakly implied.

4 / 5

Trigger Term Quality

Keywords like "rendered HTML", "interactive components", "dialogs", "accessible name", and "screen-reader" are relevant, but common natural terms users would say are missing: "modal", "popup", "aria-labelledby", "role=dialog", or "alertdialog". This matches the anchor for some relevant keywords missing common variations or synonyms, rather than 4, where only a few natural terms would be missing.

3 / 5

Distinctiveness Conflict Risk

The trigger phrase "reviewing rendered HTML, interactive components, or design-system patterns related to X" would be shared nearly verbatim by sibling accessibility-rule skills from the same source (e.g., other aria-* checks), so it could overlap with closely related skills. Only the tail of the sentence differentiates this skill from its siblings, which fits the "somewhat specific but could still overlap with similar skills" anchor rather than 4's "minor overlap risk".

3 / 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/aria-dialog-name/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.