android-mobile-frontend-design
Design Android mobile frontend experiences from scratch, improve existing screens, and fix UI issues with brand-forward, localization-safe, overflow-safe guidance across Compose and Views.
60
51%
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-mobile-frontend-design/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 carving out an Android mobile UI niche with concrete actions and framework mentions (Compose and Views). However, it lacks an explicit 'Use when...' clause which hurts completeness, and could benefit from more natural trigger terms that users would actually say when requesting help.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Android UI, screen layouts, Jetpack Compose components, XML Views, or mobile design issues.'
Include additional natural trigger terms users would say, such as 'Jetpack Compose', 'Material Design', 'XML layout', 'Android screen', 'mobile app UI', or '.kt/.xml files'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Design Android mobile frontend experiences from scratch', 'improve existing screens', 'fix UI issues', with qualifiers like 'brand-forward, localization-safe, overflow-safe guidance across Compose and Views'. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with designing, improving, and fixing Android UI, 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 good terms like 'Android', 'Compose', 'Views', 'UI issues', 'localization', but misses common user phrases like 'layout', 'XML', 'Jetpack Compose', 'Material Design', 'responsive', 'screen design', or file extensions. Users might say 'fix my Android layout' or 'Jetpack Compose UI' which aren't covered. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Android-specific mobile frontend with both Compose and Views, plus specific qualifiers (localization-safe, overflow-safe, brand-forward). Unlikely to conflict with generic UI, web frontend, or iOS skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is comprehensive in scope but suffers significantly from verbosity—it reads more like a mobile design textbook chapter than a concise skill file for Claude. Much of the content restates general UX and Android design principles that Claude already knows. The structure and operating modes are well-conceived, but the lack of concrete code examples, specific component patterns, or executable artifacts limits actionability.
Suggestions
Cut the content by 50-60%: remove general UX wisdom Claude already knows (e.g., 'The first screenful answers three questions instantly', 'Motion should reveal structure') and keep only project-specific rules, non-obvious constraints, and concrete patterns.
Move the detailed sections (Localization Best Practices, Adaptive Best Practices, Screen-family best practices, Anti-Patterns) into reference files and link to them from a concise overview in the main skill.
Add concrete, executable examples: show actual Compose/XML code snippets for key patterns like overflow-safe buttons, adaptive layouts, or RTL-safe spacing rather than just describing principles.
Add explicit validation checkpoints to the workflow: e.g., 'Run pseudolocalization pass and verify no clipping before proceeding to step 6' with specific commands or tool references.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines, with extensive prose that explains design concepts Claude already understands (what 'brand-forward' means, what makes UI 'premium', basic mobile design principles). Sections like 'Amazing UI Quality Bar', 'Design Direction', and 'Anti-Patterns' are largely restating general UX knowledge rather than providing project-specific or tool-specific guidance Claude wouldn't already know. | 1 / 3 |
Actionability | The skill provides structured guidance with clear operating modes and workflow steps, but lacks concrete executable code, specific component examples, or copy-paste-ready snippets. The 'Examples' section references shell commands but doesn't show actual design output or code. It's more of a design philosophy document than actionable implementation guidance. | 2 / 3 |
Workflow Clarity | The workflow section provides a clear 8-step sequence with handoff routing, and the operating modes (create/improve/fix) are well-defined. However, there are no explicit validation checkpoints or feedback loops within the design process itself—step 7 mentions 'validate' but doesn't specify how to verify or what to do if validation fails beyond the general 'Done Checklist'. | 2 / 3 |
Progressive Disclosure | The skill references external files (references/patterns.md, references/scenarios.md) and handoff skills, which is good progressive disclosure. However, the main file itself is monolithic with enormous inline sections (Design Direction, Localization, Adaptive, etc.) that could be split into reference files. The content that is inline far exceeds what an overview should contain. | 2 / 3 |
Total | 7 / 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.