CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/lighthouse-a11y

Configures Lighthouse CI's Accessibility category for automated accessibility testing (a11y / WCAG coverage) - `categories:accessibility` audits backed by axe-core (axe) - with per-URL minimum-score assertions (fail a build when a page's score drops below a threshold) and per-audit overrides, distinct from the Performance category that `lighthouse-perf` covers. Use when the project already runs Lighthouse CI for Web Vitals and the team wants to add accessibility coverage in the same pipeline rather than spinning up a separate scanner.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

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.

The body is well-structured with a clear overview, executable worked example, sequenced workflow with verification, anti-patterns, limitations, and a single well-signaled reference file. It respects token budget while remaining fully actionable.

DimensionReasoningScore

Conciseness

The body is lean and executable — no padding explaining what WCAG or Lighthouse is — and nearly every token earns its place; the sibling-relationship restatement in the Overview is the only mild excess.

3 / 3

Actionability

Provides a fully executable .lighthouserc.js, copy-paste commands ('npm install --save-dev @lhci/cli', 'npx lhci autorun'), and concrete per-audit assertions matching the top anchor.

3 / 3

Workflow Clarity

The 6-step How-to-use includes an explicit verification checkpoint ('confirm the assert phase reports every assertion passing locally before merging; if one fails, fix... and re-run npx lhci autorun until green') — a clear feedback loop.

3 / 3

Progressive Disclosure

Overview points to a single, real one-level-deep reference (references/advanced-config-and-ci.md, verified present) signaled in multiple places; detail is appropriately split out.

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.

The description is specific, trigger-rich, and self-disambiguating, explicitly covering what it does, when to use it, and how it differs from sibling skills. It is concise without fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Configures Lighthouse CI's Accessibility category', 'per-URL minimum-score assertions (fail a build when a page's score drops below a threshold)', and 'per-audit overrides' — matching the top anchor.

3 / 3

Completeness

Explicitly answers both what (configure category with assertions/overrides) and when via the 'Use when the project already runs Lighthouse CI for Web Vitals and the team wants to add accessibility coverage in the same pipeline' clause.

3 / 3

Trigger Term Quality

Strong natural-term coverage including 'accessibility testing (a11y / WCAG coverage)', 'Lighthouse CI', 'Web Vitals', and 'accessibility coverage' that users would actually say.

3 / 3

Distinctiveness Conflict Risk

Clearly carves a niche ('distinct from the Performance category that lighthouse-perf covers', 'rather than spinning up a separate scanner') making collision with sibling skills unlikely.

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