CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

70

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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.

An efficiently written standards body: lean directives, concrete API-level guidance, and a well-signaled one-level-deep reference holding the executable template. Its main gaps are the absence of any inline enqueue/scheduling snippet and no explicit sequencing for tasks that do involve multiple steps.

Suggestions

Add a minimal inline enqueue snippet (e.g., a 3-line OneTimeWorkRequestBuilder with Constraints) so the most common action is executable directly from SKILL.md without opening the reference.

Drop or justify the "Priority: P1 (HIGH)" heading, which carries no actionable meaning for the model executing the skill.

Give the references/implementation.md link a one-phrase description of its contents (e.g., full CoroutineWorker + enqueue template) so readers know what depth it provides before opening it.

DimensionReasoningScore

Conciseness

The body is lean directive fragments ("CoroutineWorker: Use for all background tasks"; "No IntentService: Deprecated") that assume Claude's Android knowledge and explain nothing Claude already knows. Only the "Priority: P1 (HIGH)" heading is arguably trimmable, which is too minor to drop it from anchor 5.

5 / 5

Actionability

Names exact APIs (@HiltWorker, @AssistedInject, HiltWorkerFactory, Constraints) and gives concrete rules, but the body itself contains no executable code or commands — the runnable Kotlin template lives in references/implementation.md. Concrete and mostly executable guidance with a minor gap; not 3 because nothing is vague or pseudocode.

4 / 5

Workflow Clarity

The WorkManager-vs-Foreground-Service decision rule is unambiguous ("Only When Necessary... Playback, Calls, Active Navigation. Otherwise use WorkManager") and anti-patterns are explicit, but the body is a standards list rather than a sequenced workflow — no enqueue/retry steps or checkpoints in-body. Clear guidance with minor gaps, matching anchor 4.

4 / 5

Progressive Disclosure

The body is a concise overview with a clearly signaled References section, and the single reference ([Worker Template](references/implementation.md)) exists, is one level deep, and contains a complete copy-paste Kotlin CoroutineWorker template. Content is appropriately split with easy navigation.

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 description: it pairs a clear capability statement with an explicit, trigger-phrase-rich "Use when" clause, and even adds boundary guidance to avoid conflicting with a sibling notifications skill. The only room for improvement is enumerating a couple more natural trigger variations.

DimensionReasoningScore

Specificity

Enumerates several concrete actions ("creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers") with minor coverage gaps. Not a 5 because the core capability statement ("Implement WorkManager and background processing correctly") is broad rather than a comprehensive enumerated list.

4 / 5

Completeness

Explicitly answers both: what ("Implement WorkManager and background processing correctly on Android") and when ("Use when creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers") with concrete trigger phrases. Directly matches the anchor-5 example pattern.

5 / 5

Trigger Term Quality

Good coverage of natural terms users would say: "WorkManager", "Worker classes", "scheduling tasks", "Hilt", "Foreground Services". A few natural variations are missing (e.g., "background job", "background service", "AlarmManager"), keeping it below the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

Clear Android background-work niche with distinct triggers, and the clause "defer FCM and notification delivery to android-notifications" explicitly disambiguates against the closest related skill. Minimal conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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

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.