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.
49
37%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent/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 establishes a clear accessibility domain focus with relevant terminology but suffers from two key weaknesses: it uses second-person voice ('You are') which violates the third-person requirement, and it completely lacks explicit trigger guidance for when Claude should select this skill. The actions listed are somewhat generic rather than concrete accessibility-specific tasks.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about WCAG compliance, accessibility audits, screen reader compatibility, color contrast, keyboard navigation, or ADA requirements'
Rewrite in third person voice: 'Conducts accessibility audits, identifies WCAG compliance issues, and provides remediation guidance for inclusive design'
Include more specific concrete actions and natural trigger terms users would say: 'a11y', 'alt text', 'screen reader', 'color contrast checker', 'keyboard accessible'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (accessibility/WCAG) and some actions ('conduct audits, identify barriers, provide remediation guidance'), but these are somewhat general rather than listing multiple concrete specific actions like 'test screen reader compatibility, validate color contrast ratios, check keyboard navigation'. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this has no 'when' component at all. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'WCAG', 'accessibility', 'inclusive design', 'assistive technology', but misses common user variations like 'a11y', 'screen reader', 'ADA compliance', 'color contrast', 'alt text', or 'keyboard navigation'. | 2 / 3 |
Distinctiveness Conflict Risk | The accessibility/WCAG focus provides some distinctiveness, but 'conduct audits' and 'provide guidance' are generic enough to potentially overlap with other audit or compliance-related skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable high-level framework for accessibility auditing with good progressive disclosure, but lacks the concrete, actionable guidance needed for execution. The instructions read more like a checklist of activities than executable steps, with no specific tools, commands, or examples provided. The workflow structure is present but missing validation checkpoints critical for audit processes.
Suggestions
Add specific tool names and commands for automated scanning (e.g., 'Run axe-core: `npx axe-cli https://example.com`' or 'Use Lighthouse: `lighthouse --accessibility-only`')
Include concrete examples of manual checks with specific techniques (e.g., 'Tab through all interactive elements, verify focus indicator is visible with 3:1 contrast ratio')
Add validation checkpoints such as 'Confirm zero critical violations before proceeding to manual testing' and specify pass/fail criteria for re-testing
Remove redundant content - the opening description duplicates the Context section
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill has some unnecessary repetition (the description appears twice - once in context and once at the top) and includes sections like 'Use this skill when' that explain when to apply the skill rather than how to execute it. However, it's not excessively verbose. | 2 / 3 |
Actionability | The instructions are vague and abstract - 'Run automated scans', 'Perform manual checks', 'Map findings to WCAG criteria' without specifying which tools, commands, or concrete steps. No executable code, specific tool names, or copy-paste ready commands are provided. | 1 / 3 |
Workflow Clarity | Steps are listed in a logical sequence (scope → scan → manual check → map → remediate → re-test), but there are no validation checkpoints, no explicit feedback loops for failed audits, and the 're-test after fixes' step lacks specificity on what constitutes passing. | 2 / 3 |
Progressive Disclosure | Clear structure with a concise overview and well-signaled one-level-deep reference to 'resources/implementation-playbook.md' for detailed procedures. The skill appropriately defers detailed content to a separate file. | 3 / 3 |
Total | 8 / 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
- Dokhacgiakhoa/antigravity-ide
- Commit
332e58b
- 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.