CtrlK
BlogDocsLog inGet started
Tessl Logo

a11y-debugging

Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.

77

1.03x
Quality

86%

Does it follow best practices?

Impact

100%

1.03x

Average score across 1 eval scenario

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

86%Weight 40%Scale 1-5

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

A well-structured, highly actionable skill: concrete MCP tool invocations with exact parameters, verified one-level-deep snippet references, and clear sequenced workflows for each accessibility check. The only improvements are trimming a few explanations Claude already knows and adding explicit fix-and-retry loops for cases where automated checks fail.

DimensionReasoningScore

Conciseness

The ~90-line body is lean and workflow-driven, but includes minor over-explanations Claude mostly already knows (e.g., that visual hiding differs from display:none for screen readers, and "This is much easier to read!"). Matches anchor 4 (efficient, minor instances that could be trimmed) rather than 5 (every token earns its place).

4 / 5

Actionability

Every workflow gives exact tool names and parameters (mode: "navigation", types: ["issue"], includePreservedMessages: true), an executable node one-liner for parsing Lighthouse output, and pointers to four named copy-paste-ready snippets verified to exist in references/a11y-snippets.md, including how to pass the snapshot uid. Matches anchor 5 (fully executable, covers the common cases).

5 / 5

Workflow Clarity

Eight numbered, well-sequenced workflows with verification checkpoints (check audits.failed count, re-snapshot after press_key to confirm focus moved, compare DOM order against take_screenshot). Falls short of anchor 5 because explicit error-recovery feedback loops are only loosely covered in the Troubleshooting section rather than built into the workflows.

4 / 5

Progressive Disclosure

The body is a well-organized overview that keeps snippet code out of SKILL.md and signals the single one-level-deep reference ([references/a11y-snippets.md]) by bolded snippet name at each point of use; the referenced file exists and contains all four named snippets. Matches anchor 5.

5 / 5

Total

18

/

20

Passed

Description

87%Weight 40%Scale 1-5

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 description: it states the tool, the domain, the governing guidelines, and an explicit "Use when" clause with six concrete trigger areas. The only gap is that the capability verbs themselves ("debugging and auditing") are generic while the specifics live in the trigger list, and a few natural synonyms (screen readers, WCAG) are absent.

DimensionReasoningScore

Specificity

Names the domain and tool explicitly ("Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing") and the trigger list enumerates six concrete test areas, but the core action verbs ("debugging and auditing") are generic rather than a comprehensive list of concrete actions, matching anchor 4 rather than 5.

4 / 5

Completeness

Clearly answers both "what" (Chrome DevTools MCP-based a11y debugging and auditing per web.dev guidelines) and "when" ("Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast") with concrete trigger phrases, matching anchor 5 exactly.

5 / 5

Trigger Term Quality

"semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast" are natural phrases users would say when needing this skill, plus the "a11y" synonym. Missing common variations such as "screen readers", "WCAG", or "accessibility audit", so it falls short of anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (DevTools-MCP-driven accessibility testing) with distinct trigger terms; minimal risk of firing for unrelated skills, matching anchor 5.

5 / 5

Total

18

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ChromeDevTools/chrome-devtools-mcp
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.