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.

64

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/accessibility/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

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 and clear sequencing, but it is verbose for a single file and lacks per-workflow validation checkpoints and external progressive disclosure. Splitting reference detail into bundle files and adding verification steps would raise the weaker dimensions.

Suggestions

Add explicit validation/test checkpoints inside each workflow (e.g., 'Open the help dialog with the accessibility keybinding and confirm the hint announces') to support error-recovery feedback loops.

Move detailed code skeletons and ARIA attribute reference lists into reference files under references/ and link to them one level deep, keeping SKILL.md as a lean overview.

Collapse the two help-dialog implementation skeletons into one canonical pattern, noting the Disposable/IInstantiationService variant only when injected services are needed, to reduce length.

DimensionReasoningScore

Conciseness

The body is dense VS Code-internal API guidance with no basic-concept padding, but at ~300 lines it includes redundant dual code skeletons and lengthy feature lists that could be tightened.

2 / 3

Actionability

Provides complete, executable TypeScript skeletons with exact API names, file paths, and registration calls — copy-paste ready rather than pseudocode.

3 / 3

Workflow Clarity

Each section has clearly numbered steps plus a comprehensive end checklist, but there are no per-workflow validation/test checkpoints or error-recovery feedback loops beyond a passing screen-reader test mention.

2 / 3

Progressive Disclosure

Sections are well-organized, but the skill is a single ~300-line monolithic file with no bundle files; reference-style detail such as code skeletons and ARIA attribute lists is inline rather than split into one-level-deep references.

2 / 3

Total

9

/

12

Passed

Description

85%

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, distinctive, and covers both what the skill does and when to use it with explicit trigger guidance. Its weakest point is trigger-term quality, where 'contribution work' is jargon and natural keyword variations are absent.

DimensionReasoningScore

Specificity

Lists multiple concrete capability areas — 'accessibility help dialogs, accessible views, verbosity settings, signals, ARIA announcements, keyboard navigation, and ARIA labels/roles' — rather than vague language.

3 / 3

Completeness

It answers both what ('Covers...') and when ('REQUIRED for new feature and contribution work, and also applies to updates of existing UI'), with explicit trigger guidance equivalent to a 'Use when' clause.

3 / 3

Trigger Term Quality

'new feature' is a natural user term, but 'contribution work' is VS Code jargon and no common keyword variations are enumerated, so coverage is partial.

2 / 3

Distinctiveness Conflict Risk

'Primary accessibility skill for VS Code' is a clear, distinct niche with scoped triggers, making overlap with other skills unlikely.

3 / 3

Total

11

/

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
posit-dev/positron
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.