CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/wcag-checklist-builder

Builds a per-component WCAG 2.2 accessibility checklist from a component spec - covers focus management, color contrast, ARIA roles & states, keyboard interaction, error handling, and live-region announcements - emitting a markdown checklist or YAML test plan that pairs with screen-reader-test-author for manual verification and the violation gate for automated scans. Use during component-spec review or pre-implementation acceptance.

77

Quality

97%

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.

The body is highly actionable and concise, with clearly sequenced steps and concrete copy-paste templates. Its main weakness is structure: everything is inline with no progressive disclosure via separate reference files, despite substantial reusable content like the keystroke table and output templates.

Suggestions

Move the NVDA/VoiceOver keystroke table and the two full output templates (markdown checklist + YAML test plan) into separate reference files under references/, leaving SKILL.md as an overview that links one level deep — this raises progressive_disclosure without losing actionability.

Add a short 'Reference files' subsection near the top signaling those extracted files, so navigation is explicit rather than implicit.

Consider extracting the per-archetype checklists into a single references/archetypes.md to keep SKILL.md's core workflow (Steps 1–4) scannable while the detailed items remain one click away.

DimensionReasoningScore

Conciseness

The body is a lean reference checklist — every line is an actionable item or a concrete template; it does not explain concepts Claude already knows (no 'what is WCAG' prose), matching the score-3 lean/efficient anchor rather than the padded score-2 example.

3 / 3

Actionability

Guidance is fully executable — specific ARIA attributes, contrast ratios, keyboard keys, an NVDA/VoiceOver keystroke table, and complete copy-paste markdown and YAML templates — matching the score-3 copy-paste-ready anchor rather than the pseudocode score-2 example.

3 / 3

Workflow Clarity

Steps 1–4 (identify archetype → apply checklist → add customization → emit artifact) are clearly sequenced with an explicit pass criterion ('A step passes when the announcement identifies the element type, reads the visible label verbatim…'); the task is generation rather than destructive/batch manipulation, so the missing validate-loop cap does not apply.

3 / 3

Progressive Disclosure

No bundle files exist and the full ~270-line body — including the keystroke table and both complete output templates — lives inline in SKILL.md; sections are well-organized but content that could reasonably be split into separate reference files is not, matching the score-2 'content that should be separate is inline' anchor rather than the score-3 one-level-deep split.

2 / 3

Total

11

/

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.

The description is specific, trigger-rich, and complete, naming concrete coverage areas, explicit use-conditions, and sibling-skill pairings. It is dense but every clause earns its place and it clearly distinguishes itself from adjacent a11y skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'covers focus management, color contrast, ARIA roles & states, keyboard interaction, error handling, and live-region announcements' and 'emitting a markdown checklist or YAML test plan' — matching the score-3 anchor of several specific concrete actions rather than the single-domain score-2 example.

3 / 3

Completeness

It clearly answers both what (builds a per-component WCAG checklist from a spec, emitting markdown/YAML) and when ('Use during component-spec review or pre-implementation acceptance'), matching the score-3 anchor with an explicit trigger clause rather than the implied-only score-2 example.

3 / 3

Trigger Term Quality

It surfaces natural terms an a11y-aware user would say ('WCAG 2.2 accessibility checklist', 'component spec', 'color contrast', 'ARIA roles & states', 'keyboard interaction'), giving good coverage; it is not jargon-only like the score-1 'document object model' example.

3 / 3

Distinctiveness Conflict Risk

The niche is specific — a per-component WCAG 2.2 checklist that pairs with named sibling skills (screen-reader-test-author, violation gate) — making it unlikely to trigger for the wrong skill, matching the score-3 clear-niche anchor.

3 / 3

Total

12

/

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