CtrlK
BlogDocsLog inGet started
Tessl Logo

wcag-audit-patterns

Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing accessible design patterns.

66

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/wcag-audit-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 concise and reasonably sequenced with a re-test loop, but it lacks executable commands for the named tools and references a playbook file that is not present in the bundle.

Suggestions

Add concrete executable commands or examples for the named tools (e.g., an axe CLI invocation or Lighthouse command) to lift actionability.

Provide an explicit validation checkpoint between manual checks and remediation mapping (e.g., 'verify each finding reproduces before recording').

Create the referenced resources/implementation-playbook.md file or remove the dangling reference so progressive disclosure navigation resolves.

DimensionReasoningScore

Conciseness

Lean and efficient body that assumes Claude's competence, lists only the steps and tools needed, and avoids explaining what WCAG or accessibility concepts are.

5 / 5

Actionability

Names specific tools (axe, Lighthouse, WAVE) but provides no executable commands, code, or flags; the steps read as high-level direction rather than copy-paste-ready guidance.

3 / 5

Workflow Clarity

A clear four-step sequence is present with a re-test feedback loop ('Re-test after fixes'), though explicit validation checkpoints before proceeding are only implicit.

4 / 5

Progressive Disclosure

The overview points to a referenced file ('resources/implementation-playbook.md') that does not exist in the bundle, and the path is repeated rather than clearly signaled once, leaving navigation unreliable.

3 / 5

Total

15

/

20

Passed

Description

87%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.

A strong description that clearly states capabilities and provides explicit 'Use when' triggers with concrete natural-language phrases. Minor improvements possible by adding common synonyms such as a11y, ADA, and VPAT.

DimensionReasoningScore

Specificity

Lists several concrete actions ('automated testing, manual verification, and remediation guidance') tied to a named domain, with only minor coverage gaps such as reporting artifacts.

4 / 5

Completeness

Explicitly answers both 'what' (conduct WCAG 2.2 audits with testing, verification, remediation) and 'when' via a concrete 'Use when...' clause with multiple triggers.

5 / 5

Trigger Term Quality

Includes natural terms users say ('accessibility', 'WCAG violations', 'auditing websites', 'accessible design patterns') but omits common synonyms like a11y, ADA, or VPAT.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (WCAG 2.2 accessibility audits) with distinct triggers, presenting minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
rmyndharis/antigravity-skills
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.