android-design-system
Enforce Material Design 3 theming and design token usage in Jetpack Compose. Use when implementing M3 components, color schemes, typography, or design tokens.
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 solid description with clear 'what' and 'when' clauses, strong trigger terms covering the M3/Compose ecosystem, and excellent distinctiveness. The main weakness is that the specificity of concrete actions could be improved—it says 'enforce' but doesn't enumerate what specific enforcement actions it performs (e.g., validating token usage, suggesting correct color roles, checking dynamic color implementation).
Suggestions
Expand the 'what' portion with more concrete actions, e.g., 'Validates color role usage, enforces dynamic color support, checks typography scale compliance, and ensures proper MaterialTheme token references in Jetpack Compose.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Material Design 3, Jetpack Compose) and some actions ('enforce theming', 'design token usage'), but doesn't list multiple concrete actions like 'validate color tokens', 'check typography scales', 'audit component usage'. | 2 / 3 |
Completeness | Clearly answers both what ('Enforce Material Design 3 theming and design token usage in Jetpack Compose') and when ('Use when implementing M3 components, color schemes, typography, or design tokens') with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Material Design 3', 'M3', 'Jetpack Compose', 'color schemes', 'typography', 'design tokens', 'theming'. These cover the main variations a developer would use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche combining Material Design 3 + Jetpack Compose + design tokens. Unlikely to conflict with generic UI, theming, or Android skills due to the precise technology stack mentioned. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A concise, well-structured skill that clearly communicates M3 theming conventions and anti-patterns. Its main weakness is the lack of concrete, executable code examples (e.g., a sample Theme.kt or colorScheme definition) and an empty References section that should either contain links or be removed.
Suggestions
Add a short, copy-paste-ready code example showing a minimal Theme.kt with lightColorScheme/darkColorScheme setup and MaterialTheme usage in a composable.
Either populate the References section with links to relevant M3/Compose documentation or remove the empty header.
| 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 already knows. | 3 / 3 |
Actionability | Provides specific file names, token access patterns, and anti-patterns with concrete examples of what to avoid, but lacks executable code examples showing correct implementations (e.g., a sample Theme.kt or Color.kt snippet). | 2 / 3 |
Workflow Clarity | This is a simple, single-purpose skill (design token enforcement) with no multi-step destructive process. The single action—use MaterialTheme tokens instead of hardcoded values—is unambiguous and clearly stated. | 3 / 3 |
Progressive Disclosure | The References section is empty, which is a missed opportunity. The structure is reasonable with Guidelines and Anti-Patterns sections, but the empty References header is a flaw, and no links to further resources or examples are provided. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
4c72e76
- 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.