CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aria-required-parent

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Ensure ARIA roles are contained by required parent roles. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

Quality

69%

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-required-parent/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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 brief, well-sectioned overview with an appropriate one-level-deep reference, but it carries redundant restatements (Quick Reference, Explain) and its guidance stays high-level — the concrete verification steps and code examples all live in references/rule.md while the body itself gives neither a checking method nor an inline example. Sequencing of check → fix → verify is implied by section order rather than stated.

Suggestions

Merge the Quick Reference bullets into the Check/Fix sections (they restate the intro) and either concretize or drop the vague "Explain" section.

Inline one minimal verification step (e.g. "run axe-core or inspect the browser accessibility tree for the orphaned role") so the Check section states how, not just what — currently all verification detail is deferred to the reference.

Align the references/rule.md pointer with the file's actual contents (it holds the code example, rationale, exceptions, and verification steps, not the promised "framework-specific guidance").

DimensionReasoningScore

Conciseness

The body is short and mostly efficient, but the "Quick Reference" bullets ("Certain roles (like listitem) must be owned by specific parent roles (like list)") restate the intro paragraph and the Check section, and the one-line "Explain" section adds no new information. This is more than the minor trimmable instances of the 4 anchor, but well short of the padded sections of the 2 anchor.

3 / 5

Actionability

Some concrete guidance is present — named roles to check ("listitem, tab, or menuitem") and a specific fix example ("wrap role=\"listitem\" in role=\"list\"") — but there is no code example, command, or verification method in the body itself; the Check section says only "verify that elements... are correctly nested" without how, and the concrete steps (axe, accessibility tree) live in the reference. This fits the 3 anchor (some concrete guidance but incomplete, missing key details) rather than 4, which requires concrete code or commands with only minor gaps.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections imply a rough sequence, but it is never explicitly ordered and validation is only vaguely gestured at ("note how to verify the fix with browser accessibility tooling or assistive tech") without a checkpoint or feedback loop in the body. This matches the 3 anchor (sequence present but checkpoints missing or implicit); the simple-skill 5 exception does not apply because check-then-fix-then-verify is a multi-step flow whose verification step is delegated entirely to the reference.

3 / 5

Progressive Disclosure

The body is a compact overview with clear sections and a well-signaled, verified one-level-deep reference ("see `references/rule.md`", which exists and contains the code examples, rationale, and verification detail — no nested references). Not 5 because the pointer slightly over-promises: it advertises "framework-specific guidance" and "full implementation details" that references/rule.md does not actually contain, a minor navigation-accuracy gap matching the 4 anchor.

4 / 5

Total

13

/

20

Passed

Description

71%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 serviceable description with an explicit "Use when" trigger and several concrete inspection actions, but it leans on generic accessibility-review boilerplate rather than stating the rule's own capability (verify and fix ARIA required-parent nesting). The rule title is grammatically jammed into the trigger clause, and the most natural term "accessibility" never appears.

Suggestions

State the rule-specific capability as a direct action, e.g. "Verifies that ARIA child roles (menuitem, tab, listitem) are nested within their required parent roles and wraps orphaned elements in the proper container."

Add the natural trigger terms "accessibility" and "a11y" plus the concrete role names (menu, menuitem, tab, tablist, list, listitem) that users would actually mention.

Rewrite the trigger clause so the rule title is not embedded mid-sentence ("related to Ensure ARIA roles are contained by required parent roles" reads as an inserted heading, not a natural phrase).

DimensionReasoningScore

Specificity

The description lists several concrete inspection actions — "Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output" — naming the domain (ARIA roles, rendered HTML) with concrete verbs. It falls short of 5 because the rule's own core actions (verifying role nesting, wrapping orphans in their required parents) are only conveyed through the awkwardly embedded rule title, and the fix action is absent; it sits above 3 because more than 1-2 concrete actions are explicitly stated.

4 / 5

Completeness

Both parts are present: an explicit "Use when reviewing rendered HTML, interactive components, or design-system patterns related to..." trigger clause, and a "what" expressed through the check/inspect actions. Not 5 because the "what" is not cleanly stated — the rule's purpose is jammed grammatically into the "when" clause ("related to Ensure ARIA roles are contained by required parent roles") rather than declared as a clear capability sentence.

4 / 5

Trigger Term Quality

Good natural-term coverage: "rendered HTML", "interactive components", "design-system patterns", "ARIA roles", "keyboard", "focus", "accessible names", "screen-reader output" — phrases a reviewer would plausibly say. It misses the most common synonyms "accessibility"/"a11y" and the concrete role names (menuitem, tab, listitem) that users would mention, keeping it below the 5 anchor's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The embedded rule name ("Ensure ARIA roles are contained by required parent roles") is specific, but the surrounding boilerplate ("Use when reviewing rendered HTML, interactive components, or design-system patterns... Check native semantics first, then inspect keyboard behavior...") is generic accessibility-review text that would apply equally to a whole family of sibling ARIA rule skills, creating real overlap risk. Not 4 because the shared boilerplate trigger means many closely related skills would fire simultaneously; not 2 because the rule title does carve out a distinct niche.

3 / 5

Total

15

/

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-required-parent/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.