android-accessibility
Expert checklist and prompts for auditing and fixing Android accessibility issues, especially in Jetpack Compose.
62
52%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.github/skills/android-accessibility/SKILL.mdQuality
Discovery
32%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 identifies a clear domain (Android/Jetpack Compose accessibility) but lacks the explicit trigger guidance needed for Claude to reliably select it. It would benefit from specific concrete actions and a 'Use when...' clause with natural user phrases.
Suggestions
Add a 'Use when...' clause with trigger terms like 'Android accessibility', 'Compose a11y', 'TalkBack support', 'content descriptions', or 'accessibility audit'.
List specific concrete actions such as 'add contentDescription modifiers', 'fix focus traversal order', 'implement semantic properties', or 'resolve Accessibility Scanner warnings'.
Include common accessibility-related terms users might mention: 'screen reader', 'a11y', 'WCAG', 'accessibility testing', '.semantics modifier'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Android accessibility, Jetpack Compose) and mentions actions ('auditing and fixing'), but lacks specific concrete actions like 'add content descriptions', 'fix focus order', or 'implement TalkBack support'. | 2 / 3 |
Completeness | Describes what it does ('checklist and prompts for auditing and fixing') but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Android', 'accessibility', 'Jetpack Compose', but misses common variations users might say such as 'a11y', 'TalkBack', 'screen reader', 'content description', or 'accessibility scanner'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Android accessibility' and 'Jetpack Compose' provides some distinctiveness, but 'accessibility issues' is broad enough to potentially overlap with general accessibility or other mobile accessibility skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured accessibility checklist that efficiently covers key Android/Compose accessibility concerns. Its main weakness is the lack of executable code examples showing how to implement the fixes (e.g., actual Modifier.semantics usage), which limits immediate actionability for an agent.
Suggestions
Add executable Kotlin/Compose code snippets for each fix, such as showing how to properly use `Modifier.semantics(mergeDescendants = true)` or implement MinTouchTargetSize
Include a brief sequential workflow for conducting an accessibility audit (e.g., 1. Run TalkBack, 2. Check each category, 3. Verify fixes with accessibility scanner)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting only essential accessibility criteria without explaining what accessibility is or how Android/Compose works. Every section delivers actionable standards without padding. | 3 / 3 |
Actionability | Provides specific standards (48x48dp, 4.5:1 contrast) and mentions specific APIs (Modifier.semantics, mergeDescendants), but lacks executable code examples. The fixes are described rather than demonstrated with copy-paste ready snippets. | 2 / 3 |
Workflow Clarity | The checklist format provides clear categories to check, but lacks a sequential workflow for conducting an audit. No validation steps or feedback loops for verifying fixes are included. | 2 / 3 |
Progressive Disclosure | For a skill under 50 lines with a focused scope, the content is well-organized into clear sections with logical grouping. No external references are needed for this checklist-style skill. | 3 / 3 |
Total | 10 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Commit
3f68e39
- 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.