メニュー
Send images to the user by writing standard Markdown image syntax in your reply. Supported on Discord and WeCom; falls back to plain text on other channels.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
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.
| name | send-image |
| description | Send images to the user by writing standard Markdown image syntax in your reply. Supported on Discord and WeCom; falls back to plain text on other channels. |
Send images to the user by writing standard Markdown image syntax inline in your reply text. The platform parses your reply, finds the image references, and uploads them to the channel as native attachments — without modifying the text you wrote.
Standard Markdown:
alt text — short description (may be empty: )path — an absolute filesystem path (e.g. {{WORKSPACE}}/media/photo.jpg)The image markdown can appear anywhere in your reply, including mid-paragraph. It does not need its own line.
Inline in a sentence:
Here is the result  — note the spike on day 3.
On its own line:
Sure, here is the screenshot.
Multiple images:
Comparing the two:  vs .
Image syntax inside a fenced code block (``` or ~~~) or inline backticks (`) is not sent as an image. The markdown stays as literal text. This lets you talk about image syntax without triggering an upload.
Use `` to send an image.
The line above is shown to the user as plain text — no upload.
| Channel | Image Send |
|---|---|
| Discord | supported |
| WeCom | supported (≤10 MB per image) |
| Telegram | not yet |
| Feishu | not yet |
| Web / CLI / Socket | not yet |
On unsupported channels the markdown remains in the message and is rendered (or left as text) by the channel's normal Markdown handling. No upload happens. Don't reference image markdown when the user is on a channel that does not support image send.
{{WORKSPACE}}. Other relative roots will not resolve.