android-compose-accessibility
Make Compose interfaces accessible with semantics, announcements, contrast, focus order, and adaptive touch targets.
48
36%
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 ./skills/android-compose-accessibility/SKILL.mdQuality
Discovery
50%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 on specificity and distinctiveness, listing concrete accessibility actions specific to Jetpack Compose. However, it lacks an explicit 'Use when...' clause, which is critical for Claude to know when to select this skill. It also misses common user-facing trigger terms like 'a11y', 'TalkBack', 'screen reader', or 'Jetpack Compose' (spelled out).
Suggestions
Add a 'Use when...' clause such as 'Use when the user asks about accessibility in Jetpack Compose, screen reader support, TalkBack compatibility, or a11y improvements.'
Include common trigger term variations like 'Jetpack Compose', 'a11y', 'TalkBack', 'screen reader', 'WCAG', and 'accessibility' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: semantics, announcements, contrast, focus order, and adaptive touch targets. These are distinct, actionable accessibility concerns in Jetpack Compose. | 3 / 3 |
Completeness | Describes what the skill does but has no 'Use when...' clause or equivalent explicit trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'when' is entirely absent (not even implied beyond the domain), this scores at 1. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'Compose', 'accessible', 'semantics', 'announcements', 'contrast', 'focus order', and 'touch targets', but misses common user variations like 'a11y', 'screen reader', 'TalkBack', 'Jetpack Compose', 'accessibility', or 'WCAG'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Compose' (Jetpack Compose) with specific accessibility concerns like semantics, announcements, focus order, and touch targets creates a clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads like a generic template filled with high-level platitudes rather than actionable accessibility guidance for Jetpack Compose. It completely lacks concrete code showing Modifier.semantics, contentDescription, mergeDescendants, clearAndSetSemantics, or any other Compose accessibility API. The workflow and examples are too abstract to help Claude actually implement accessibility improvements.
Suggestions
Add concrete, executable Compose code examples showing key accessibility patterns: Modifier.semantics { contentDescription = '...' }, mergeDescendants = true, heading(), Role.Button, and custom actions.
Replace the generic workflow with accessibility-specific steps: 1) Audit semantics tree with Layout Inspector, 2) Add/fix semantic properties, 3) Validate with TalkBack, 4) Check contrast ratios, 5) Verify touch targets ≥48dp.
Include specific validation commands or code for checking accessibility (e.g., using AccessibilityValidator, semantics node assertions in tests, or contrast ratio calculation).
Remove generic content like 'Select the lowest-friction UI pattern' and 'Prefer measured performance work' that aren't specific to accessibility and waste tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably concise but includes generic workflow steps (e.g., 'Select the lowest-friction UI pattern') and guardrails that are not specific to accessibility. The 'When To Use' and 'Done Checklist' sections contain boilerplate that doesn't add accessibility-specific value. | 2 / 3 |
Actionability | The skill lacks any concrete code examples showing how to implement accessibility in Compose—no Modifier.semantics{} usage, no contentDescription examples, no mergeDescendants patterns, no contrast checking code. The examples section only provides gradle commands without showing actual accessibility implementation patterns. | 1 / 3 |
Workflow Clarity | The workflow is generic and abstract ('Identify whether the target surface is Compose...', 'Select the lowest-friction UI pattern...') with no accessibility-specific validation steps. There are no checkpoints for verifying semantics trees, running TalkBack testing, or validating contrast ratios—critical for an accessibility skill. | 1 / 3 |
Progressive Disclosure | The document has clear section structure and references official Android documentation links. However, it doesn't reference any supplementary files for detailed patterns (e.g., a SEMANTICS_PATTERNS.md or CONTRAST_GUIDE.md), and the content that is present is too shallow to serve as a useful overview. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 Passed | |
- Repository
- krutikJain/android-agent-skills
- Commit
c5bf673
- 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.