CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

69

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A compact, well-organized standards skill that delegates code to a single real reference, but the body itself lacks executable examples and any sequenced workflow with validation checkpoints. Actionability and workflow clarity are the main weak spots.

Suggestions

Inline a minimal executable Kotlin snippet (a CoroutineWorker skeleton or enqueue example) directly in SKILL.md so guidance is copy-paste ready without opening the reference.

Add a short sequenced workflow for standing up a worker — e.g. define Worker -> configure constraints -> enqueue -> verify via WorkManager inspector/logs — with an explicit validation checkpoint.

Tighten vague directives like 'Constraints: explicit (Require Network, Charging)' into concrete Constraints.Builder usage so the body is actionable on its own.

DimensionReasoningScore

Conciseness

Lean directive bullets with no padded explanation of concepts Claude already knows; every line earns its place ('Use for all background tasks', 'No IntentService: Deprecated').

3 / 3

Actionability

Names concrete annotations and classes ('@HiltWorker', '@AssistedInject', 'HiltWorkerFactory') but the SKILL.md body contains no executable code — it is deferred to the reference — and some guidance like 'Constraints: explicit (Require Network, Charging)' is directional rather than copy-paste ready.

2 / 3

Workflow Clarity

Content is organized as implementation guidelines and anti-patterns rather than a sequenced multi-step process, and there are no validation or verification checkpoints for the worker setup workflow.

2 / 3

Progressive Disclosure

Short, well-sectioned overview with a single clearly signaled, one-level-deep reference ([Worker Template](references/implementation.md)) that resolves to a real file.

3 / 3

Total

10

/

12

Passed

Description

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.

A concise, well-targeted description that clearly states capabilities and explicit use-when triggers with strong, natural trigger terms. No meaningful weaknesses for a description of this kind.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services... setting up Hilt in workers' — rather than vague language.

3 / 3

Completeness

Explicitly states what ('Implement WorkManager and background processing correctly on Android') and when via an explicit 'Use when...' clause with concrete triggers.

3 / 3

Trigger Term Quality

Covers natural terms an Android developer would say — 'WorkManager', 'Worker classes', 'Foreground Services', 'Hilt' — with good breadth of the domain's vocabulary.

3 / 3

Distinctiveness Conflict Risk

Narrow Android background-work niche with distinct technical triggers makes it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.

Validation14 / 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
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.