android-background-work
Implement WorkManager and background processing correctly on Android. Use when creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers.
67
82%
Does it follow best practices?
Impact
—
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 (Android background processing with WorkManager), lists specific concrete actions, and includes an explicit 'Use when' clause with natural trigger terms. It is concise, well-structured, and highly distinguishable from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: implementing WorkManager, creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, and setting up Hilt in workers. | 3 / 3 |
Completeness | Clearly answers both 'what' (implement WorkManager and background processing on Android) and 'when' (explicit 'Use when' clause listing creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'WorkManager', 'background processing', 'Android', 'Worker classes', 'scheduling tasks', 'Foreground Services', 'Hilt in workers'. These cover the main terms a developer would use when seeking help with Android background work. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Android WorkManager and background processing. The specific mention of WorkManager, Foreground Services, Worker classes, and Hilt integration makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%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 Android background work standards without over-explaining. Its main weakness is the lack of concrete, executable code examples inline — the actionability relies heavily on a referenced implementation file that isn't present in the bundle. Adding a minimal code snippet for the CoroutineWorker + Hilt setup would significantly improve it.
Suggestions
Add a minimal executable code example showing a @HiltWorker CoroutineWorker class with @AssistedInject constructor inline in the skill, so the skill is actionable even without the referenced file.
Include a brief sequenced workflow for setting up WorkManager with Hilt (e.g., 1. Create Worker class, 2. Configure HiltWorkerFactory, 3. Schedule work with constraints), with a validation step.
Ensure the referenced 'references/implementation.md' file exists in the bundle to support the progressive disclosure structure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. No unnecessary explanations of what WorkManager or Foreground Services are. Every line provides actionable guidance or constraints that Claude wouldn't inherently know about the project's standards. | 3 / 3 |
Actionability | Provides specific guidance (use CoroutineWorker, @HiltWorker, @AssistedInject) but lacks executable code examples. The reference to a Worker Template could fill this gap, but the bundle file is missing, so the skill itself doesn't provide copy-paste ready code. | 2 / 3 |
Workflow Clarity | The skill provides clear decision guidance (when to use WorkManager vs Foreground Services vs Coroutines) but lacks a sequenced workflow for setting up WorkManager with Hilt. Steps like configuring HiltWorkerFactory in WorkManager configuration are mentioned but not sequenced with validation checkpoints. | 2 / 3 |
Progressive Disclosure | References a Worker Template at 'references/implementation.md' which is good progressive disclosure structure, but the bundle file is not provided, making it impossible to verify the reference exists. The main content is well-organized with clear sections, but the single reference is the only navigation point. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
3df717f
- 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.