android-architecture-clean
Apply clean architecture boundaries, use cases, repositories, and lifecycle-aware presentation models in Android projects.
41
27%
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-architecture-clean/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 architectural domain (clean architecture in Android) and names relevant patterns, but it reads more like a topic label than an actionable skill description. It lacks a 'Use when...' clause, concrete action verbs for specific tasks, and common keyword variations that would help Claude reliably select this skill.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about structuring Android projects, separating concerns, or implementing clean architecture patterns.'
Include common keyword variations users might say, such as 'MVVM', 'ViewModel', 'domain layer', 'data layer', 'Jetpack components', 'dependency injection', or 'separation of concerns'.
List more concrete actions, e.g., 'Structure module boundaries, create use case classes, define repository interfaces, implement lifecycle-aware ViewModels, and set up dependency injection for Android projects.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Android projects) and several architectural concepts (clean architecture boundaries, use cases, repositories, lifecycle-aware presentation models), but these are more like architectural patterns than concrete actions. It doesn't list specific tasks like 'create repository interfaces', 'implement use case classes', or 'set up dependency injection modules'. | 2 / 3 |
Completeness | Describes what the skill does (apply clean architecture patterns in Android projects) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' portion is also only moderately clear, warranting a score of 1. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'clean architecture', 'use cases', 'repositories', 'lifecycle-aware', and 'Android' which users familiar with the pattern would use. However, it misses common variations like 'MVVM', 'ViewModel', 'domain layer', 'data layer', 'presentation layer', 'Jetpack', or 'separation of concerns'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'clean architecture' and 'Android' provides some distinctiveness, but it could overlap with general Android development skills or general architecture skills. The lack of explicit trigger conditions increases the risk of incorrect activation or missed activation. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a high-level process document than an actionable skill for Claude. It lacks any concrete code examples showing clean architecture patterns in Android (use cases, repositories, ViewModels), relying instead on abstract principles and vague workflow steps. The anti-patterns and guardrails sections describe general software engineering wisdom rather than Android-specific pitfalls with concrete illustrations.
Suggestions
Add concrete Kotlin code examples showing a use case class, repository interface, and ViewModel implementation following clean architecture boundaries - these should be copy-paste ready.
Replace the abstract workflow steps with specific, sequenced instructions (e.g., 'Create domain layer interfaces first, then implement repository in data layer, then wire use case into ViewModel') with validation checkpoints.
Include a concrete before/after example showing how to refactor a tightly-coupled Android component into clean architecture layers.
Remove generic software engineering advice Claude already knows (e.g., 'Apply the smallest change that improves correctness') and replace with Android-specific guidance like Hilt module setup for dependency injection across layers.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is moderately efficient but includes some filler language and vague phrasing ('Keep public APIs boring and explicit', 'Apply the smallest change that improves correctness'). Several sections describe general software engineering principles Claude already knows rather than Android-specific actionable knowledge. | 2 / 3 |
Actionability | The skill is almost entirely abstract guidance with no concrete code examples, no specific architectural patterns shown, no executable Kotlin/Java snippets, and no actual implementation details. The 'examples' section provides gradle test commands but no actual code demonstrating clean architecture boundaries, use cases, or repository patterns. | 1 / 3 |
Workflow Clarity | The workflow steps are vague and abstract ('Map the request to the current Android stack', 'Inspect the existing implementation', 'Apply the smallest change'). There are no validation checkpoints with specific criteria, no feedback loops for error recovery, and no concrete sequencing of architectural refactoring steps. | 1 / 3 |
Progressive Disclosure | The content has reasonable section structure and mentions handoff skills (android-modularization, android-state-management) and official references. However, there are no references to detailed companion files for specific patterns like use case implementation, repository contracts, or ViewModel patterns that would benefit from deeper documentation. | 2 / 3 |
Total | 6 / 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.