CtrlK
BlogDocsLog inGet started
Tessl Logo

accessibility

Primary accessibility skill for VS Code. REQUIRED for new feature and contribution work, and also applies to updates of existing UI. Covers accessibility help dialogs, accessible views, verbosity settings, signals, ARIA announcements, keyboard navigation, and ARIA labels/roles.

70

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 content is highly actionable with concrete code skeletons and clear per-section workflows anchored by a verification checklist. Conciseness and progressive disclosure are good but not exceptional due to some inline detail that could be externalized.

DimensionReasoningScore

Conciseness

The body is dense and code-forward, adding codebase-specific knowledge (enum entries, file paths, registration APIs) Claude lacks rather than generic concepts, with only minor explanatory prose in section intros that could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready TypeScript skeletons with real imports, AccessibleViewProviderId enum entries, verbosity setting registration, and AccessibleViewRegistry.register calls covering the common cases.

5 / 5

Workflow Clarity

Each section is sequenced with numbered Steps (1-4) and capped by a per-feature Checklist, but there is no explicit validate-then-fix error-recovery loop, so it sits at 4 rather than 5.

4 / 5

Progressive Disclosure

No bundle files exist (references/scripts/assets empty), but the body is well-organized into 7 numbered sections plus a checklist and a Key Files index; some detailed skeletons could be split out, leaving minor organization gaps.

4 / 5

Total

17

/

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.

The description is strong: it pairs an explicit capability list with clear trigger guidance and a distinct VS Code accessibility niche. The only weakness is that capabilities are phrased as covered topics rather than concrete verbs.

DimensionReasoningScore

Specificity

Lists several specific capability areas ("accessibility help dialogs, accessible views, verbosity settings, signals, ARIA announcements, keyboard navigation, and ARIA labels/roles"), but the "Covers..." phrasing enumerates topics rather than concrete actions like extract/fill/merge, so it sits just below a 5.

4 / 5

Completeness

Explicitly answers what ("Primary accessibility skill for VS Code... Covers [capability list]") and when ("REQUIRED for new feature and contribution work, and also applies to updates of existing UI"), matching the 5 anchor's clear what + concrete when.

5 / 5

Trigger Term Quality

Includes natural user-facing terms ("new feature and contribution work", "updates of existing UI", "VS Code") a developer would actually say, but misses common synonyms/variations, fitting the 4 anchor.

4 / 5

Distinctiveness Conflict Risk

"Primary accessibility skill for VS Code" plus the explicit REQUIRED/when clause carves a clear niche with minimal overlap risk against other skills.

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
microsoft/vscode
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.