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.
35
Quality
3%
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
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 essentially a placeholder with no substantive content. It repeats the skill name as triggers, provides no concrete actions or capabilities, and lacks any 'Use when...' guidance. The description would fail to help Claude distinguish this skill from others or know when to select it.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Runs automated accessibility audits using axe-core, identifies WCAG 2.1 violations, generates remediation reports'
Include a 'Use when...' clause with natural trigger terms like 'accessibility check', 'a11y audit', 'WCAG compliance', 'screen reader testing', 'accessibility issues'
Remove the duplicate trigger term and expand with variations users would naturally say: 'accessibility scan', 'ADA compliance check', 'audit for accessibility'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Accessibility Audit Runner') without describing any concrete actions. There are no specific capabilities listed like 'runs axe-core scans', 'identifies WCAG violations', or 'generates accessibility reports'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when to use' guidance. It only states it's part of Frontend Development category without explaining functionality or use cases. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('accessibility audit runner, accessibility audit runner'). Missing natural user terms like 'a11y', 'WCAG', 'screen reader', 'accessibility check', 'ADA compliance', or 'accessibility issues'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'accessibility audit' is somewhat specific to a niche domain, but without concrete actions or clear triggers, it could overlap with general accessibility skills or testing tools. 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 content is entirely placeholder boilerplate with no actual substance. It contains zero actionable information about accessibility auditing - no tools, no code examples, no audit processes, no WCAG guidelines, and no concrete guidance. The content would be completely useless for helping Claude perform accessibility audits.
Suggestions
Add concrete code examples for running accessibility audits using tools like axe-core, Lighthouse, or pa11y (e.g., `npx axe-cli https://example.com`)
Include a clear workflow: 1) Run automated audit, 2) Review violations by severity, 3) Generate report, 4) Prioritize fixes by WCAG level
Provide specific output examples showing what audit results look like and how to interpret them
Remove all generic boilerplate text and replace with actual accessibility audit commands, configuration snippets, and WCAG reference information
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. It explains what the skill does in abstract terms without any concrete information about accessibility auditing. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance is provided. The content only describes what the skill claims to do without showing how to actually run an accessibility audit. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no tools mentioned (like axe-core, Lighthouse, pa11y), no validation checkpoints, and no actual process for conducting accessibility audits. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic placeholder text with no references to detailed documentation, no links to examples, and no structured navigation to deeper 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
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.