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.
87
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 Android background processing with WorkManager. It uses proper third-person voice, includes an explicit 'Use when' clause with specific trigger scenarios, and contains natural keywords that Android developers would use. The description is concise yet comprehensive enough to distinguish it from other Android-related 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', 'Worker classes', 'scheduling tasks', 'Foreground Services', 'Hilt', 'Android' — these cover the main terms a developer would use when seeking help with Android background work. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche targeting Android WorkManager and background processing with distinct triggers like 'WorkManager', 'Foreground Services', and 'Hilt in workers' that are unlikely to conflict with other 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 Android background work standards without over-explaining. Its main weakness is the lack of inline executable code examples—the actionable implementation details are entirely deferred to a reference file. Adding a minimal code snippet for the most common case (CoroutineWorker with Hilt) would significantly improve actionability.
Suggestions
Add a minimal inline code example showing a CoroutineWorker with @HiltWorker and @AssistedInject constructor to make the skill immediately actionable without needing to consult the reference file.
Include a brief step-by-step workflow for setting up a new worker (e.g., 1. Create Worker class, 2. Configure HiltWorkerFactory, 3. Schedule with WorkManager constraints) to improve workflow clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. No unnecessary explanations of what WorkManager or Foreground Services are. Every bullet point adds actionable, non-obvious guidance that Claude wouldn't inherently know about project-specific standards. | 3 / 3 |
Actionability | Provides specific guidance (use CoroutineWorker, @HiltWorker, @AssistedInject, HiltWorkerFactory) but lacks executable code examples. The concrete implementation details are deferred to a reference file rather than shown inline with at least a minimal example. | 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 a worker. There's no step-by-step process for creating and registering a worker with validation checkpoints. | 2 / 3 |
Progressive Disclosure | Appropriately structured with a concise overview in the main file and a single, clearly signaled reference to an implementation template. One level deep, well-organized sections, and easy to navigate. | 3 / 3 |
Total | 10 / 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 | |
4c72e76
Table of Contents
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.