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

Does it follow best practices?

Impact

55%

1.01x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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-organized, actionable walkthrough that delegates reusable snippets to a single reference file. It is held back mainly by light conceptual padding and the absence of explicit error-recovery feedback loops in the workflow.

Suggestions

Tighten the 'Core Concepts' section: drop or shorten the opacity-vs-display:none primer that Claude already knows, and remove the 'This is much easier to read!' aside on the web.dev tip.

Add a brief validate-fix-retry loop to the Lighthouse and console-issue sections (e.g., 'if violations remain, fix the top failure and re-run the audit') to reach the top workflow-clarity anchor.

Consider moving the web.dev .md.txt fetch trick into the reference file or a one-line note so it does not interrupt the workflow.

DimensionReasoningScore

Conciseness

Mostly efficient with executable examples and a tight workflow, but includes some educational padding Claude already knows (the opacity vs display:none accessibility-tree explanation) and asides like 'This is much easier to read!' that could be trimmed.

2 / 3

Actionability

Provides concrete executable guidance: a copy-paste Node.js one-liner for filtering Lighthouse failures, specific tool parameter values ('mode', 'outputDirPath', 'types'), and pointers to executable JS snippets in the references.

3 / 3

Workflow Clarity

The eight sections are clearly sequenced with checkpoints (e.g., the 'CRITICAL' Lighthouse parsing step), but there are no explicit validate-fix-retry feedback loops for error recovery, which the top anchor requires.

2 / 3

Progressive Disclosure

SKILL.md is a concise overview with well-signaled, one-level-deep links to references/a11y-snippets.md (a verified real file) for the reusable JS snippets, keeping the body lean.

3 / 3

Total

10

/

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, well-formed description that clearly states the capability, the tool, and explicit usage triggers with natural keyword coverage. It is concise, in third person, and distinct from other skills.

DimensionReasoningScore

Specificity

Names a concrete tool ('Chrome DevTools MCP') and specific actions ('debugging and auditing') plus a list of concrete test targets, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

It answers both 'what' ('Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing') and an explicit 'when' trigger ('Use when testing semantic HTML...').

3 / 3

Trigger Term Quality

Phrases like 'semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast' are natural terms users would say when requesting a11y testing, giving good coverage.

3 / 3

Distinctiveness Conflict Risk

The niche is clear (a11y debugging via DevTools MCP based on web.dev) with distinct triggers unlikely to conflict with unrelated skills.

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.

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.