aria-required-children

Use when applies to custom ARIA widgets using composite roles: tablist, list, listbox, menu, menubar, tree, treegrid, grid, rowgroup, row, radiogroup. Use when reviewing components built with div/span elements that replace native HTML list, select, or nav elements.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/aria-required-children/SKILL.md

Quality

Content

71%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 content is a well-structured, actionable overview with excellent progressive disclosure to a real reference file. Its main weakness is moderate verbosity and redundancy across the Quick Reference, Check, and Explain sections, plus verification guidance that is lighter than the checking workflow warrants.

Suggestions

Collapse the repeated container→child role mappings so they appear in one authoritative place (Quick Reference or Check) rather than restated across Quick Reference, Check, and Explain.

Trim the Explain section's background on what WAI-ARIA required owned elements are — Claude already knows this — and keep only the rule-specific distinction from aria-required-parent.

Add a brief inline verification checkpoint in the Check or Code Review section (e.g., inspect the accessibility tree / run axe) so the review workflow has an explicit validation step in the body.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and well-structured, but the Explain section rehashes WAI-ARIA required-owned-elements concepts Claude already knows, and the container→child mappings are restated across Quick Reference, Check, and Explain, so it could be tightened.	3 / 5
Actionability	Concrete, specific guidance throughout: explicit role mappings (tablist→tab, list→listitem, etc.) and a Fix section with executable steps (add role='tab', role='none' on wrappers, prefer <ul>/<li>); no inline code examples, but they are appropriately delegated to references/rule.md and the guidance is actionable for an instruction/review skill.	4 / 5
Workflow Clarity	A clear Check→Fix→Explain→Code Review sequence with a defined inspection procedure and numbered remediation steps; verification is only lightly addressed in the body ('note how to verify the fix'), a minor gap that keeps it below 5.	4 / 5
Progressive Disclosure	The body is a well-organized overview (Quick Reference, Check, Fix, Explain, Code Review) that points to one clearly signaled, one-level-deep reference (references/rule.md) which exists in the bundle and holds the code examples and framework guidance — easy to navigate.	5 / 5
	Total	16 / 20 Passed

Description

56%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 excels at trigger guidance and niche distinctiveness but is framed almost entirely as 'Use when...' clauses, leaving the skill's concrete capabilities unstated. Adding an explicit 'what' statement would lift completeness and specificity.

Suggestions

Lead with a concrete capability statement, e.g. 'Verifies ARIA container roles contain their required child roles and fixes invalid nesting', before the 'Use when' triggers.

Name the concrete actions the skill performs (flag missing required children, add role attributes to children, apply role='none' to wrappers) rather than only describing when it applies.

Tighten the opening 'Use when applies to' phrasing, which is grammatically awkward as a trigger clause.

Dimension	Reasoning	Score
Specificity	The description thoroughly lists the domain (composite role names: tablist, list, listbox, menu, etc.) but concrete actions are minimal and generic — only 'applies to' and 'reviewing components' appear, with no enumeration of what the skill actually does (verify required children, fix nesting).	2 / 5
Completeness	The 'when' is explicit (two 'Use when...' clauses with concrete triggers), but the 'what' is only weakly implied through 'applies to' and 'reviewing' — the skill's actual capability (verifying/fixing required child roles) is never stated, so it does not reach the both-what-and-when anchors.	3 / 5
Trigger Term Quality	Strong natural keyword coverage via explicit 'Use when' clauses naming role tokens (tablist, menu, tree, listbox) and native HTML equivalents (list, select, nav) plus 'div/span elements' that reviewers would naturally say; falls short of 5 only because it is a token list rather than varied phrasings.	4 / 5
Distinctiveness Conflict Risk	Carves a clear niche (ARIA required-children for composite widget roles) with a specific role list, giving minimal conflict risk; minor overlap with the sibling aria-required-parent skill keeps it just below 5.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/aria-required-children/SKILL.md
Commit: 30756a7

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

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.