CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

66

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 tight, well-organized review-checklist skill that defers detail to a single existing reference file with clear navigation. It is concise and well-disclosed; the only gap is the absence of inline verification checkpoints in the body itself.

DimensionReasoningScore

Conciseness

Lean, well-sectioned body with no padding or basic-concept explanation; every line (Quick Reference, Check, Fix, Explain, Code Review) earns its place.

5 / 5

Actionability

Concrete checks ('every element with role="dialog" or role="alertdialog" has an accessible name') and concrete fixes ('aria-labelledby pointing to the header or aria-label'); executable examples are deferred to the reference rather than inline.

4 / 5

Workflow Clarity

The Check→Fix→Explain→Code Review sections form a clear review sequence, but the body lacks explicit verification checkpoints (those live in references/rule.md), keeping it below 5.

4 / 5

Progressive Disclosure

A concise overview body with a clearly signaled one-level-deep pointer ('see references/rule.md') to an existing reference file that holds the detail; easy to navigate.

5 / 5

Total

18

/

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.

The description is well-structured with an explicit trigger clause and concrete review actions, but a templated bookish phrase ('related to Ensure dialogs have an accessible name') slightly undermines natural trigger phrasing. It scores consistently at 4 across dimensions.

Suggestions

Reword the templated fragment 'related to Ensure dialogs have an accessible name' into natural user phrasing, e.g. 'related to ensuring dialogs have an accessible name'.

Lead with the concrete 'what' before the 'when' so the skill's purpose is immediately clear.

DimensionReasoningScore

Specificity

Lists several concrete actions ('inspect keyboard behavior, focus flow, accessible names, and screen-reader output') with only minor coverage gaps, sitting above the 1-2 action anchor.

4 / 5

Completeness

Both 'what' (review these aspects of dialog naming) and 'when' (explicit 'Use when reviewing rendered HTML...') are present; the 'what' could be more tightly tied to a single concrete outcome.

4 / 5

Trigger Term Quality

Good natural-term coverage ('rendered HTML', 'interactive components', 'design-system patterns', 'accessible name'), but the templated phrase 'related to Ensure dialogs have an accessible name' reads unnaturally and keeps it below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Scoped to accessible-name checks on dialogs, making it mostly distinct from sibling accessibility skills with only minor overlap risk.

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.

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.