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; defer FCM and notification delivery to android-notifications.

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.

The body is an efficient, well-structured standards overview that defers code to a real reference file with clean one-level-deep navigation. Actionability and workflow_clarity sit at 4 because the body is directive-only (no inline code) and is a decision guide rather than a sequenced procedure.

Suggestions

Inline a minimal CoroutineWorker skeleton so the body is actionable without opening the reference.

Add a brief decision sequence (e.g., 1. Is the task user-visible? 2. If no, WorkManager; 3. If yes, Foreground Service) to strengthen workflow clarity.

Dimension	Reasoning	Score
Conciseness	Lean bullet-point standards with no padding and no explanation of concepts Claude already knows; every line earns its place and detailed code is offloaded to the reference.	5 / 5
Actionability	Names specific executable APIs (@HiltWorker, @AssistedInject, HiltWorkerFactory, CoroutineWorker) and points to a complete code template, but the body itself has no inline executable code and 'Use Coroutines in ViewModel scope' is high-level.	4 / 5
Workflow Clarity	As a decision/standards guide it clearly delineates WorkManager vs Foreground Services use cases and anti-patterns rather than a sequenced procedure, with no destructive/batch operations requiring validation checkpoints.	4 / 5
Progressive Disclosure	Concise overview body with a single well-signaled one-level-deep reference (references/implementation.md, verified to exist) holding the full code template, making navigation easy.	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.

The description is well-crafted: third-person voice, explicit 'Use when' triggers, concrete capabilities, and clear boundary guidance against a sibling notifications skill. Minor keyword synonyms and a few uncovered sub-topics keep specificity and trigger_term_quality at 4 rather than 5.

Suggestions

Add natural synonyms like 'Coroutines' or 'background jobs' to broaden trigger_term_quality coverage.

Mention constraints/backoff or periodic vs one-time scheduling to push specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions ('creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, setting up Hilt in workers') but leaves minor gaps like constraints, backoff/retry, and periodic vs one-time distinction.	4 / 5
Completeness	Explicitly answers both what ('Implement WorkManager and background processing correctly on Android') and when ('Use when creating Worker classes, scheduling tasks...') with concrete trigger phrases and boundary guidance.	5 / 5
Trigger Term Quality	Strong natural keyword coverage ('WorkManager', 'Worker classes', 'Foreground Services', 'Hilt') that Android developers actually say, but misses synonyms like 'Coroutines' or 'JobScheduler'.	4 / 5
Distinctiveness Conflict Risk	Clear Android background-work niche with explicit boundary deferral ('defer FCM and notification delivery to android-notifications') minimizing conflict with sibling skills.	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-background-work/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.