android-workmanager-notifications
Schedule reliable background work, reminders, and notification delivery with WorkManager and Android execution limits.
59
49%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/android-workmanager-notifications/SKILL.mdQuality
Discovery
57%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 identifies a clear Android-specific niche around WorkManager and background scheduling, which makes it distinctive. However, it lacks an explicit 'Use when...' clause and could benefit from more specific concrete actions and additional trigger terms that users commonly use when dealing with Android background work.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to schedule background tasks, handle Doze mode restrictions, or implement WorkManager in an Android app.'
Include more natural trigger term variations such as 'periodic tasks', 'deferred work', 'Doze mode', 'battery optimization', 'JobScheduler', 'AlarmManager migration', or 'foreground service'.
List more specific concrete actions, e.g., 'Create one-time and periodic work requests, chain dependent tasks, set constraints, handle retry policies, and manage foreground service notifications.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Android background work) and some actions (schedule background work, reminders, notification delivery), but doesn't list multiple concrete specific actions like 'create periodic tasks, chain work requests, handle constraints'. | 2 / 3 |
Completeness | Answers 'what' (schedule background work, reminders, notifications with WorkManager) but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric guidelines. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'WorkManager', 'background work', 'reminders', 'notification delivery', and 'Android execution limits', but misses common variations users might say such as 'periodic tasks', 'deferred work', 'Doze mode', 'battery optimization', 'foreground service', or 'AlarmManager'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'WorkManager', 'Android execution limits', and background scheduling creates a clear niche that is unlikely to conflict with other skills. This is distinctly an Android-specific background processing skill. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-organized with good progressive disclosure and reasonable conciseness, but critically lacks actionable code examples. For an Android development skill about WorkManager and notifications, the absence of any Kotlin/Java code for Worker implementation, WorkRequest building, notification channel creation, or permission handling makes it largely descriptive rather than instructive. The workflow provides a logical sequence but remains too abstract to guide concrete implementation.
Suggestions
Add executable Kotlin code examples for key operations: creating a Worker subclass, building a OneTimeWorkRequest/PeriodicWorkRequest with constraints and backoff, enqueuing unique work, and creating a NotificationChannel with permission check.
Replace the grep-based 'Examples' section with concrete implementation scenarios showing input (user requirement) → output (complete code snippet), such as scheduling a daily reminder notification with WorkManager.
Add a concrete validation step in the workflow, e.g., a code snippet or adb command to verify work is enqueued (`adb shell dumpsys jobscheduler`) and test notification delivery after process death.
Tighten the anti-patterns and guardrails sections by removing items Claude already knows (like 'don't block the main thread') and replacing with Android-version-specific gotchas that are genuinely non-obvious.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some verbose guidance that Claude would already know (e.g., 'Blocking the main thread with disk or network calls' as an anti-pattern). The workflow and guardrails sections describe concepts at a high level without being overly padded, but could be tightened. | 2 / 3 |
Actionability | The skill provides no executable code examples—no Kotlin/Java snippets for WorkManager setup, Worker implementation, notification channel creation, or enqueue calls. The 'Examples' section only shows grep/rg commands for searching codebases, not actual implementation guidance. The workflow is entirely abstract description rather than concrete, copy-paste-ready instructions. | 1 / 3 |
Workflow Clarity | The workflow has a clear 5-step sequence and the done checklist provides validation points. However, the steps are abstract ('Choose the right execution API', 'Apply constraints') without concrete validation checkpoints or feedback loops for error recovery. Step 5 mentions validation but doesn't specify how to actually validate duplicate scheduling or reboot behavior. | 2 / 3 |
Progressive Disclosure | The skill is well-structured with clear sections and references to external files (references/patterns.md, references/scenarios.md) that are one level deep and clearly signaled with context about when to read them. Handoff skills are also clearly identified. | 3 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 Passed | |
- Repository
- krutikJain/android-agent-skills
- Commit
c5bf673
- 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.