Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计通过

android-workmanager-notificationsAndroid WorkManager 通知

Agent Skill

android-workmanager-notifications 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

259

周安装

11

GitHub Stars

5

下载量

91
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:android-workmanager-notifications(Android WorkManager 通知)
来源仓库:https://github.com/krutikjain/android-agent-skills
仓库路径:skills/android-workmanager-notifications
安装命令:
npx skills add https://github.com/krutikjain/android-agent-skills --skill android-workmanager-notifications
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/krutikjain/android-agent-skills --skill android-workmanager-notifications

简介

利用 WorkManager 调度可靠后台任务与通知提醒,适配 Android 执行限制并提供重试机制。

  • 适用于需要定时提醒、离线同步或延迟操作的场景,确保在系统资源受限下仍能交付。
  • 支持唯一工作请求、通知权限管理和多种 API 选型矩阵(WorkManager vs 前台服务)。
  • 需处理运行时权限申请与渠道配置;复杂场景应参考 patterns.md 和 scenarios.md 文档。
  • 安装前请评估电量与网络消耗,避免过度唤醒设备或触发用户隐私警告。

SKILL.md

Android WorkManager Notifications

When To Use

  • Use this skill when the request is about: android workmanager job, background reminder notification android, reliable retry workmanager.
  • Primary outcome: Schedule reliable background work, reminders, and notification delivery with WorkManager and Android execution limits.
  • Read references/patterns.md when you need the API-choice matrix for WorkManager vs foreground service vs alarms.
  • Read references/scenarios.md for unique-work, notification-permission, and reminder-delivery review paths.
  • Handoff skills when the scope expands:
  • android-permissions-activity-results
  • android-performance-observability

Workflow

  1. Choose the right execution API first: WorkManager for deferrable guaranteed work, foreground services for ongoing user-visible work, and exact alarms only when clock-time precision and policy requirements truly demand them.
  2. Make work idempotent and uniquely addressable with explicit names, input data contracts, backoff policy, and cancellation behavior.
  3. Apply constraints, expedited work, and retry semantics only where they match user value and platform limits.
  4. Build notification delivery as part of the contract: channels, importance, tap action, runtime permission handling, and graceful behavior when notifications are denied.
  5. Validate duplicate scheduling, reboot/process death, and degraded states before handing off performance or permission-specific follow-up work.

Guardrails

  • Keep background work idempotent and cancellation-aware.
  • Use unique work or unique periodic work when the feature represents one logical reminder or sync pipeline.
  • Treat expedited work as scarce and user-valuable; do not use it as a generic queue-jumping flag.
  • If a worker uses network constraints, ensure the app declares the permissions required for those constraints on modern Android versions.
  • Keep notification value intact even when the user declines POST_NOTIFICATIONS; the app still needs a visible recovery path.

Anti-Patterns

  • Blocking the main thread with disk or network calls.
  • Expecting WorkManager to deliver exact wall-clock timing like an alarm API.
  • Re-enqueueing duplicate reminder work instead of using unique work policies.
  • Failing to create channels or handle notification permission decline paths.
  • Hiding critical foreground or exact-alarm policy assumptions in comments instead of code and docs.

Review Focus

  • Is WorkManager the right API for this workload?
  • Are unique work policies, constraints, retry, and cancellation explicit?
  • Do reminder and notification paths still make sense if notifications are denied?
  • Are expedited, foreground, or exact-alarm behaviors justified and policy-safe?

Examples

Happy path

  • Scenario: Find background-work and notification hooks before proposing a scheduling change.
  • Command: rg -n "WorkManager|Worker|enqueueUnique|PeriodicWorkRequest|NotificationChannel|POST_NOTIFICATIONS" examples

Edge case

  • Scenario: Review exact-alarm, expedited, or network-constrained work for platform-sensitive behavior.
  • Command: rg -n "setExpedited|setRequiredNetworkType|AlarmManager|ForegroundInfo" examples

Failure recovery

  • Scenario: Disambiguate WorkManager requests from permission prompts and performance work.
  • Command: python3 scripts/eval_triggers.py --skill android-workmanager-notifications

Done Checklist

  • The chosen execution API matches the workload's timing and visibility requirements.
  • Unique work, retry, cancellation, and constraint behavior are explicit.
  • Notification channel and permission behavior are handled as part of the feature contract.
  • Process-death, reboot, and duplicate-scheduling behavior have been considered.

Official References

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

33.81%
按下载量换算31

Claude

33.65%
按下载量换算31

Cursor

18.19%
按下载量换算17

Gemini CLI

8.89%
按下载量换算8

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills