dayapp-mobile-push
Dayapp Mobile Push
Overview
用 Day.app 接口发送手机告警推送。调用时先从当前任务上下文提炼 taskname 与 tasksummary,再直接触发 GET 请求。
Workflow
- 从当前任务上下文提炼参数:
taskname:不超过 6 个中文字符(英文场景建议不超过 12 个字母)tasksummary:不超过 25 个中文字符,或不超过 50 个英文字符
- 读取
config.json的deviceid、app_name与quiet_hours。 - 若
deviceid为空,立即提示用户并停止:- 配置位置:当前技能目录下的
./config.json - 配置方式:把
deviceid写入{"deviceid":"你的值"} - 获取方式:在 App Store 安装
Bark,打开 App 即可看到并复制deviceid
- 配置位置:当前技能目录下的
- 生成请求 URL:
- 标题前缀不是写死
Codex-,而是{应用名}-{taskname} group参数也不是写死值,而是与{应用名}保持一致app_name=auto时自动识别:Codex 环境用Codex-,Claude Code 环境用Claude-- 若当前时间在静音时段内:从 URL 参数里去掉
sound、level、volume - 若不在静音时段:保留
sound=alarm&level=critical&volume=5
- 标题前缀不是写死
- 发送 GET 请求。
Rules
- 只发送一次 GET 请求,不做重试风暴。
- 若
config.json缺少deviceid,先提示用户配置,再停止。 app_name默认auto;也可以手动写死,例如Codex、Claude。quiet_hours为可选;未配置时按非静音处理。- 发送前必须做长度约束;超长内容交给脚本自动截断。
- 不在消息中写入敏感信息(token、密码、cookie、内网地址等)。
Config
编辑同目录下 config.json:
{
"deviceid": "YOUR_DEVICE_ID",
"app_name": "auto",
"quiet_hours": {
"start": "23:00",
"end": "08:00"
}
}
说明:
app_nameauto:自动识别当前应用(Codex / Claude)- 其他值:手动指定前缀(会规范化,例如
Claude Code->Claude)
quiet_hours.start/quiet_hours.end使用HH:MM(24 小时制)- 支持跨天(如
23:00到08:00) - 在静音窗口内会自动移除
sound、level、volume
Command Reference
python3 scripts/send_dayapp_push.py --task-name "构建完成" --task-summary "CLI 构建与测试全部通过"
python3 scripts/send_dayapp_push.py --task-name "部署阻塞" --task-summary "生产发布被权限策略拦截" --dry-run
More from okwinds/miscellany
prd-to-engineering-spec
Transform PRD (Product Requirements Document) into actionable engineering specifications. Creates detailed technical specs that developers can implement step-by-step without ambiguity. Covers data modeling, API design, business logic, security architecture, deployment, and agent system design. Use when: converting product requirements to technical specs, validating PRD completeness, planning technical implementation, creating task breakdowns, or defining test specifications. Triggers: 'PRD to spec', 'convert requirements', 'technical spec from PRD', 'engineering doc from requirements', 'validate PRD'.
45headless-web-viewer
Render and view webpages using a headless browser (Playwright) to fetch JS-rendered HTML, extract visible text, and optionally save full-page screenshots. Use when a user asks to “无头浏览器打开/查看网页”, needs the rendered DOM instead of raw curl HTML, or wants a screenshot of a page.
33prd-writing-guide
Write complete, unambiguous PRDs that development teams can implement without guesswork. Includes requirement discovery framework, structured documentation methodology, completeness checklists, and common pitfall avoidance. Use when: writing new PRDs, reviewing PRD drafts, validating requirement completeness, preparing for engineering handoff. Triggers: 'write PRD', '写PRD', '产品需求文档', '需求文档', '需求规格', '需求评审', '完善需求', 'create requirements doc', 'product requirements', 'feature spec', 'requirements document'. Anti-triggers: 'technical design doc', 'architecture design', 'implementation plan', 'API design', '架构设计', '技术方案', '实现方案', '接口设计'.
23codebase-spec-extractor
Extract complete, replicable engineering specifications from existing codebases. Produces documentation detailed enough to fully replicate a project without seeing the original source code—even using a different tech stack. Use when: analyzing existing projects, documenting legacy systems, creating technical specs from code, preparing for system migration, or onboarding new teams. Triggers: 'extract spec from code', 'document codebase', 'analyze project architecture', 'create spec from existing system'.
16pptx-offline
PPTX 文档离线读写:解析/替换/重排/缩略图、OOXML 解包编辑回包,以及 html2pptx(HTML→PPT)工作流。适用于生成与维护演示文稿(依赖安装可能需要网络)。
14prd-to-uiux-rd-spec
从产品 PRD 产出“复刻级可落地”的 UI/UX 研发规格文档包(目录同构骨架、公共基座、组件/页面契约、覆盖映射、索引与 worklog)。适用于需要把 PRD 转成前端可复刻实现的规格文档、UI/UX 研发规格、界面契约与验收标准的场景;避免用于只要视觉灵感/纯 UI 赏析或直接写代码实现的请求。
14