accessibility-audit-runner
Accessibility Audit Runner - Auto-activating skill for Frontend Development. Triggers on: accessibility audit runner, accessibility audit runner Part of the Frontend Development skill category.
33
0%
Does it follow best practices?
Impact
95%
1.02xAverage 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/accessibility-audit-runner/SKILL.mdQuality
Discovery
0%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 essentially a placeholder that restates the skill name and category without providing any meaningful information about capabilities, actions, or trigger conditions. It fails across all dimensions due to lack of concrete actions, absence of natural trigger terms, and no explicit 'Use when...' guidance.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Runs automated accessibility audits using axe-core, checks WCAG 2.1 compliance, identifies missing ARIA labels, evaluates color contrast ratios, and generates remediation reports.'
Add a 'Use when...' clause with natural trigger terms: 'Use when the user asks about accessibility testing, a11y audits, WCAG compliance, screen reader compatibility, ARIA attributes, contrast checks, or ADA compliance.'
Remove the redundant duplicate trigger term ('accessibility audit runner' listed twice) and replace with varied natural language terms users would actually use.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Accessibility Audit Runner') and its category ('Frontend Development') but lists no concrete actions like 'run axe-core scans', 'check WCAG compliance', 'identify ARIA issues', etc. It is entirely vague about what the skill actually does. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' clause is just a redundant repetition of the skill name rather than meaningful trigger guidance. Both dimensions are very weak. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'accessibility audit runner' repeated twice. It misses natural user phrases like 'a11y', 'WCAG', 'screen reader', 'accessibility check', 'ADA compliance', 'contrast ratio', etc. Users would rarely say 'accessibility audit runner' verbatim. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so generic ('Frontend Development' category, no specific actions or file types) that it could easily conflict with any other frontend or accessibility-related skill. Nothing distinguishes it clearly. | 1 / 3 |
Total | 4 / 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. It consists entirely of generic boilerplate that repeats the skill name without providing any actionable information about accessibility auditing—no tools (axe-core, Lighthouse, pa11y), no code examples, no workflows, no WCAG references. It would provide zero value to Claude in performing accessibility audits.
Suggestions
Add concrete, executable code examples for running accessibility audits using specific tools (e.g., axe-core, pa11y, Lighthouse CLI) with actual commands and code snippets.
Define a clear multi-step workflow: e.g., 1) Run automated scan, 2) Parse results, 3) Categorize by WCAG level, 4) Generate report—with validation at each step.
Remove all boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill meta-information rather than teaching how to do the task.
Add references to WCAG 2.1 success criteria levels and link to detailed guides for specific audit types (keyboard navigation, color contrast, ARIA patterns).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats the phrase 'accessibility audit runner' excessively, and provides zero substantive information about how to actually run an accessibility audit. | 1 / 3 |
Actionability | There are no concrete commands, code examples, tool references, or executable guidance whatsoever. The skill describes what it claims to do in abstract terms ('provides step-by-step guidance') without actually providing any guidance. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. There are no sequences, validation checkpoints, or any indication of how to actually perform an accessibility audit. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative page with no references to detailed materials, no links to tools or documentation, and no meaningful structure beyond generic boilerplate headings. | 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
c8a915c
- 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.