aria-allowed-attr

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Use only allowed ARIA attributes for each role. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

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-allowed-attr/SKILL.md

Quality

Content

42%

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

The skill body is a lean, well-decoupled overview pointing to a real reference file, but the in-body guidance is abstract and template-like with no executable examples or an explicit review/verify feedback loop. Most of the actual instructional value is deferred to the reference, leaving the SKILL.md itself thin on actionability.

Suggestions

Add a small concrete example in the body — e.g. a short HTML snippet showing an invalid aria attribute on a role with the corrected markup — so the guidance is actionable without opening the reference.

Turn the 'Check'/'Code Review' sections into an explicit sequence: inspect role → list supported attributes → flag violations → apply fix → re-verify with accessibility tooling.

Include a compact allowed-attributes-by-role reference table or a pointer to the canonical ARIA spec section so the verify step has a concrete source of truth.

Dimension	Reasoning	Score
Conciseness	The body is short and free of concept explanation padding, but it largely restates the rule abstractly across Quick Reference, Check, Fix, Explain, and Code Review sections with minimal unique information per section.	2 / 3
Actionability	No executable code, concrete commands, or an allowed-attributes/roles table appear; guidance like 'Verify that all ARIA attributes used on elements are valid' and 'Remove or correct ARIA attributes' describes rather than instructs.	1 / 3
Workflow Clarity	Sections are present but there is no sequenced review workflow with validation checkpoints; for a review task the detect-violation → fix → re-verify feedback loop is only implied, never made explicit.	2 / 3
Progressive Disclosure	The body is a concise overview that signals a single one-level-deep reference (references/rule.md, which exists) plus a source URL, matching the expected split between overview and detail.	3 / 3
	Total	8 / 12 Passed

Description

85%

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 clearly states what the skill does and when to use it, with concrete review actions and a distinct accessibility niche. The main weakness is trigger-term phrasing, where the literal rule title is stitched into the prose and common ARIA/accessibility keywords are underrepresented.

Suggestions

Rewrite the trigger clause to use natural phrasing a user would say, e.g. 'Use when auditing accessibility, reviewing ARIA attributes and roles, or checking interactive components for screen-reader compatibility.'

Surface the keyword 'ARIA' earlier and add common variations like 'accessibility audit', 'ARIA roles', and 'screen reader' as explicit trigger terms.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output' — rather than vague language.	3 / 3
Completeness	Explicitly answers both what ('Check native semantics... inspect keyboard behavior, focus flow, accessible names, and screen-reader output') and when ('Use when reviewing rendered HTML, interactive components, or design-system patterns'), in third person.	3 / 3
Trigger Term Quality	Includes some natural terms ('reviewing rendered HTML, interactive components, design-system patterns') but the embedded rule title is awkward and misses common variations like 'ARIA', 'accessibility audit', or 'screen reader' as standalone triggers.	2 / 3
Distinctiveness Conflict Risk	Scoped narrowly to allowed-ARIA-attributes-per-role validation, a clear niche unlikely to trigger for unrelated skills.	3 / 3
	Total	11 / 12 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-allowed-attr/SKILL.md
Commit: 48405aa

Reviewed: about 8 hours 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.