CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/pa11y-a11y

Authors and runs pa11y accessibility scans - a CLI / Node.js tool that wraps HTML CodeSniffer (htmlcs) and / or axe-core engines - with `pa11y {url}` invocation, reporter selection (cli / csv / json / html / tsv), WCAG standard selection (WCAG2A / WCAG2AA / WCAG2AAA), and rule ignoring. Use when the project needs scriptable a11y scans without a full test framework, or when a Node-stack project wants an alternative to direct axe-core use.

75

Quality

94%

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

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, actionable skill body with executable install/run/CI examples, a sequenced workflow with an explicit verify-and-retry loop, and a well-organized single-level reference. Minor repetition of the deduplication point keeps conciseness just below the top anchor.

Suggestions

Consolidate the dual-engine duplicate-finding explanation into one section (e.g. 'Results structure') and reference it from 'Worked example' rather than restating it twice.

The 'Key flags' summary in the body overlaps with the full table in references/flags-and-output.md; consider trimming the inline list to only the flags not already covered in the overview.

DimensionReasoningScore

Conciseness

Mostly efficient and avoids explaining concepts Claude already knows, but the dual-engine duplicate-finding point is repeated across 'Results structure', 'Worked example', and the reference, so it could be tightened — placing it between the 2 and 3 anchors.

2.5 / 3

Actionability

Provides fully executable, copy-paste-ready guidance — install commands, `pa11y <url>`, a `.pa11yci` JSON config, a `require('pa11y')` programmatic example, and a complete GitHub Actions workflow.

3 / 3

Workflow Clarity

The 8-step 'How to use' sequence is clearly ordered with an explicit validation checkpoint ('Verify: run `pa11y-ci` locally and confirm it exits zero ... re-run until green') providing the fix-and-retry feedback loop the rubric rewards.

3 / 3

Progressive Disclosure

Clear overview body that signals a single one-level-deep reference ([references/flags-and-output.md]) for the full flag table and JSON shape; the referenced file exists and is appropriately split out, matching the 'clear overview with well-signaled one-level-deep references' anchor.

3 / 3

Total

11.5

/

12

Passed

Description

92%

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 specific, well-structured description with concrete capabilities and explicit 'Use when' triggers that cleanly separate it from adjacent axe skills. Trigger phrasing is slightly technical, which is the only minor weakness.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Authors and runs pa11y accessibility scans', 'reporter selection (cli / csv / json / html / tsv)', 'WCAG standard selection', 'and rule ignoring' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Clearly answers both what (authors/runs scans with the listed features) and when via the explicit 'Use when the project needs scriptable a11y scans without a full test framework, or when a Node-stack project wants an alternative to direct axe-core use' trigger.

3 / 3

Trigger Term Quality

Covers natural terms like 'accessibility scans', 'a11y scans', 'pa11y', 'axe-core', and 'WCAG', but 'scriptable a11y scans' and 'Node-stack' lean technical and omit common lay phrasings like 'check my site for accessibility', so it sits between the 2 and 3 anchors.

2.5 / 3

Distinctiveness Conflict Risk

Names the specific tool (pa11y) and engine wrappers (htmlcs / axe-core) and explicitly carves a niche apart from direct axe-core use, giving it a clear niche unlikely to trigger the wrong skill.

3 / 3

Total

11.5

/

12

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.

Reviewed

Table of Contents