CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aria-valid-attr

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

Quality

73%

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-valid-attr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 well-structured and appropriately brief with clean progressive disclosure to a real reference file, but the in-body guidance itself is high-level: it names what to do without examples, tooling, or concrete invalid/valid attribute pairs. Mild redundancy across Quick Reference, Check, Fix, and Code Review sections dilutes an otherwise clean simple-skill layout.

Suggestions

Inline 2-3 concrete invalid-vs-valid attribute examples (e.g., `aria-labeledby` → `aria-labelledby`) in the Fix section so the skill is actionable without opening the reference.

Name the specific verification tooling once (e.g., axe DevTools or the W3C WAI-ARIA spec attribute list) in the Check or Code Review section instead of the generic "browser accessibility tooling".

Merge the Quick Reference bullets into Check/Fix (or drop them) to remove duplicated content and tighten the token budget.

DimensionReasoningScore

Conciseness

The body is short, but the opening sentence ("Invalid ARIA attributes are ignored by browsers and screen readers...") explains a concept Claude already knows, and the Quick Reference bullets ("Use only valid, standard-defined ARIA attributes") largely duplicate the Check/Fix sections. Mostly efficient, but it could be tightened by merging these redundant sections.

3 / 5

Actionability

Guidance like "Identify any invalid or misspelled ARIA attributes on HTML elements" and "Replace invalid ARIA attributes with their correct names as defined in the WAI-ARIA specification" is directionally concrete but incomplete — no tooling (axe, WAVE, browser devtools), no invalid-vs-valid attribute examples, and no inline spec lookup guidance, with all specifics deferred to references/rule.md. This lands between minimal high-level hints and executable guidance.

3 / 5

Workflow Clarity

For a simple single-purpose review skill, the Check → Fix → Explain sequence makes the core action (flag invalid attributes, supply correct names) reasonably unambiguous, and the Code Review section adds verification framing ("note how to verify the fix with browser accessibility tooling"). It loses a point because the relationship between Check and Code Review sections is unclear and there is no explicit post-fix re-validation step.

4 / 5

Progressive Disclosure

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`" — and references/rule.md exists in the bundle and covers exactly that. Content is appropriately split with easy navigation.

5 / 5

Total

15

/

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.

The description has a clear 'Use when...' trigger and a decent set of concrete review actions, but it never plainly states the core capability (identifying invalid/misspelled aria-* attributes per the WAI-ARIA spec) — that's obfuscated by splicing the rule name into the sentence. The broad frontend-review triggers plus generic a11y inspection terms create overlap risk with sibling accessibility skills.

Suggestions

Rewrite the 'what' as a plain capability statement, e.g., "Identifies invalid or misspelled aria-* attributes in rendered HTML and maps them to their valid WAI-ARIA counterparts", instead of the rule-name splice "related to Ensure ARIA attributes are valid".

Narrow the trigger to the skill's actual niche (e.g., "Use when auditing markup for ARIA correctness or when assistive-tech output suggests unrecognized aria-* attributes") to reduce conflict with sibling a11y checklist skills.

Add a couple of natural synonyms ("a11y", "WAI-ARIA", "aria-*") to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output" — which is a list of specific review behaviors. It stops short of 5 because the core capability itself (validating that aria-* attributes exist in the WAI-ARIA spec) is never stated as an action, only embedded via the rule-name splice "related to Ensure ARIA attributes are valid".

4 / 5

Completeness

Both parts are present: an explicit trigger ("Use when reviewing rendered HTML, interactive components, or design-system patterns related to...") and a what ("Check native semantics first, then inspect keyboard behavior..."). The 'what' is indirect — the actual capability is buried in the ungrammatical rule-name splice "related to Ensure ARIA attributes are valid" rather than stated as a plain capability verb — so it does not clearly and explicitly answer both at the 5-anchor level.

4 / 5

Trigger Term Quality

Good natural-term coverage for this domain: "rendered HTML", "interactive components", "design-system patterns", "keyboard behavior", "focus flow", "accessible names", "screen-reader output" — phrases a user doing accessibility review would say. A few natural variations are missing ("a11y", "accessibility audit", "WAI-ARIA", "aria-*"), keeping it below the comprehensive-anchor.

4 / 5

Distinctiveness Conflict Risk

The ARIA-validity niche is named, but the broad trigger clause "reviewing rendered HTML, interactive components, or design-system patterns" and the appended "keyboard behavior, focus flow, accessible names, and screen-reader output" make this description fire for nearly any frontend accessibility skill (keyboard-navigation, aria-roles, accessible-names rules), creating real overlap risk with closely related checklist rules.

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-valid-attr/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.