android-material3-design-system
Apply Material 3 tokens, color, type, spacing, adaptive components, and theme ownership in Android apps.
55
45%
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-material3-design-system/SKILL.mdQuality
Discovery
67%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 in specificity and distinctiveness, clearly identifying the Material 3 design system for Android as its domain and listing concrete capabilities. However, it lacks an explicit 'Use when...' clause and misses common user-facing trigger terms like 'M3', 'Material Design', 'Jetpack Compose', or 'dynamic color', which limits its effectiveness for skill selection.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Material Design theming, M3 components, dynamic color, or styling Android/Jetpack Compose apps.'
Include common trigger term variations such as 'M3', 'Material Design', 'Material You', 'Jetpack Compose theming', 'dynamic color', and 'dark theme' to improve matching against natural user queries.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Apply Material 3 tokens, color, type, spacing, adaptive components, and theme ownership' — these are distinct, concrete capabilities in the Material 3 design system domain. | 3 / 3 |
Completeness | Clearly answers 'what' (apply Material 3 tokens, color, type, spacing, etc. in Android apps) but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric. | 2 / 3 |
Trigger Term Quality | Includes relevant terms like 'Material 3', 'tokens', 'color', 'type', 'spacing', 'adaptive components', 'theme', and 'Android apps', but misses common user variations like 'M3', 'Material Design', 'Jetpack Compose theming', 'dark mode', 'dynamic color', or 'Material You'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Material 3' and 'Android apps' creates a very clear niche. It is unlikely to conflict with generic UI/design skills or non-Android theming skills due to the specific technology stack mentioned. | 3 / 3 |
Total | 10 / 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 more like a project management checklist than an actionable technical guide. It lacks any concrete code examples showing how to actually apply Material 3 tokens, define color schemes, set up typography, or configure themes in Compose or XML. The workflow and examples sections are too abstract to guide Claude through actual implementation tasks.
Suggestions
Add concrete, executable Kotlin/Compose code examples showing Material 3 theme setup (e.g., MaterialTheme with colorScheme, typography, and shapes), token usage in components, and dynamic color configuration.
Replace the abstract workflow steps with specific, sequenced instructions like: 'Define color scheme using dynamicDarkColorScheme()/dynamicLightColorScheme(), wrap root composable in MaterialTheme { }, reference tokens via MaterialTheme.colorScheme.primary'.
Add a validation step with concrete commands or checks, such as screenshot testing commands or accessibility contrast verification, to create feedback loops in the workflow.
Annotate the official references with brief descriptions of what each covers (e.g., 'Migration from M2 to M3', 'Custom design system tokens') to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably structured and avoids explaining what Material 3 is, but includes some filler sections (e.g., the 'When To Use' trigger keywords, vague workflow steps) that don't add actionable value. The anti-patterns section is useful but could be tighter. | 2 / 3 |
Actionability | The skill provides no concrete code examples, no executable Compose/Kotlin snippets, no specific theme configuration, and no copy-paste-ready Material 3 token usage. The workflow steps are abstract descriptions ('Build the UI around stable state') rather than concrete instructions. The example commands are just gradle builds with no explanation of what they demonstrate or how to apply tokens. | 1 / 3 |
Workflow Clarity | The workflow is a sequence of vague, high-level steps ('Identify whether the target surface is Compose, View system, or mixed') with no validation checkpoints, no concrete commands at each step, and no feedback loops. For a skill involving theme application across surfaces, there's no clear process for verifying correct token application or visual consistency. | 1 / 3 |
Progressive Disclosure | The content is organized into clear sections with references to external official docs and handoff skills. However, there are no internal reference files (e.g., a TOKENS.md or MIGRATION.md) that would provide deeper guidance, and the official references are just bare links without context about what each covers. | 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.