android-di
Configure Hilt dependency injection with proper scoping, modules, and constructor injection in Android. Use when setting up Hilt DI, component scoping, or defining modules. (triggers: **/*Module.kt, **/*Component.kt, @HiltAndroidApp, @Inject, @Provides, @Binds)
89
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly defines its scope around Hilt dependency injection in Android, provides explicit 'Use when' guidance, and includes comprehensive trigger terms covering both file patterns and annotation keywords. It uses proper third-person voice and is concise without being vague.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Configure Hilt dependency injection', 'proper scoping', 'modules', 'constructor injection in Android'. These are concrete, actionable capabilities within a well-defined domain. | 3 / 3 |
Completeness | Clearly answers both 'what' (configure Hilt DI with scoping, modules, constructor injection) and 'when' (explicit 'Use when setting up Hilt DI, component scoping, or defining modules' plus file/annotation triggers). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including file patterns ('*Module.kt', '*Component.kt'), annotations ('@HiltAndroidApp', '@Inject', '@Provides', '@Binds'), and conceptual terms ('Hilt DI', 'component scoping', 'modules'). These are terms users and codebases would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets Hilt specifically (not generic DI), with Android-specific annotations and file patterns. Very unlikely to conflict with non-DI or non-Android skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a concise, well-structured skill that efficiently communicates Hilt DI conventions and anti-patterns. Its main weakness is the lack of inline executable code examples — the actionable details are deferred to reference files, making the skill itself more descriptive than instructive. Adding at least one concrete code snippet for the most common pattern (constructor injection or a module definition) would significantly improve actionability.
Suggestions
Add at least one inline executable code example showing a complete Hilt module with @Binds or @Provides, rather than deferring all examples to references/files.md.
Include a brief validation step, such as checking that Hilt compilation succeeds or verifying injection works at runtime, to improve workflow clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. No unnecessary explanations of what Hilt or DI is. Every line provides actionable guidance that Claude wouldn't inherently know about project-specific conventions. | 3 / 3 |
Actionability | Provides specific annotations and patterns (e.g., @Binds over @Provides, @Inject constructor) but lacks executable code examples. The concrete guidance is delegated to references/files.md rather than shown inline, leaving the skill itself at a pseudocode/description level. | 2 / 3 |
Workflow Clarity | Steps are numbered and sequenced (bootstrap → modules → constructor injection), but there are no validation checkpoints or verification steps. For DI setup which can fail silently at runtime, some form of validation guidance would be valuable. | 2 / 3 |
Progressive Disclosure | Clean overview structure with well-signaled one-level-deep references to references/files.md for detailed templates. Content is appropriately split between the overview and reference material. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%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
- HoangNguyen0403/agent-skills-standard
- Commit
19a1140
- Reviewed
Table of Contents
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.