android-architecture

Expert guidance on setting up and maintaining a modern Android application architecture using Clean Architecture and Hilt. Use this when asked about project structure, module setup, or dependency injection.

Quality

81%

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

72%Weight 40%Scale 1-3

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

A tight, concrete architecture reference with specific annotations, module paths, and hard dependency rules, well-organized for a sub-50-line skill. It loses points only for restating a few well-known concepts and lacking explicit validation checkpoints in its workflow.

Suggestions

Trim the per-layer 'Responsibility' lines that restate well-known UI/Domain/Data concepts to improve token efficiency.

Add an explicit validation checkpoint (e.g., 'verify no android.* imports in :core:domain before proceeding') to turn the closing checklist into a feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and bullet-structured, but the per-layer 'Responsibility' lines (e.g., 'Displaying data and handling user interactions') restate concepts Claude already knows about UI/Domain/Data layers, so it could be tightened further rather than fully earning the level-3 'every token earns its place' anchor.	2 / 3
Actionability	Despite being an instruction-only skill, the guidance is highly concrete and copy-paste ready: specific annotations (@HiltAndroidApp, @HiltViewModel), exact module paths (:core:data, :feature:[name]), and hard rules ('Must NOT contain any android.* imports'), matching the actionable anchor.	3 / 3
Workflow Clarity	Sections are logically sequenced (layers -> DI -> modularization -> checklist) and the closing checklist provides some validation, but there are no explicit validation checkpoints or feedback loops within the process, fitting the 'steps present but checkpoints missing or implicit' anchor rather than level 3.	2 / 3
Progressive Disclosure	The skill is under 50 lines with no bundle files and is organized into clearly labeled sections (layers, DI, modularization, checklist), which per the rubric's simple-skill guidance earns a 3 on well-organized structure without external references.	3 / 3
	Total	10 / 12 Passed

Description

90%Weight 40%Scale 1-3

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 well-formed third-person description that explicitly covers both capability and trigger conditions with natural, distinctive terms. Its only weakness is that the action verbs ('setting up and maintaining') are generic rather than a concrete enumerated action list.

Dimension	Reasoning	Score
Specificity	The description names the domain ('modern Android application architecture using Clean Architecture and Hilt') and two actions ('setting up and maintaining'), but does not enumerate multiple concrete actions, matching the 'names domain and some actions, but not comprehensive' anchor rather than the level-3 list of specific actions.	2 / 3
Completeness	It clearly states what the skill does ('Expert guidance on setting up and maintaining... architecture') and provides an explicit 'Use this when...' trigger clause, satisfying both the what and the when at the top level.	3 / 3
Trigger Term Quality	The explicit 'Use this when asked about project structure, module setup, or dependency injection' covers natural phrases a user would actually say, aligning with the 'good coverage of natural terms' anchor; it is not merely technical jargon.	3 / 3
Distinctiveness Conflict Risk	The narrow scope ('modern Android application architecture using Clean Architecture and Hilt') with specific triggers (project structure, module setup, dependency injection) gives it a clear niche unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: new-silvermoon/awesome-android-agent-skills
Path: .github/skills/architecture/android-architecture/SKILL.md
Commit: 82900ea

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