CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/a11y-violation-gate

Builds a CI gate that fails the build on **new** WCAG / a11y violations introduced by a PR while grandfathering pre-existing violations on a per-rule / per-page baseline. Aggregates verdicts from axe-core / pa11y / Lighthouse a11y / WAVE / IBM Equal Access scans. Use when a project has accumulated a11y debt and a strict "zero violations" gate would block every PR - the ratchet pattern lets the team ship while preventing regressions.

79

Quality

99%

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

100%

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

A well-structured, token-efficient skill body: an executable gate script, concrete schemas, a sequenced five-step workflow with validation/feedback signals, and a single genuine one-level reference for the heavier detail. It avoids re-teaching concepts Claude already knows.

DimensionReasoningScore

Conciseness

The body is lean: it never explains what WCAG/axe-core are, jumps straight into the unified record, baseline, gate decision, and artifact, and every section earns its tokens. It is tighter than the level-2 anchor that pads with unnecessary library justification.

3 / 3

Actionability

Provides a fully executable `run_a11y_gate.py` with real imports, concrete JSON schemas for the unified record and baseline, and a copy-paste-ready severity-tier table — matching the 'fully executable code/commands; copy-paste ready' anchor.

3 / 3

Workflow Clarity

Steps 1–5 are clearly sequenced with the gate's exit code (`sys.exit(0 if verdict == 'go' else 1)`) as an explicit checkpoint, and Step 5's baseline-maintenance workflow gives error-recovery guidance ('Manually remove the fingerprint... otherwise the baseline accumulates stale entries'). This exceeds the level-2 anchor's missing-checkpoint case.

3 / 3

Progressive Disclosure

The core runnable gate lives inline while per-scanner shapes and the full PR-artifact template are split into a single, clearly signaled, one-level-deep reference (`references/gate-implementation.md`, confirmed to exist), matching the 'clear overview with well-signaled one-level-deep references' anchor.

3 / 3

Total

12

/

12

Passed

Description

100%

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, third-person description that states concrete capabilities, names the five scanners it aggregates, and provides an explicit 'Use when' trigger tied to a realistic scenario. It is distinctive within a family of sibling gate skills and avoids vague fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Builds a CI gate that fails the build on new WCAG / a11y violations', 'grandfathering pre-existing violations on a per-rule / per-page baseline', and 'Aggregates verdicts from axe-core / pa11y / Lighthouse / WAVE / IBM Equal Access' — matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

It explicitly answers what ('Builds a CI gate that fails the build on new... violations... grandfathering pre-existing violations') and when ('Use when a project has accumulated a11y debt and a strict zero violations gate would block every PR'), with an explicit trigger clause.

3 / 3

Trigger Term Quality

The 'Use when a project has accumulated a11y debt and a strict "zero violations" gate would block every PR' clause surfaces natural phrases (a11y debt, zero violations gate, PR) a user would actually say, giving good coverage rather than just jargon.

3 / 3

Distinctiveness Conflict Risk

The ratchet-pattern a11y gate niche is highly specific and unlikely to trigger for sibling gates (data-quality-gate, perf-budget-gate, etc.) or generic scanners, matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents