CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/axe-a11y

Use for any request to check accessibility automatically, including adding a scan to an existing Playwright, Cypress or unit test, or stopping missing labels and contrast errors from shipping: axe-core via axe.run(), @axe-core/playwright or the CLI on every PR, rule configuration and CI-gateable results, plus pa11y, Lighthouse CI, WAVE and IBM Equal Access in its references.

Quality

91%

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

Overview
Quality
Evals
Security
Files

Quality

Content

86%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 well-structured, highly actionable body: complete code and CI examples, a clearly sequenced workflow with a demonstrated error-recovery loop, and clean one-level-deep reference files verified to exist. The minor deductions are for repeated ratchet-pattern mentions and a CI example that doesn't quite implement the stated artifact-persistence guidance.

DimensionReasoningScore

Conciseness

Efficient and tool-specific with no explanation of concepts Claude already knows, but the ratchet/'a11y-violation-gate' pattern is repeated across ~5 sections and the References list re-states links already given inline, so a few spots could be trimmed.

4 / 5

Actionability

Fully executable guidance: copy-paste-ready install command, complete Playwright test, Cypress commands, a full GitHub Actions workflow, a jq triage command, and specific API calls (.withTags, .disableRules, .exclude) covering the common integration cases.

5 / 5

Workflow Clarity

The 7-step 'How to use' sequence is clear and the worked example demonstrates an explicit validate→fix→retry loop, but the CI YAML uploads playwright-report/ while the guidance (step 5) says to persist the raw accessibilityScanResults JSON as an artifact — the example doesn't implement its own step.

4 / 5

Progressive Disclosure

All five referenced files exist in references/, are one level deep, and are well-signaled — the 'Other scanners' table gives a 'reach for it when' per link and results-and-config.md is introduced with a summary of its contents — making navigation easy.

5 / 5

Total

18

/

20

Passed

Description

92%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: it explicitly states when to use the skill with concrete trigger scenarios, names specific tools and integration paths for what it does, and carves out a distinct automated-accessibility niche. Its only weakness is missing common synonyms like 'a11y' and 'WCAG' in the trigger phrasing.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with named tools and APIs — 'adding a scan to an existing Playwright, Cypress or unit test', 'axe-core via axe.run(), @axe-core/playwright or the CLI on every PR', 'rule configuration and CI-gateable results', plus named alternative scanners — giving comprehensive coverage of the automated a11y scanning domain.

5 / 5

Completeness

Explicitly answers both: the 'Use for any request to check accessibility automatically, including...' clause gives concrete when-triggers, and the remainder specifies the what via named engines, adapters, and outputs.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('check accessibility', 'adding a scan', 'Playwright, Cypress or unit test', 'missing labels and contrast errors', 'on every PR'), but common user phrasings like 'a11y', 'WCAG', and 'accessibility audit' are missing.

4 / 5

Distinctiveness Conflict Risk

The 'check accessibility automatically' phrasing scopes away manual testing, and the named engines (axe-core, pa11y, Lighthouse CI, WAVE, IBM Equal Access) create a clear niche with distinct triggers and minimal conflict risk.

5 / 5

Total

19

/

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.

Reviewed

On this page