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.

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/accessibility-compliance-accessibility-audit/SKILL.md

Quality

Content

63%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a concise, well-structured audit process with a re-test loop, but it stays at a high level without concrete tooling and relies on a referenced playbook file that is missing from the bundle.

Suggestions

Ship the referenced `resources/implementation-playbook.md` (or remove the references) so Claude can actually retrieve the detailed procedures.

Name specific tools/commands for the concrete steps (e.g., axe-core, Lighthouse, WAVE) to lift actionability past high-level guidance.

Remove the duplicated opening paragraph and tighten the Context section to avoid restating the frontmatter description.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-sectioned, but the opening paragraph duplicates the frontmatter description and the Context section restates scope, so a few tokens could be trimmed.	4 / 5
Actionability	The instructions give a clear process ("Run automated scans", "Perform manual checks") but no concrete tools, commands, or code, and the detailed playbook it points to for specifics does not exist in the bundle.	3 / 5
Workflow Clarity	Steps are clearly sequenced from scope confirmation through remediation, with a "re-test after fixes" feedback loop; it lacks an explicit validation checklist to reach a 5.	4 / 5
Progressive Disclosure	Sectioning is good, but the body twice references `resources/implementation-playbook.md`, which is not present in any bundle directory, so the primary offloading/navigation path is broken.	3 / 5
	Total	14 / 20 Passed

Description

66%Weight 40%Scale 1-5

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 states a clear domain and several concrete actions but omits an explicit "Use when..." trigger clause, capping completeness. It is specific and distinct, just not fully self-activating.

Suggestions

Add an explicit "Use when..." trigger clause naming common phrasings (e.g., WCAG audit, accessibility review, screen-reader/contrast testing).

Expand trigger terms to include common natural keywords users say: ARIA, screen reader, keyboard navigation, color contrast.

Broaden the action list slightly (e.g., "establish ongoing testing practices") to push specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the accessibility domain and three concrete actions ("Conduct audits, identify barriers, and provide remediation guidance") with only minor coverage gaps; not quite comprehensive enough for a 5.	4 / 5
Completeness	The "what" is clear, but there is no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural terms a user would say ("WCAG compliance", "accessibility", "audits", "remediation"), but omits common variations such as screen reader, contrast, ARIA, or keyboard navigation.	4 / 5
Distinctiveness Conflict Risk	It targets a clear accessibility-compliance niche distinct from general UI review skills; minor overlap risk remains because the trigger guidance is not fully explicit.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/accessibility-compliance-accessibility-audit/SKILL.md
Commit: 1f67c44

Reviewed: about 16 hours ago

Table of Contents

Discovery Implementation Validation

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.