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
Quality
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 severely underdeveloped, essentially just restating the skill name without explaining capabilities or use cases. It lacks concrete actions, natural trigger terms, and explicit guidance on when Claude should select this skill. The redundant trigger terms and missing 'Use when...' clause make it nearly unusable for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Generates appropriate ARIA attributes for HTML elements, validates existing ARIA usage, suggests accessibility improvements for interactive components.'
Include a 'Use when...' clause with natural trigger terms: 'Use when the user asks about accessibility, ARIA roles, screen reader support, a11y, or making HTML elements accessible.'
Add common file types or contexts: 'Works with HTML, JSX, Vue templates, or any markup requiring accessibility attributes.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Aria Attribute Helper' without describing any concrete actions. There are no verbs or specific capabilities listed - it doesn't explain what the skill actually does with ARIA attributes. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when to use' guidance. There is no explicit trigger clause or use case explanation. | 1 / 3 |
Trigger Term Quality | The only trigger terms are 'aria attribute helper' repeated twice, which is redundant and unlikely to match natural user queries. Missing natural terms like 'accessibility', 'a11y', 'screen reader', 'ARIA roles', or 'accessible HTML'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'ARIA attributes' is a specific domain within frontend development, the lack of detail about what operations it performs could cause overlap with general accessibility or HTML skills. The category mention provides some context. | 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 essentially a placeholder template with no actual instructional content. It describes what an ARIA helper skill would do without providing any concrete guidance on ARIA attributes, accessibility patterns, or implementation details. The entire content is meta-description rather than actionable instruction.
Suggestions
Replace the generic description with actual ARIA attribute examples and usage patterns (e.g., aria-label, aria-describedby, aria-live with concrete code snippets)
Add executable code examples showing correct ARIA implementation in React/Vue components
Include a quick reference table of common ARIA attributes with their purposes and valid values
Provide validation guidance or tools for checking ARIA implementation correctness
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance, no code examples, no actual ARIA attributes explained, and no executable instructions. The skill describes what it does rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequences, and no validation checkpoints. The content only lists vague 'capabilities' without any process guidance. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no structure pointing to actual resources, examples, or reference materials. No useful navigation or content organization exists. | 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
994edc4
- 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.