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.

1.01x

Quality

58%

Does it follow best practices?

Impact

100%

1.01x

Average score across 3 eval scenarios

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

56%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 body is well-structured with a clear sequenced workflow and explicit re-test feedback loop, but it is held back by redundant restating of the description, high-level actionability, and a referenced playbook file that is missing from the bundle.

Suggestions

Remove or condense the opening persona paragraph and Context section, which duplicate the frontmatter description.

Name specific tools in the instructions (e.g. axe-core/Lighthouse for automated scans, NVDA/VoiceOver for screen-reader checks) to make guidance executable.

Provide the referenced 'resources/implementation-playbook.md' bundle file, or drop the reference if no detailed material exists.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but the opening persona paragraph nearly duplicates the frontmatter description and the Context section restates the same purpose, which is padding that could be trimmed.	3 / 5
Actionability	The instructions give concrete categories (keyboard, screen reader, focus order, contrast; platforms, WCAG level) but stay high-level, omitting specific tool names (e.g. axe-core, Lighthouse, NVDA) and concrete steps.	3 / 5
Workflow Clarity	The six steps are clearly sequenced from scoping through remediation to 're-test after fixes', providing an explicit validation checkpoint with only minor gaps.	4 / 5
Progressive Disclosure	Structure and signaling are good with a one-level-deep reference to 'resources/implementation-playbook.md', but no bundle directory (resources/) or file actually exists, so the reference is a dangling pointer.	3 / 5
	Total	13 / 20 Passed

Description

61%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 clearly states a distinct accessibility-audit niche and several concrete actions, but uses second-person voice and lacks an explicit 'Use when' trigger clause, capping specificity and completeness.

Suggestions

Convert to third-person voice ('Conducts accessibility audits...') to avoid the specificity penalty.

Add an explicit trigger clause, e.g. 'Use when auditing experiences for WCAG compliance, identifying accessibility barriers, or preparing remediation guidance.'

Include common synonyms users say ('a11y', 'screen reader testing', 'Section 508') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and three concrete actions ('Conduct audits, identify barriers, and provide remediation guidance'), which would merit a 4, but the second-person voice ('You are an accessibility expert') triggers the -1 specificity penalty per the judging guidelines.	3 / 5
Completeness	The 'what' is clear (audit, identify barriers, remediate) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Includes natural terms users would say like 'WCAG compliance', 'accessibility', 'audits', and 'remediation', though it omits common synonyms such as 'a11y', 'Section 508', or 'screen reader testing'.	4 / 5
Distinctiveness Conflict Risk	The WCAG/inclusive-design/assistive-technology niche is mostly distinct, with only minor overlap risk against general UX or design-review skills.	4 / 5
	Total	14 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rmyndharis/antigravity-skills
Path: skills/accessibility-compliance-accessibility-audit/SKILL.md
Commit: 3eff4af

Reviewed: 1 day 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.