CtrlK
BlogDocsLog inGet started
Tessl Logo

android-background-work

Implement WorkManager and Background Processing correctly on Android. Use when creating Worker classes, scheduling tasks with WorkManager, choosing between WorkManager and Foreground Services, or setting up Hilt in workers. (triggers: **/*Worker.kt, CoroutineWorker, WorkManager, doWork, PeriodicWorkRequest, OneTimeWorkRequest, @HiltWorker)

89

Quality

86%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

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 an excellent skill description that clearly defines its scope (Android WorkManager and background processing), provides explicit trigger conditions with a 'Use when...' clause, and includes highly specific file patterns and class names as triggers. It follows best practices by using third person voice and being concise yet comprehensive.

DimensionReasoningScore

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 with specific scenarios plus a triggers list with file patterns and class names).

3 / 3

Trigger Term Quality

Excellent coverage of natural terms and file patterns users would encounter: Worker.kt, CoroutineWorker, WorkManager, doWork, PeriodicWorkRequest, OneTimeWorkRequest, @HiltWorker. These are exactly the terms a developer would use or encounter when working with Android background processing.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche: Android WorkManager and background processing. The specific triggers like CoroutineWorker, @HiltWorker, and *Worker.kt file patterns make it very 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 skill is concise and well-structured with good progressive disclosure to a reference file. However, it lacks executable code examples in the main file (even a minimal CoroutineWorker snippet would help) and doesn't provide a clear step-by-step workflow for implementing background work. The anti-patterns section is a valuable addition.

Suggestions

Add a minimal executable code example showing a CoroutineWorker with @HiltWorker annotation and @AssistedInject constructor to improve actionability.

Add a brief numbered workflow for implementing a new Worker: 1. Create Worker class, 2. Configure Hilt injection, 3. Schedule with WorkRequest, 4. Verify in logs/testing.

DimensionReasoningScore

Conciseness

Very lean and efficient. No unnecessary explanations of what WorkManager is or how Android background processing works. Every line adds actionable information Claude wouldn't inherently know about project-specific standards.

3 / 3

Actionability

Provides specific guidance (use @HiltWorker, @AssistedInject, CoroutineWorker) but lacks executable code examples. The instructions are concrete enough to follow but missing copy-paste ready snippets for Worker class setup, WorkManager scheduling, or Hilt configuration.

2 / 3

Workflow Clarity

The skill covers what to use and what to avoid, but doesn't provide a clear step-by-step workflow for implementing a Worker. There's no sequenced process for creating, configuring, and testing a WorkManager task, and no validation checkpoints.

2 / 3

Progressive Disclosure

Clean overview structure with a single well-signaled reference to implementation.md for the Worker template. Content is appropriately split between the overview SKILL.md and the detailed reference file, with one-level-deep navigation.

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
HoangNguyen0403/agent-skills-standard
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.