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.
64
77%
Does it follow best practices?
Impact
—
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 solid skill description with clear 'what' and 'when' clauses, good trigger terms covering natural user language (M3, color schemes, typography, design tokens), and a distinct niche. The main weakness is that the 'what' portion could be more specific about the concrete actions performed beyond 'enforce theming and design token usage'.
Suggestions
Expand the capability list with more concrete actions, e.g., 'Validates color token usage, enforces dynamic color schemes, checks typography scale compliance, and ensures proper M3 component theming 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', 'apply typography scales', 'check component compliance', etc. | 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 explicit trigger guidance. | 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 common variations well. | 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
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 efficiently communicates M3 theming conventions and anti-patterns. Its main weaknesses are the lack of executable code examples (e.g., a minimal Theme.kt setup) and an empty References section that could point to more detailed guidance. The anti-patterns section is a strength, providing clear guardrails.
Suggestions
Add a minimal executable code example showing a correct Theme.kt or Color.kt setup with lightColorScheme/darkColorScheme to improve actionability.
Either populate the References section with links to relevant files/docs or remove it to avoid the appearance of incomplete content.
Add a brief example of correct usage alongside each anti-pattern (e.g., show the correct MaterialTheme.colorScheme.primary usage next to the hardcoded Color(0xFF...) anti-pattern).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It assumes Claude knows what Material Design 3, Jetpack Compose, ColorScheme, and Typography are. Every line adds actionable information without padding. | 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 usage (e.g., a sample Theme.kt or Color.kt). The guidance is specific but not copy-paste ready. | 2 / 3 |
Workflow Clarity | For a simple skill like this, the workflow is mostly clear—define files, map values, access through MaterialTheme. However, the sequencing is implicit rather than explicit, and there's no validation step (e.g., how to verify tokens are correctly applied or catch hardcoded values). | 2 / 3 |
Progressive Disclosure | The References section is empty, which is a missed opportunity. The content is appropriately brief for a SKILL.md overview, but it neither provides deeper reference files nor signals where to find more detailed guidance on theme setup patterns. | 2 / 3 |
Total | 9 / 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
556618c
- 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.