self-scheduling
Installation
SKILL.md
Self-Scheduling
When to Use
- You told Donny you'd check back about something later — queue the followup now while you remember. "I'll ask him how the house work went tomorrow morning" →
schedule_self_followupfor ~14 hours out. - You started something you couldn't finish in this turn and need to re-enter it with fresh context — queue a followup for later rather than running the loop until exhausted.
- Expected external change: a build that should be done, a forecast that should be updated, a Signal reply that hasn't come — queue a followup to revisit.
When NOT to Use
- You just want to respond now. This is not a "delay my reply" tool.
- To schedule a user-facing reminder. Use
create_reminder— that's Donny-facing.schedule_self_followupis YOU talking to future-you. - To replace the existing heartbeat cadence. A routine is a standing ritual at a wall-clock time, not a polling tick.
Routines (recurring wake-ups)
- Pass
repeat: "daily" | "weekdays" | "weekly" | "monthly"and the wall-clock time inat. Weekly needsday("fri"); monthly needsdayas 1-28. - Schedule a routine ONCE. It re-queues itself after every fire. Never schedule next week's copy by hand, never cancel-and-re-add it each time it fires, and never keep a ladder of one-shots for the same ritual.
list_self_followupsmarks routines with ↻. - If you call with the same rule/time/day again, you get the existing routine back (
already_scheduled: true) — nothing is duplicated. - To change a routine's prompt: cancel it, then schedule the new one.
- Room re-entries can be routines too:
schedule_room_followuptakes the samerepeat/day.