メニュー
Nighttime dreaming. Reviews the past 24 hours of this session's conversation, reflects on what matters, overwrites dream.md with the result, and may schedule one next-day follow-up wake. Triggered by the heartbeat scheduler at night (should_dream=true) — never call directly.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Schedule nagobot's own background jobs — recurring tasks, one-time delayed tasks, and repeating reminders that nagobot itself delivers to the user as a message. Use when the user wants something to happen automatically later or on a repeat (every morning, every Monday, daily at a set hour, in two hours), or wants to create, update, remove, or list existing cron schedules. For an entry in the macOS Reminders or Calendar app instead, use apple-apps.
Use when about to call the `dispatch` tool and unsure which `to` form to pick, when a dispatch validation error reports a mismatch between asserted caller kind and actual caller, or when handling a `child_completed` wake from a previously dispatched subagent/fork. Focused decision tree for routing replies (caller:user / caller:session / user / session), spawning (subagent / fork), receiving child results, and silent termination.
Use when you need to interact with other threads or manage thread lifecycle. Covers dispatching work to subagents / forks / existing sessions via a single primitive, inspecting session state by key, scheduling a delayed self-wake (via the manage-cron set-at --direct-wake job), and running health diagnostics across all active threads.
Routing layer for heartbeat pulses. Reads pulse_index from the wake message and dispatches to the appropriate sub-skill. Called automatically by the heartbeat scheduler — never call directly.
Background reflection on conversation history. Extracts user preferences, corrections, and workflow patterns into USER.md. Triggered by heartbeat at the 4-hour quiet mark — never call directly.
Control Apple apps on this Mac (Calendar events, Reminders app items, Notes, Contacts, Mail), macOS system settings (dark mode, volume, Wi-Fi, app launch, Finder, sleep/lock), and Spotlight file search via AppleScript and shell commands. Use when the action must land in the user's real macOS apps — an appointment in their calendar, a checkbox in their Reminders list, a note, a system toggle. For nagobot's own scheduled jobs, use manage-cron instead. Loads as a router — read the relevant reference file for the task at hand instead of pulling everything into context.
| name | dream |
| description | Nighttime dreaming. Reviews the past 24 hours of this session's conversation, reflects on what matters, overwrites dream.md with the result, and may schedule one next-day follow-up wake. Triggered by the heartbeat scheduler at night (should_dream=true) — never call directly. |
The heartbeat scheduler decided this session should dream. It is night and the user has been quiet for a while. Look back over the past 24 hours of conversation, reflect on what happened, organize what matters, and write a fresh dream into dream.md.
This is a BACKGROUND task. You will NOT message the user.
Review the past 24 hours. The recent conversation is already in your context — use the timestamps to scope to the last 24 hours and ignore anything older. (The full session log is at {{SESSIONDIR}}/session.jsonl if you need more than what is in context.)
Reflect on that 24-hour window. Stay grounded in what actually happened. Cover:
Overwrite dream.md. Use write_file to write {{SESSIONDIR}}/dream.md.
dream.md completely — do NOT append to or merge with the old dream. Each night's dream fully replaces the last one.Refresh this session's one-line summary. Distill the whole session — who this is, what it's about, its current state — into a factual summary of at most 200 characters, weighted toward recent activity, written in the language the conversation predominantly uses. Save it:
exec: {{WORKSPACE}}/bin/nagobot set-summary {{SESSIONKEY}} "<summary>"
This feeds the cross-session awareness section injected into every agent's system prompt — it is how other sessions know what this one is about. Refresh it every dream night, even when the past 24 hours were quiet.
Plan a follow-up for the day ahead. Put yourself in the shoes of a friend who cares about this user. Based on the past 24 hours: is there a greeting or follow-up worth sending them tomorrow, and when? ("Tomorrow" as the user will experience it — dreams run in the small hours, so it is usually later this same calendar day.)
Think of up to 3 candidates. For each: what to send, when to send it, and a suitability score — low / medium / high. Include them in the dream you write in step 3, under a ## Follow-up heading.
If at least one candidate scores high, schedule the single best one as a one-time direct wake into this session:
exec: {{WORKSPACE}}/bin/nagobot cron set-at --id <short-descriptive-id> \
--at "<RFC3339 time, session-local offset>" \
--task "<the plan>" \
--wake-session {{SESSIONKEY}} --direct-wake
Write --task so tomorrow-you can act on it directly: what to send and why, with enough context from today's conversation. It must also instruct: first look at the recent conversation — if the moment has passed (the user already brought it up, or the follow-up no longer feels natural), end silently with dispatch({}); otherwise send it via dispatch(to=user).
No candidate scores high → schedule nothing. A day with no natural follow-up is normal; do not force one.
Tidy the workspace. After the dream, run the file-track skill — use_skill("file-track") — and follow it to archive stale files and refresh file-track.md. Same nightly-maintenance spirit as the dream: keep this session's work files organized and catalogued. Do this even on a quiet night (it's about files on disk, not the conversation).
End silently. Call dispatch({}) with empty sends. Produce NO user-facing output.
dream.md completely; never append to the previous dream.dispatch({}).dispatch({}) — silent termination.