CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

qa-accessibility

Test WCAG 2.2 AA accessibility with axe-core plus manual keyboard, focus, screen-reader, contrast, and zoom checks. Use for any customer-facing UI.

68

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A concise, well-structured checklist-style skill with genuinely non-obvious domain knowledge (the axe placeholder gotcha, the 57% coverage stat) and an explicit exit-criteria validation gate. Its main defect is the dangling 'see pattern D7' reference, which points to no existing file or section and leaves the reader unable to follow it.

Suggestions

Remove the 'see pattern D7' reference or back it with a real reference file (e.g. add references/focus-patterns.md with pattern D7) — as written it points to nothing.

Add a short feedback loop after the exit criteria, e.g. 'If violations are found, fix them and re-run the scan before proceeding.'

Include one concrete example of how to run the axe-core scan (e.g. an npm/CLI snippet) to make step 1 fully executable.

DimensionReasoningScore

Conciseness

The body is lean and every line earns its place: the 57% axe-core stat justifies manual checks, and details like axe accepting placeholders as accessible names are non-obvious knowledge Claude would otherwise lack. No padding or re-teaching of known concepts.

5 / 5

Actionability

The guidance is concrete and specific for an instruction-only skill (exact WCAG tags, named tools, specific manual checks), but 'see pattern D7' references material that does not exist in any bundle file, and there is no example of how to actually invoke axe-core.

4 / 5

Workflow Clarity

A clear six-step numbered procedure is capped by an explicit 'Exit criteria' validation section ('No serious or critical axe violations, and the manual checklist is recorded per route'). It falls short of a 5 because there is no feedback loop describing what to do when violations are found.

4 / 5

Progressive Disclosure

The skill is under 50 lines with well-organized sections and no external references needed, which would merit a 5, but the body references 'pattern D7' — a pointer to content that does not exist anywhere in the skill directory.

4 / 5

Total

17

/

20

Passed

Description

80%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 what the skill does with a comprehensive list of concrete check types and an explicit use-when clause. Its main weaknesses are the single broad trigger condition ('any customer-facing UI') instead of natural trigger phrases, and missing common synonyms like 'a11y' or 'Section 508'.

Suggestions

Expand the 'when' clause with concrete trigger phrases users would actually say, e.g. 'Use when the user mentions accessibility, a11y, WCAG, screen readers, or ADA/Section 508 compliance, or before shipping any customer-facing UI.'

Add common synonyms and standards names (a11y, Section 508, ADA) as trigger terms to improve discovery.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete actions — 'Test WCAG 2.2 AA accessibility with axe-core plus manual keyboard, focus, screen-reader, contrast, and zoom checks' — covering all major categories of accessibility testing comprehensively.

5 / 5

Completeness

Both what ('Test WCAG 2.2 AA accessibility with axe-core plus manual... checks') and when ('Use for any customer-facing UI') are explicitly present, but the when-clause is a single broad condition rather than the concrete trigger phrases users would naturally say.

4 / 5

Trigger Term Quality

Good natural keywords are present ('accessibility', 'WCAG 2.2 AA', 'axe-core', 'screen-reader', 'contrast', 'zoom', 'customer-facing UI'), but common variations like 'a11y', 'Section 508', or 'ADA compliance' are missing.

4 / 5

Distinctiveness Conflict Risk

The accessibility-testing niche is clear and distinct, but 'Use for any customer-facing UI' is broad enough to create minor overlap risk with general frontend development and UI design skills.

4 / 5

Total

17

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

itsablabla/qa-bug-agent-skills

Path

skills/qa-accessibility/SKILL.md

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.