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

33%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/antigravity-accessibility-compliance-accessibility-audit/SKILL.md

Quality

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/WCAG) and lists some high-level actions, but it reads more like a system prompt role assignment ('You are an accessibility expert') than a skill description. It lacks an explicit 'Use when...' clause, uses second-person voice instead of third person, and misses common user trigger terms like 'a11y', 'screen reader', 'ADA', or 'alt text'.

Suggestions

Rewrite in third person voice (e.g., 'Conducts accessibility audits against WCAG guidelines, identifies barriers, and provides remediation guidance') instead of the role-play 'You are...' format.

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about accessibility, WCAG compliance, a11y, screen reader compatibility, ADA, alt text, aria attributes, or keyboard navigation.'

Include more specific concrete actions such as 'evaluates color contrast ratios, checks semantic HTML structure, reviews ARIA attribute usage, and validates keyboard navigability'.

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. Per the rubric, a missing 'Use when' clause caps completeness at 2, and the 'what' portion is also only moderately detailed, placing this at the lower end. Additionally, the description uses second-person framing ('You are') which is a role-play prompt rather than a proper skill description.	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 domain is fairly specific and unlikely to conflict with most skills, but the broad framing ('conduct audits, identify barriers, provide remediation guidance') could overlap with general code review or web development skills without clearer scoping.	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 any concrete tools, commands, code examples, or specific WCAG criteria references, making it difficult for Claude to execute meaningfully. The workflow structure is reasonable but needs validation checkpoints and the referenced implementation playbook is missing from the bundle.

Suggestions

Add concrete tool recommendations and executable commands (e.g., specific axe-core CLI commands, Lighthouse accessibility audit commands, or code snippets for programmatic testing).

Include at least one concrete example of a finding mapped to a WCAG criterion with severity, user impact, and remediation code — this would dramatically improve actionability.

Add explicit validation checkpoints in the workflow, such as 'Verify automated scan covers at least X% of pages before proceeding to manual checks' or 'Confirm all Critical/High findings are remediated before re-test.'

Provide the referenced `resources/implementation-playbook.md` bundle file, or inline the most critical content (tooling setup, key manual check procedures) so the skill is useful standalone.

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 '$ARGUMENTS' placeholder adds no value. However, it's not excessively verbose.	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 nothing executable or copy-paste ready.	1 / 3
Workflow Clarity	There is a clear sequence of steps (confirm scope → automated scans → manual checks → map findings → remediate → re-test), which is good. However, there are no validation checkpoints, no explicit feedback loops for error recovery, 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 appropriate one-level-deep disclosure. However, no bundle files were provided, so the reference is unverifiable, and the main content itself is too thin — it defers almost all substance to the referenced file without providing a useful quick-start overview.	2 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 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: cfced3a

Reviewed: 2 days 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.