CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

android-accessibility

Expert checklist and prompts for auditing and fixing Android accessibility issues, especially in Jetpack Compose.

Quality

80%

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/ui/android-accessibility/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 a well-organized, concise accessibility checklist with concrete APIs and thresholds that assumes Claude's intelligence. Its main gap is the absence of complete copy-paste code examples and explicit validation/feedback steps for the audit findings.

Suggestions

Add one or two short executable Compose code snippets (e.g., a clickable Icon with contentDescription and MinTouchTargetSize) to make guidance copy-paste ready.

Include a brief verification step prompting Claude to confirm each flagged issue against its standard (e.g., re-check the computed contrast ratio) before reporting, adding a light feedback loop to the audit workflow.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no explaining what a composable or WCAG is); every token earns its place with specific thresholds and APIs inline.

5 / 5

Actionability

Provides concrete actionable guidance with specific APIs (contentDescription = null, Modifier.semantics(mergeDescendants = true), heading()) and thresholds (48x48dp, 4.5:1); not 5 because there are no complete copy-paste code blocks, only inline references.

4 / 5

Workflow Clarity

As a simple single-purpose auditing checklist the single action (analyze the component for these aspects) is unambiguous and clearly sectioned; not 5 because it is a parallel checklist rather than a sequenced workflow with explicit validation checkpoints or feedback loops.

4 / 5

Progressive Disclosure

A simple skill well under 50 lines with no need for external references (none exist), and it is cleanly organized into well-labeled sections, satisfying the simple-skill exception.

5 / 5

Total

18

/

20

Passed

Description

65%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 names a specific, distinctive niche with concrete actions but lacks an explicit "Use when..." trigger clause, which caps its completeness and limits overall effectiveness. Trigger term coverage is good though missing common synonyms like a11y and TalkBack.

Suggestions

Add an explicit trigger clause, e.g. "Use when auditing or fixing accessibility issues in Jetpack Compose apps, or when the user mentions TalkBack, a11y, WCAG, or screen-reader support."

Expand action coverage beyond "auditing and fixing" to specific concrete actions like checking content descriptions, verifying touch targets, and validating color contrast.

Include common synonyms (a11y, TalkBack, screen reader, WCAG) to broaden trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain ("Android accessibility", "Jetpack Compose") and two concrete actions ("auditing and fixing"), matching the 1-2 concrete actions anchor; not 4 because it lists only two verbs rather than several specific actions.

3 / 5

Completeness

Provides a clear "what" (checklist and prompts for auditing/fixing accessibility) but no "Use when..." trigger clause, capping completeness at 3 per the missing-trigger-guidance rule.

3 / 5

Trigger Term Quality

Includes natural terms a user would say ("Android accessibility", "Jetpack Compose", "auditing", "fixing") with good coverage; not 5 because synonyms like a11y, TalkBack, screen reader, and WCAG are missing.

4 / 5

Distinctiveness Conflict Risk

"Android accessibility... Jetpack Compose" carves a clear niche with distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

15

/

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

new-silvermoon/awesome-android-agent-skills

Path

.github/skills/ui/android-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.