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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill aria-attribute-helperOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder with no substantive content. It only provides a skill name and category without explaining what the skill does, what actions it performs, or when it should be selected. The repeated trigger term is the skill name itself, which provides no useful matching criteria.
Suggestions
Add specific actions the skill performs, e.g., 'Suggests appropriate ARIA attributes, validates ARIA usage, adds aria-labels and roles to HTML elements'
Include a 'Use when...' clause with natural trigger terms like 'accessibility', 'a11y', 'screen reader support', 'ARIA roles', 'aria-label', 'aria-describedby'
Describe the scope clearly to distinguish from general accessibility or frontend skills, e.g., 'specifically for adding and validating ARIA attributes in HTML/JSX components'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. 'Aria Attribute Helper' is just a name, not a description of what it does. There are no verbs describing capabilities like 'adds', 'validates', 'suggests', etc. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no 'Use when...' clause or equivalent guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'aria attribute helper' repeated twice, which is the skill name itself rather than natural user language. Missing obvious terms like 'accessibility', 'a11y', 'screen reader', 'ARIA roles', 'aria-label', etc. | 1 / 3 |
Distinctiveness Conflict Risk | While 'aria attribute' is somewhat specific to accessibility work, the lack of detail about what the skill actually does makes it unclear how it differs from general accessibility or frontend development skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual substance. It contains no information about aria attributes, no code examples, no accessibility guidance, and no actionable instructions. The entire content could be replaced with a single sentence saying 'this skill helps with aria attributes' and convey the same (lack of) information.
Suggestions
Add concrete aria attribute examples with code snippets showing proper usage (e.g., aria-label, aria-describedby, aria-hidden) in HTML/JSX context
Include a quick reference table of common aria attributes, their purposes, and when to use each one
Provide executable code examples showing before/after accessibility improvements with aria attributes
Add links to detailed references for complex aria patterns like live regions, dialogs, and custom widgets
| 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 attribute information, 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 unhelpful text with no references to detailed materials, no links to examples, and no structured navigation to actual aria attribute documentation. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.