CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/wave-a11y

Runs WebAIM WAVE accessibility scans via the WAVE API or the browser-extension UI - produces visual overlay of errors / alerts / structural elements directly on the page, plus categorized JSON output for CI use. Use when the team values manual-review-friendly visual feedback (the WAVE overlay) alongside automated CI scans, or when a regulatory audit requires WebAIM-branded reports.

74

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

Quality

Content

85%

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

A highly actionable, well-structured CI-tooling skill with executable code, a complete workflow, and clean sectioning. The only meaningful weakness is the inline dated source-fetch note, which dents token-efficiency per the time-sensitive guidance.

Suggestions

Move the dated 'Source-fetch note (2026-05-04)' into a clearly labeled 'Source / verification' or 'Deprecated' subsection, or strip the date and keep only the 'verify current WAVE API v3+ docs' pointer, to avoid time-sensitive conciseness penalties.

Tighten the Overview's WAVE-category taxonomy into a compact list; the prose around it repeats what the later icon-color legend and JSON categories already convey.

Consider extracting the full WAVE API JSON response shape into a short REFERENCES section pointer or table so the main body stays a lean overview.

DimensionReasoningScore

Conciseness

Mostly efficient and tool-specific, but the inline 'Source-fetch note (2026-05-04)' embeds a time-sensitive date outside any deprecated/old-patterns section, which the guidelines penalize; the Overview also pads slightly.

2 / 3

Actionability

Fully executable guidance throughout - a real curl command, a concrete JSON response shape, jq triage one-liners, a complete GitHub Actions workflow, and an anti-patterns table with explicit fixes - all copy-paste ready.

3 / 3

Workflow Clarity

The CI workflow is clearly sequenced (scan each URL -> upload artifacts with if: always() -> gate via violation-gate), and manual usage is a clean numbered list; the gate step serves as the explicit verification checkpoint even though gating logic is delegated to a sibling skill.

3 / 3

Progressive Disclosure

No bundle files exist (references/scripts/assets absent), and the single ~200-line body is organized into clearly signaled one-level-deep sections (Overview, When to use, Install, Manual/API usage, CI, Anti-patterns, Limitations, References) with no nested reference chains.

3 / 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.

A strong, third-person description that concretely states capabilities, gives explicit use-when triggers, and carves out a distinct niche from sibling a11y scanners. Minor jargon in the trigger clause keeps it just short of flawless.

DimensionReasoningScore

Specificity

Lists multiple concrete actions - 'Runs WebAIM WAVE accessibility scans', 'produces visual overlay of errors / alerts / structural elements', and 'categorized JSON output for CI use' - matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what (scans / visual overlay / JSON) and when ('Use when the team values manual-review-friendly visual feedback... or when a regulatory audit requires WebAIM-branded reports'), satisfying the both-what-and-when anchor.

3 / 3

Trigger Term Quality

Includes natural domain terms an a11y practitioner would say - 'WAVE', 'accessibility scans', 'visual overlay', 'CI scans', 'regulatory audit' - giving good coverage, though some phrasing like 'manual-review-friendly visual feedback' leans slightly jargon-heavy.

3 / 3

Distinctiveness Conflict Risk

WAVE-specific niche (visual overlay, WebAIM-branded reports) clearly distinguishes it from sibling axe/pa11y scanners, making false-trigger conflict unlikely.

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