CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

audit-accessibility

Ensure the plugin's custom UI components are accessible to users with screen readers and other assistive technologies.

Quality

73%

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 ./.agents/skills/audit-accessibility/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 lean, well-sequenced audit workflow with concrete gradle commands and specific accessibility API checks. Its weaknesses are redundant restatement of the objective, generic manual-test boilerplate, and verification steps that lack explicit error-recovery loops and measurable criteria (e.g., WCAG contrast ratios).

Suggestions

Remove the duplicated objective — the intro paragraph and the "## Objective" section repeat the description verbatim; a single statement suffices.

Replace the generic "Suggest manual test steps" boilerplate with the actual manual test steps or a tighter one-line instruction, since the current paragraph explains a process rather than instructing action.

Add a feedback loop after the step 6 verification (e.g., "If tests fail, fix the accessibility issue and re-run ./gradlew test before proceeding") and specify the WCAG contrast threshold or a tool to check it.

DimensionReasoningScore

Conciseness

The objective sentence is repeated verbatim three times ("You are tasked with ensuring...", "## Objective / Ensure the plugin's custom UI components are accessible..."), and the "Suggest manual test steps" boilerplate in step 6 pads the skill; the workflow steps themselves are lean, so this sits at "mostly efficient but could be tightened" rather than noticeably verbose.

3 / 5

Actionability

Concrete commands ("./gradlew testClasses", "./gradlew verifyPlugin") and specific API calls ("getAccessibleContext().setAccessibleName(...)") give mostly executable guidance; the ellipsis placeholders are not copy-paste ready and "verify they meet WCAG contrast guidelines" gives no contrast ratio or checking tool, preventing a 5.

4 / 5

Workflow Clarity

A clear 7-step sequence with baseline validation (step 1) and final regression checks (step 6) covers most checkpoints; it falls short of 5 because there is no explicit error-recovery feedback loop (e.g., "if tests fail, fix and re-run") after verification. The operation is non-destructive, so the cap-at-3 rule for unvalidated destructive/batch operations does not apply.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, needs no external reference files, and is cleanly organized into numbered sections with descriptive headers — the rubric's simple-skill note states this merits a 5 with just well-organized sections.

5 / 5

Total

16

/

20

Passed

Description

61%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 clear, appropriately scoped description that identifies a specific niche (plugin custom UI accessibility) but describes only a single high-level action. Its main weaknesses are the missing "Use when..." trigger clause and the absence of the specific sub-actions the skill actually performs.

Suggestions

Add a "Use when..." clause (e.g., "Use when auditing plugin UI for screen-reader support or when users mention accessibility, a11y, or WCAG") to raise completeness above 3.

Enumerate the concrete actions the skill performs (e.g., "set accessible names/descriptions on custom components, verify focus traversal, and check WCAG color contrast") to strengthen specificity.

Include natural synonyms such as "a11y" and "WCAG" so the description matches the vocabulary users actually say.

DimensionReasoningScore

Specificity

"Ensure the plugin's custom UI components are accessible to users with screen readers and other assistive technologies" names a concrete domain but offers only one generic action ("ensure...accessible"); it does not list the several specific actions (e.g., accessible names, contrast checks, focus handling) needed for a 4.

3 / 5

Completeness

The description clearly answers "what" but contains no "Use when..." clause or equivalent trigger guidance, which the rubric explicitly caps at 3; it is above 2 because the "what" is specific and clear.

3 / 5

Trigger Term Quality

"accessible", "screen readers", and "assistive technologies" are natural phrases users would say when needing this skill, giving good keyword coverage; common synonyms like "a11y", "WCAG", or "accessibility audit" are missing, keeping it below 5.

4 / 5

Distinctiveness Conflict Risk

"the plugin's custom UI components" carves a fairly distinct niche (IDE plugin UI accessibility) with only minor overlap risk against general accessibility or UI-testing skills; it lacks the distinct trigger phrases needed for a 5.

4 / 5

Total

14

/

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

flutter/flutter-intellij

Path

.agents/skills/audit-accessibility/SKILL.md

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.