android-development
Android development guidelines for Kotlin with clean architecture, MVI pattern, Material Design, and best practices for building robust mobile applications
47
35%
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 ./android-development/SKILL.mdQuality
Discovery
32%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 identifies a clear technical domain with specific architectural patterns but fails to provide actionable trigger guidance. It reads more like a topic summary than a skill selection guide, lacking concrete actions and explicit 'when to use' criteria that would help Claude choose this skill from a large pool.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'Android app', 'Kotlin code', 'mobile development', 'Jetpack', or when users mention specific Android components.
List concrete actions the skill enables, such as 'structure Android projects', 'implement ViewModel/Repository patterns', 'create Composable UI components', 'handle state management'.
Include common file extensions and Android-specific terms users might mention: '.kt files', 'Activity', 'Fragment', 'Compose', 'Gradle'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Android development) and mentions specific patterns/technologies (Kotlin, clean architecture, MVI pattern, Material Design), but doesn't list concrete actions like 'create activities', 'implement ViewModels', or 'structure modules'. | 2 / 3 |
Completeness | Describes what the skill covers (Android development guidelines) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Android', 'Kotlin', 'Material Design', 'MVI' that developers would use, but misses common variations like 'mobile app', 'Android app', 'Jetpack Compose', or file extensions like '.kt'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of Android + Kotlin + MVI + clean architecture is fairly specific, but 'mobile applications' and 'best practices' are generic terms that could overlap with iOS or general mobile development skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a comprehensive overview of Android development conventions but reads more like a style guide than actionable instructions. It lacks executable code examples, concrete implementation patterns, and clear workflows with validation steps. The content would benefit from specific code snippets for MVI setup, navigation configuration, and testing patterns rather than abstract descriptions.
Suggestions
Add executable code examples for key patterns: MVI ViewModel setup, Navigation Component configuration, and repository implementation with actual Kotlin code
Create clear step-by-step workflows for common tasks like 'Setting up a new feature module' or 'Implementing a new screen' with validation checkpoints
Remove generic programming advice Claude already knows (SOLID principles, basic naming conventions) and focus on Android/project-specific patterns
Split detailed content (testing examples, authentication implementation, DI setup) into referenced files and keep SKILL.md as a concise overview
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some guidance Claude already knows (basic Kotlin naming conventions, SOLID principles, general programming best practices). Could be tightened to focus on Android-specific patterns and project conventions. | 2 / 3 |
Actionability | Provides structural guidance and naming conventions but lacks executable code examples. The project structure diagram is helpful, but MVI pattern, navigation setup, and authentication flow descriptions are abstract rather than copy-paste ready implementations. | 2 / 3 |
Workflow Clarity | No clear multi-step workflows with validation checkpoints. Authentication flow lists screens but doesn't sequence implementation steps. Testing section describes what to test but not how to structure the testing workflow or validate results. | 1 / 3 |
Progressive Disclosure | Content is organized into logical sections with clear headers, but it's a monolithic document with no references to separate detailed files. API patterns, testing examples, and authentication implementation details could be split into referenced documents. | 2 / 3 |
Total | 7 / 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 — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 13 / 16 Passed | |
- Repository
- mindrally/skills
- Commit
47f47c1
- 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.