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.

81

1.01x
Quality

85%

Does it follow best practices?

Impact

55%

1.01x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

The body is a well-structured, actionable auditing guide that respects token budget and offloads snippets to a real reference file. Tightening the redundant explanatory comments would push conciseness to a 5.

Suggestions

Trim explanatory comments that restate what the code already shows (e.g., 'This efficiently extracts the selector and snippet of failing elements without loading the full report into context').

Consider adding an explicit verify/retry loop for at least one workflow (e.g., after fixing contrast or tap-target issues, re-run the snippet to confirm the violation cleared) to strengthen workflow_clarity.

Move or hyperlink the contrast snippet's caveat about injecting axe-core for production audits to keep the inline guidance lean.

DimensionReasoningScore

Conciseness

Mostly efficient with skill-specific, non-obvious tips (opacity vs display:none behavior, the .md.txt URL trick); a few comments like the jq/node explanation state what the tool already shows and could be trimmed.

4 / 5

Actionability

Provides concrete tool names with parameter values, an executable node one-liner, and named pointers to copy-paste-ready snippets in the reference; minor gaps only because some snippets live in the bundled file.

4 / 5

Workflow Clarity

Eight clearly sequenced patterns with numbered steps and implicit checkpoints (score<1 indicates violations, modal focus trapping); not a crisp validate->fix->retry loop but the skill is read-only auditing so the destructive cap does not apply.

4 / 5

Progressive Disclosure

Well-organized overview sections with JavaScript snippets appropriately split into a single one-level-deep reference file (a11y-snippets.md, verified present) and clearly signaled via named snippet links.

5 / 5

Total

17

/

20

Passed

Description

92%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.

The description is specific, complete, and distinctive, clearly stating both capabilities and concrete usage triggers. It would benefit from a few additional synonyms (WCAG, accessibility audit) but is otherwise strong.

DimensionReasoningScore

Specificity

Names the domain and concrete actions across six specific accessibility concerns (semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, color contrast), giving comprehensive coverage within its scope.

5 / 5

Completeness

Explicitly answers 'what' (a11y debugging and auditing via Chrome DevTools MCP) and 'when' (Use when testing the listed a11y concerns) with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural-term coverage including the 'a11y' synonym and concrete concerns users cite, but misses a few common variations like 'WCAG' or 'accessibility audit'.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Chrome DevTools MCP + web.dev a11y guidelines) with trigger terms specific to accessibility auditing, minimizing overlap with other skills.

5 / 5

Total

19

/

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.

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