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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill accessibility-audit-runnerOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder that provides almost no useful information for skill selection. It repeats the skill name as trigger terms, lacks any concrete actions or capabilities, and provides no guidance on when Claude should select this skill. The description would be indistinguishable from any other accessibility-related skill.
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 'Use when the user asks about accessibility testing, a11y audits, WCAG compliance, screen reader compatibility, or ADA requirements'
Add common user vocabulary variations: 'a11y', 'accessibility check', 'WCAG', 'screen reader', 'keyboard navigation', 'color contrast'
| 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. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 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 testing'. | 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, testing skills, or frontend development skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual instructional value. It contains only generic descriptions of what the skill supposedly does without any concrete guidance on how to run accessibility audits, which tools to use, or what to check for. The content fails on all dimensions by being verbose yet empty of actionable information.
Suggestions
Add concrete code examples for running accessibility audits using specific tools (e.g., axe-core, pa11y, or Lighthouse CLI commands)
Include a clear workflow: 1) Run automated audit, 2) Review results, 3) Prioritize issues by WCAG level, 4) Fix and re-validate
Provide specific WCAG criteria to check and common accessibility issues to look for (color contrast, alt text, keyboard navigation)
Replace generic capability descriptions with actual audit commands and expected output formats
| 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, no commands, no specific steps for running accessibility audits. The content describes what the skill does rather than instructing how to do it. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. There are no steps for running an accessibility audit, no tools mentioned (like axe-core, pa11y, Lighthouse), and no validation checkpoints. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no structure pointing to detailed resources, no references to specific documentation, and no organized sections for different audit scenarios. | 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.