aria-attribute-helper
Aria Attribute Helper - Auto-activating skill for Frontend Development. Triggers on: aria attribute helper, aria attribute helper Part of the Frontend Development skill category.
36
3%
Does it follow best practices?
Impact
98%
1.04xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/05-frontend-dev/aria-attribute-helper/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is extremely weak, consisting essentially of the skill name repeated as a trigger with no substantive information about capabilities or usage context. It provides no concrete actions, no natural trigger terms users would actually say, and no explicit guidance on when Claude should select this skill. It reads like auto-generated boilerplate rather than a useful skill description.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Adds appropriate ARIA roles, labels, and properties to HTML elements to improve accessibility for screen readers and assistive technologies.'
Add a 'Use when...' clause with natural trigger terms like 'accessibility', 'screen reader support', 'ARIA roles', 'aria-label', 'a11y', 'WAI-ARIA compliance', or 'make this accessible'.
Remove the duplicate trigger term and replace with varied, natural keywords users would actually use when needing help with ARIA attributes.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('aria attribute') but describes no concrete actions. There are no specific capabilities listed such as 'adds ARIA roles', 'validates ARIA labels', or 'generates accessible markup'. It is essentially just a title repeated. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the vague title, and the 'when' clause is just a repetition of the skill name rather than explicit trigger guidance. Both what and when are very weak. | 1 / 3 |
Trigger Term Quality | The only trigger term is 'aria attribute helper' repeated twice. It misses natural user phrases like 'accessibility', 'screen reader', 'ARIA roles', 'aria-label', 'a11y', 'WAI-ARIA', or 'accessible HTML'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'aria attribute' does narrow the domain somewhat compared to generic 'frontend development', but the lack of specificity about what it actually does could cause overlap with other accessibility or frontend skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell with no substantive content about ARIA attributes. It consists entirely of meta-descriptions and boilerplate that tell Claude what the skill supposedly does without providing any actual knowledge, code examples, or actionable guidance. Claude already knows more about ARIA attributes than this file teaches.
Suggestions
Replace the boilerplate with concrete ARIA attribute guidance: a quick-reference table of common roles (role='button', role='dialog', etc.), states (aria-expanded, aria-hidden), and properties (aria-label, aria-describedby) with HTML code examples.
Add executable code examples showing correct vs incorrect ARIA usage, e.g., a before/after for making a custom dropdown accessible.
Include a decision workflow: 'Does the native HTML element already convey semantics? → Don't add redundant ARIA. Is it a custom widget? → Follow WAI-ARIA Authoring Practices for that pattern.'
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill rather than teaching ARIA knowledge.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual knowledge about ARIA attributes. Every section restates the same vague idea. | 1 / 3 |
Actionability | There is zero concrete guidance—no code examples, no specific ARIA attributes, no HTML snippets, no rules for when to use which attribute. It describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or sequences. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of boilerplate with no references to detailed resources, no links to examples or reference files, and no meaningful structural organization of actual content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3076d78
- 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.