accessibility-compliance-accessibility-audit
You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct audits, identify barriers, and provide remediation guidance.
36
33%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/antigravity-awesome-skills-claude/skills/accessibility-compliance-accessibility-audit/SKILL.mdQuality
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a clear domain (accessibility and WCAG compliance) and lists some high-level actions, but it lacks a 'Use when...' clause, uses second-person framing ('You are'), and doesn't include enough natural trigger terms users would use. The actions listed are somewhat generic and could be more concrete with specific deliverables or file types.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'accessibility audit', 'WCAG', 'screen reader', 'a11y', 'ADA compliance', 'alt text', 'aria attributes', 'keyboard navigation'.
Rewrite in third person voice (e.g., 'Conducts accessibility audits...') instead of the current second person 'You are...' framing.
List more specific concrete actions such as 'evaluate HTML for WCAG 2.1 AA conformance, check color contrast ratios, review ARIA markup, generate compliance reports'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (accessibility, WCAG compliance) and some actions (conduct audits, identify barriers, provide remediation guidance), but these are somewhat general and not highly concrete or comprehensive — e.g., it doesn't specify what types of content are audited or what specific outputs are produced. | 2 / 3 |
Completeness | Describes what the skill does (conduct audits, identify barriers, provide remediation) but has no explicit 'Use when...' clause or trigger guidance for when Claude should select this skill. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also somewhat weak, so this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'WCAG', 'accessibility', 'inclusive design', 'assistive technology', and 'audits', but misses common user-facing variations such as 'screen reader', 'a11y', 'ADA compliance', 'alt text', 'aria labels', or 'keyboard navigation'. | 2 / 3 |
Distinctiveness Conflict Risk | The accessibility/WCAG focus provides some distinctiveness, but the broad framing ('inclusive design', 'identify barriers', 'remediation guidance') could overlap with general web development or UX design skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads as a high-level process outline rather than actionable guidance. It lacks concrete tools, commands, code examples, specific WCAG criteria, and output formats that would make it useful for Claude to execute. The referenced implementation playbook could potentially address these gaps, but it doesn't exist in the bundle, leaving the skill hollow.
Suggestions
Add concrete, executable examples: specify actual tools (e.g., axe-core commands, Lighthouse CLI), specific WCAG criteria to check (e.g., 1.4.3 Contrast, 2.1.1 Keyboard), and example output formats for audit reports.
Include a concrete output template or JSON schema for audit findings, showing fields like WCAG criterion, severity, element selector, current state, and remediation steps.
Add validation checkpoints to the workflow — e.g., 'After automated scan, verify at least 90% page coverage before proceeding to manual checks' and 'After remediation, re-run automated scan and confirm zero critical violations before marking complete.'
Either provide the referenced `resources/implementation-playbook.md` bundle file with detailed procedures, or inline the most critical actionable content (tool commands, specific check procedures, remediation code patterns) directly in the skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary sections like 'Context' which largely restates the description, and 'Use this skill when' / 'Do not use this skill when' sections that are somewhat generic. The instructions themselves are reasonably lean but the overall document has padding that doesn't add much value for Claude. | 2 / 3 |
Actionability | The instructions are vague and abstract — 'Run automated scans,' 'Perform manual checks,' 'Map findings to WCAG criteria' — without specifying any concrete tools, commands, code snippets, or specific techniques. There are no executable examples, no specific WCAG criteria referenced, and no concrete output formats. It describes rather than instructs. | 1 / 3 |
Workflow Clarity | There is a sequential list of steps (confirm scope → scan → manual checks → map findings → remediate → re-test), which provides a basic workflow. However, there are no explicit validation checkpoints, no feedback loops for when issues are found during re-testing, and no concrete criteria for when to proceed between steps. | 2 / 3 |
Progressive Disclosure | The skill references `resources/implementation-playbook.md` for detailed procedures, which is a good pattern for progressive disclosure. However, no bundle files were provided, meaning the referenced file doesn't exist, and the main skill body is too thin on its own — it defers almost all actionable content to a non-existent resource file. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
22710e9
- 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.