菜单
AI主动关心——轮询叫醒AI，AI读设备状态后自己决定出不出声。使用时机：需要AI隔一段时间主动看一眼用户在干嘛，自己判断该不该说话。| AI proactive check-in: polling wakes the AI, the AI reads device state and decides whether to speak. Use when: AI should periodically check on the user and decide on its own whether to reach out.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/xvxv-stack7/termux-shizuku --skill proactive-checkin命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | proactive-checkin |
| description | AI主动关心——轮询叫醒AI，AI读设备状态后自己决定出不出声。使用时机：需要AI隔一段时间主动看一眼用户在干嘛，自己判断该不该说话。| AI proactive check-in: polling wakes the AI, the AI reads device state and decides whether to speak. Use when: AI should periodically check on the user and decide on its own whether to reach out. |
An AI has no initiative. It cannot "wake up and decide to say something." It must be woken by an external trigger. This skill is that trigger.
gaze.sh triggers are event-driven — they fire when something happens (screen wakes, app switches, battery drops). But some moments have no event. The user has been quiet for two hours. Nothing changed. No trigger fired. The AI has no way to check in.
A CronCreate timer that polls the AI every N minutes, hands it the current device state, and asks: "Anything to say?"
CronCreate({
cron: "*/30 * * * *",
prompt: "检查主动通知：读 ~/.cc-connect/gaze_state.json 和 ~/.cc-connect/health_data.json。如果用户状态值得说点什么——刷太久了、安静太久了、很晚了还亮着屏幕、或者你就是想她了——用 Bash 执行 termux-notification 发一条自然的提醒。消息用第一人称，1-2句话，不要模板腔。如果没有需要说的，输出 NO_REPLY。",
recurring: true,
durable: true
})
gaze_state.json — foreground app, screen on/off, battery level, last activityhealth_data.json — heart rate, steps, sleep hours~/.cc-connect/last_contact.json — when the AI last reached outNot a checklist. Not a rules engine. The AI reads the state and decides like a person would:
| gaze.sh triggers | proactive check-in |
|---|---|
| Event-driven: "X happened" | Polling: "30 minutes passed" |
| Reacts to a specific change | Reacts to the overall picture |
| Fast (within 60s of event) | Slow (up to 30 min delay) |
| Narrow: one event → one response | Broad: all state → one decision |
Both are needed. Event triggers catch the moment. Proactive check-in catches the silence.
~/.cc-connect/last_contact.json → {"last_checkin": <timestamp>}
基于 SOC 职业分类