session-nudgelisted
Install: claude install-skill zydo/skills
# Session nudge
One helper does everything; run it with the Python 3.9+ on PATH:
```sh
python3 <this skill's directory>/scripts/nudge.py <action> [options]
```
## Map the request to an action
| User says | Run |
|---|---|
| `on`, `enable`, "turn nudges on here" | `on` |
| `off`, `disable`, "stop nudging this session" | `off` |
| nothing, `status`, "is the nudge on?" | `status` |
| a pace: "nudge every 20 minutes", "每半小时", "hourly", "every 1.5h" | `on --every N` |
| first nudge at a future time, then on the cadence from it ("resume at 7:30am and nudge every 305 minutes"; 7:30 is the "0th" nudge) | `on --every N --anchor-at 07:30` |
| "nudge once at 2:01 AM local time" | `once --at 02:01` |
| a different terminal (e.g. a Codex or Grok Build window) | add `--pid N` |
| "test the nudge", or first use on a machine | `test` |
| change the default pace for new opt-ins | `install --interval N` |
| remove the background job | `uninstall` |
A pace turns the nudge on (or changes the pace of an already-enabled session).
Convert it to whole minutes yourself: "half an hour" -> 30, "every 2 hours"
-> 120, "1.5h" -> 90; anything under one minute becomes 1. With no pace,
`on` keeps the session's existing pace, else the default (61). The pace is per
session: other sessions keep theirs.
`on --anchor-at HH:MM` backdates the pace's last-nudge stamp so the first
delivery fires exactly at the anchor minute and later deliveries keep the
every-N cadence measured from it ("first nudge at 7:30, t