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 ./skills/antigravity-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 domain (accessibility and WCAG compliance) and lists some high-level actions, but it lacks a 'Use when...' clause, which is critical for skill selection. It also uses second-person framing ('You are an accessibility expert') which is inappropriate—descriptions should use third person voice. The trigger terms are reasonable but miss many common user-facing keywords.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about accessibility, WCAG compliance, screen reader compatibility, color contrast, keyboard navigation, or ARIA attributes.'
Rewrite in third person voice (e.g., 'Conducts accessibility audits...') instead of the current second person 'You are an accessibility expert' framing.
Include more natural trigger terms users would say, such as 'a11y', 'screen reader', 'alt text', 'color contrast', 'ADA', 'keyboard navigation', and 'ARIA'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (accessibility, WCAG compliance) and some actions (conduct audits, identify barriers, provide remediation guidance), but the actions are somewhat general and not highly concrete—e.g., it doesn't specify what types of audits, what kinds of barriers, or what formats of remediation. | 2 / 3 |
Completeness | Describes what it does (conduct audits, identify barriers, provide remediation guidance) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'when' is entirely absent, warranting a score of 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'WCAG', 'accessibility', 'inclusive design', 'assistive technology', and 'audits', but misses common user variations such as 'screen reader', 'a11y', 'ADA compliance', 'alt text', 'color contrast', 'keyboard navigation', or 'ARIA'. | 2 / 3 |
Distinctiveness Conflict Risk | The accessibility/WCAG focus provides some distinctiveness, but the broad framing ('accessibility expert') and generic actions ('conduct audits', 'provide guidance') could overlap with general web development or UX design 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 structure with good progressive disclosure to a detailed playbook, but critically lacks actionability—there are no concrete tools, commands, code examples, or specific techniques mentioned. The content reads as a generic process outline that doesn't add much beyond what Claude would already know about accessibility auditing.
Suggestions
Add concrete tool recommendations and executable commands (e.g., `npx axe-core`, `lighthouse --accessibility`, specific browser DevTools steps) to make the instructions actionable.
Include at least one concrete example of a finding mapped to a WCAG criterion with severity and remediation code, rather than just describing the process abstractly.
Add explicit validation checkpoints in the workflow, such as 'Verify automated scan produces zero critical violations before proceeding to manual checks' or specific pass/fail criteria for each step.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill has some unnecessary verbosity—the 'Context' section largely restates the description and 'Use this skill when' sections. The 'You are an accessibility expert...' preamble repeats the frontmatter description. However, it's not egregiously padded. | 2 / 3 |
Actionability | The instructions are entirely abstract and vague—'Run automated scans,' 'Perform manual checks,' 'Map findings to WCAG criteria' without specifying any concrete tools, commands, code snippets, or specific techniques. There is no executable guidance; it reads as a high-level process description rather than actionable instructions. | 1 / 3 |
Workflow Clarity | Steps are listed in a logical sequence and include a re-test step, but there are no explicit validation checkpoints, no error recovery/feedback loops, and no concrete criteria for when to proceed between steps. The workflow is more of a checklist outline than a guided process. | 2 / 3 |
Progressive Disclosure | The skill appropriately keeps the main file as a concise overview and references `resources/implementation-playbook.md` for detailed procedures. The reference is one level deep and clearly signaled. | 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
- boisenoise/skills-collections
- Commit
636b862
- 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.