android-design-system
Enforce Material Design 3 and design token usage in Jetpack Compose apps. Use when implementing M3 components, color schemes, or design tokens in Android. (triggers: **/*Screen.kt, **/ui/theme/**, **/compose/**, MaterialTheme, Color, Typography, Modifier, Composable)
82
77%
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/android-design-system/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description with excellent trigger term coverage and clear completeness. Its main weakness is that the 'what' portion could be more specific about the concrete actions performed (e.g., validating token usage, replacing hardcoded values, enforcing theme consistency). The explicit trigger patterns for file paths and code keywords are a notable strength for disambiguation.
Suggestions
Expand the capability description with more concrete actions, e.g., 'Validates design token usage, replaces hardcoded colors with theme tokens, enforces M3 component patterns in Jetpack Compose apps.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Material Design 3, Jetpack Compose) and some actions ('enforce', 'implementing M3 components, color schemes, design tokens'), but doesn't list multiple concrete actions like 'validate token usage, replace hardcoded colors, apply dynamic color schemes'. | 2 / 3 |
Completeness | Clearly answers both 'what' (enforce Material Design 3 and design token usage in Jetpack Compose apps) and 'when' (when implementing M3 components, color schemes, or design tokens in Android), with explicit trigger patterns listed. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including file patterns (*Screen.kt, ui/theme/**, compose/**) and code-level keywords (MaterialTheme, Color, Typography, Modifier, Composable) that users and code contexts would naturally contain. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche combining Material Design 3, design tokens, and Jetpack Compose specifically for Android. The file patterns and specific keywords like MaterialTheme and Composable make it unlikely to conflict with generic UI or design skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a concise, well-structured skill that effectively communicates Material Design 3 token usage rules and anti-patterns. However, it lacks concrete executable code examples showing correct implementations and has an empty References section. Adding a small code example of a properly themed Composable and populating references would significantly improve its actionability.
Suggestions
Add a concrete code example showing a correctly themed Composable function using MaterialTheme.colorScheme and MaterialTheme.typography (e.g., a simple Card or Text component).
Populate the References section with links to example Color.kt/Theme.kt/Type.kt templates or relevant documentation files.
Add a brief before/after code snippet in the Anti-Patterns section to make the corrections more actionable (e.g., showing `Color(0xFF6200EE)` replaced with `MaterialTheme.colorScheme.primary`).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. Every line conveys actionable information without explaining what Material Design or Jetpack Compose is. No unnecessary padding or context Claude would already know. | 3 / 3 |
Actionability | Provides specific token access patterns (e.g., `MaterialTheme.colorScheme.*`) and clear anti-patterns with concrete bad examples, but lacks executable code snippets showing correct usage in a Composable function. No copy-paste ready examples of a properly themed component. | 2 / 3 |
Workflow Clarity | The guidelines mention file organization (Color.kt, Theme.kt, Type.kt in ui/theme/) and the mapping process, but the sequence is implicit rather than explicit. For a design system enforcement skill, a clearer step-by-step workflow (e.g., 1. check for hardcoded values, 2. replace with tokens, 3. verify theme preview) would improve clarity. | 2 / 3 |
Progressive Disclosure | The References section is empty, which is a missed opportunity to link to example files or detailed token reference docs. The structure is clean with Guidelines and Anti-Patterns sections, but for a skill that could benefit from linking to example Color.kt/Theme.kt templates, the empty references section is a gap. | 2 / 3 |
Total | 9 / 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.
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
19a1140
- 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.