android-clean-architecture

Clean Architecture patterns for Android and Kotlin Multiplatform projects — module structure, dependency rules, UseCases, Repositories, and data layer patterns. Use when structuring modules, layers, or data flow in an Android or KMP project.

Quality

85%

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

The canonical home for this skill is tdg-personal/android-clean-architecture

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with comprehensive executable code examples and a clear layer-by-layer structure. Its main weakness is progressive disclosure: substantial inlined content for multiple persistence/DI frameworks could be split into reference files.

Suggestions

Move the per-framework deep dives (Room, SQLDelight, Ktor, Koin, Hilt) into separate files under references/ and link to them from SKILL.md to reduce inlined bulk.

Add a short 'When to Activate' pointer or validation cue at the top so Claude confirms the layering context before applying patterns.

Convert the dependency rules into a quick checklist or verification step so module-boundary violations are caught explicitly.

Dimension	Reasoning	Score
Conciseness	The body is example-driven and assumes Claude's knowledge of Kotlin/Android, with only minor restatement of the description and light padding; efficient but not maximally lean.	4 / 5
Actionability	Provides copy-paste-ready, executable Kotlin and SQL examples across UseCases, repositories, mappers, Room, SQLDelight, Ktor, Koin, and Hilt covering the common cases.	5 / 5
Workflow Clarity	Content is logically sequenced by layer (module structure → domain → data → DI → errors → Gradle) with dependency rules and anti-patterns; no explicit validation checkpoints, but the skill is a patterns reference rather than a destructive/batch workflow.	4 / 5
Progressive Disclosure	No bundle files exist; the single SKILL.md inlines extensive Room/SQLDelight/Ktor/Koin/Hilt code that could plausibly live in separate reference files, and the References section points to other skills rather than bundle files.	3 / 5
	Total	16 / 20 Passed

Description

92%Weight 40%Scale 1-5

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 concrete, well-scoped, and includes an explicit 'Use when' trigger clause with natural language. It is among the stronger reference examples for both completeness and specificity.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'module structure, dependency rules, UseCases, Repositories, and data layer patterns' — giving comprehensive coverage of the skill's scope.	5 / 5
Completeness	Explicitly answers both 'what' (clean architecture patterns for Android/KMP) and 'when' via a concrete 'Use when structuring modules, layers, or data flow in an Android or KMP project' clause.	5 / 5
Trigger Term Quality	Includes natural phrases like 'structuring modules, layers, or data flow' and 'Android or KMP project'; strong coverage but missing some synonyms/file extensions that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	A clear niche — Android/KMP clean architecture with layer/module triggers — that is unlikely to fire for unrelated skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/android-clean-architecture/SKILL.md
Commit: 06c5e11

Reviewed: 3 days 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.