android-development

Android development guidelines for Kotlin with clean architecture, MVI pattern, Material Design, and best practices for building robust mobile applications

Quality

27%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./android-development/SKILL.md

Quality

Content

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 as a high-level Android development style guide that mostly restates well-known best practices Claude already understands. It lacks executable code examples, concrete commands, and actionable workflows, making it difficult for Claude to translate into specific implementation steps. The content would benefit significantly from concrete code snippets demonstrating the MVI pattern, repository setup, and navigation configuration, as well as clear step-by-step workflows.

Suggestions

Add concrete, executable code examples for key patterns (MVI state management, repository implementation, ViewModel setup, navigation graph configuration) instead of abstract descriptions.

Remove or drastically shorten sections covering general knowledge Claude already has (SOLID principles, basic Kotlin naming, 'avoid magic numbers') and focus on project-specific conventions and non-obvious decisions.

Add a step-by-step project setup workflow with specific commands (e.g., Gradle configuration, Hilt setup, module creation) and validation checkpoints.

Split detailed sections (testing strategies, authentication flow, UI patterns) into separate reference files and make SKILL.md a concise overview with clear links to those files.

Dimension	Reasoning	Score
Conciseness	The content is reasonably organized but includes many guidelines Claude already knows (SOLID principles, basic Kotlin naming conventions, 'avoid magic numbers', 'prefer composition over inheritance'). Several sections read like a general Android best practices textbook rather than adding novel, project-specific constraints.	2 / 3
Actionability	The skill is almost entirely abstract guidance with no executable code examples, no concrete commands, and no copy-paste-ready snippets. Statements like 'Deploy MVI pattern for state and event management' and 'Use repository pattern for data persistence' describe rather than instruct. The project structure diagram is the only concrete artifact.	1 / 3
Workflow Clarity	There are no clear multi-step workflows with validation checkpoints. The authentication flow lists screens but provides no implementation sequence or verification steps. There's no guidance on how to set up a project, no build/run commands, and no feedback loops for error recovery.	1 / 3
Progressive Disclosure	The content is organized into logical sections with clear headers, which provides some structure. However, it's a monolithic document with no references to supporting files, and several sections (like testing, authentication flow, UI development) could benefit from being split into separate detailed guides with the SKILL.md serving as an overview.	2 / 3
	Total	6 / 12 Passed

Description

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 technology stack and architectural patterns but reads more like a topic label than an actionable skill description. It lacks concrete actions (what the skill actually does) and has no explicit trigger guidance for when Claude should select it. The specificity of mentioning MVI and clean architecture helps with distinctiveness but the overall description needs significant improvement.

Suggestions

Add a 'Use when...' clause specifying triggers, e.g., 'Use when the user asks about Android app development, Kotlin mobile projects, MVI architecture, or building Android UIs with Material Design.'

Replace the abstract 'guidelines' framing with concrete actions, e.g., 'Scaffolds Android project structure using clean architecture layers, implements MVI state management, creates Material Design UI components, and reviews Kotlin code for Android best practices.'

Include additional natural trigger terms users might say, such as 'Jetpack Compose', 'Android Studio', 'app', '.kt files', 'ViewModel', or 'Android UI'.

Dimension	Reasoning	Score
Specificity	Names the domain (Android development) and mentions specific patterns/technologies (Kotlin, clean architecture, MVI, Material Design), but describes guidelines rather than concrete actions. No specific verbs like 'generates', 'scaffolds', or 'reviews' are present.	2 / 3
Completeness	Partially answers 'what' (Android development guidelines) but has no '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' is also weak (guidelines is vague), so this scores a 1.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Android', 'Kotlin', 'clean architecture', 'MVI', 'Material Design', and 'mobile applications' that users might naturally mention. However, it misses common variations like 'app development', 'Jetpack Compose', 'ViewModel', 'MVVM', or file extensions like '.kt'.	2 / 3
Distinctiveness Conflict Risk	The combination of Android + Kotlin + MVI + clean architecture is fairly specific and unlikely to conflict with generic coding skills. However, it could overlap with general Kotlin skills, general mobile development skills, or Android skills using different patterns.	2 / 3
	Total	7 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: mindrally/skills
Path: android-development/SKILL.md
Commit: 05a7130

Reviewed: about 13 hours ago

Table of Contents

Discovery Implementation Validation

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.