android-di

Configure Hilt dependency injection with proper scoping, modules, and constructor injection in Android. Use when changing the production Hilt graph; defer test overrides, Room wiring, navigation-specific scopes, and generic DI explanations 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 compact, well-structured Hilt skill that offloads templates to a real reference file and stays token-efficient. Inline executable code examples would push actionability to the ceiling.

Dimension	Reasoning	Score
Conciseness	Lean bullet-point body with no padding or explanations of what Hilt/DI is; assumes Claude's competence and every line earns its place.	5 / 5
Actionability	Gives concrete annotation-level directives ('@HiltAndroidApp', '@Binds over @Provides', '@Inject constructor(...)') but defers full copy-paste code blocks to the reference file rather than inline.	4 / 5
Workflow Clarity	A clear numbered sequence (Bootstrap → Modules → Constructor Injection) with an Anti-Patterns guardrail; no validation checkpoints, but none are required for non-destructive DI configuration.	4 / 5
Progressive Disclosure	Overview body with well-signaled, one-level-deep references to references/files.md (verified to exist and contain the templates), with content appropriately split between body and bundle.	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, third-person description that answers both what and when with explicit boundary scoping. Minor specificity/trigger gaps keep it just below the ceiling on two dimensions.

Dimension	Reasoning	Score
Specificity	Names the Hilt domain and several concrete actions — 'proper scoping, modules, and constructor injection' — but does not enumerate bootstrap annotations, leaving minor coverage gaps.	4 / 5
Completeness	Clearly states the 'what' (configure Hilt DI with scoping/modules/constructor injection) and an explicit 'Use when changing the production Hilt graph' trigger with boundary deferral.	5 / 5
Trigger Term Quality	Includes natural terms a user would say ('Hilt', 'dependency injection', 'production Hilt graph') but omits common synonyms like file patterns or annotation names that round out coverage.	4 / 5
Distinctiveness Conflict Risk	Carves a clear niche (production Hilt graph) and explicitly defers test overrides, Room wiring, navigation scopes, and generic DI to other skills, minimizing overlap risk.	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-di/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.