android-architecture

Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow implementation to their specific skills.

Quality

86%

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

Quality

Content

86%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.

A concise, well-organized standards body that uses progressive disclosure effectively, deferring code examples to real reference files while keeping actionable architectural guidance inline. The main gap is the absence of an explicit validation feedback loop in the verification section.

Suggestions

Add a brief error-recovery note to the Verification section (e.g., 'If ./gradlew build fails, resolve Android imports in the Domain layer before re-running') to turn the checklist into a validate→fix→retry loop.

Include one minimal inline Gradle snippet (e.g., a settings.gradle.kts include block) so the most common setup step is copy-paste ready without opening references.

Consider adding a one-line 'when' framing at the top of the body so it reads as a standalone standard, not only as a triggered skill.

Dimension	Reasoning	Score
Conciseness	Lean bullet-point body that assumes Claude's Android competence ('Domain: Pure Kotlin (No Android deps). Contains UseCases and Models.') with no padding or explanation of concepts Claude already knows.	5 / 5
Actionability	Concrete specifics throughout (module paths ':feature:home', APIs 'setContent', 'collectAsStateWithLifecycle', '@Stable') with executable verification ('./gradlew build'), though the bulk of copy-paste code is deferred to references rather than inline.	4 / 5
Workflow Clarity	Clear sequenced sections (Layer → Modularize → UDF → Verify Compose) with an explicit verification checklist ('./gradlew build succeeds', 'zero Android framework imports'), but no error-recovery feedback loop for failed validation.	4 / 5
Progressive Disclosure	Concise overview in SKILL.md with well-signaled one-level-deep references ('See [structure & examples](references/implementation.md)') and a clean References section listing both real bundle files; details are appropriately split out.	5 / 5
	Total	18 / 20 Passed

Description

87%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.

A strong, well-structured description that clearly states capabilities and explicit trigger conditions while actively managing boundaries with related skills. Its only weakness is that the named actions are architectural-level rather than granularly concrete.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Clean Architecture layering, modularization, and Unidirectional Data Flow') but they sit at an architectural abstraction level rather than the granularly concrete actions of a 5, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what ('Apply Clean Architecture layering, modularization, and Unidirectional Data Flow') and when ('Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural keyword coverage ('project structure', 'layers', 'feature/core modules', 'UDF patterns') that Android developers would actually say, though a few natural synonyms are absent.	4 / 5
Distinctiveness Conflict Risk	Clear Android-architecture niche with distinct triggers, and the explicit deferral ('defer Compose state and ViewModel/StateFlow implementation to their specific skills') actively minimizes conflict with adjacent skills.	5 / 5
	Total	18 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: HoangNguyen0403/agent-skills-standard
Path: skills/android/android-architecture/SKILL.md
Commit: 405cdd5

Reviewed: 4 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.