菜单
Send a local file (PDF, document, archive, code, log, generated HTML, anything non-image) to the user as a native channel attachment by writing standard Markdown link syntax `[label](path)` in your reply. Supported on Discord and WeCom; falls back to plain text on other channels.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
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.
基于 SOC 职业分类
| name | send-docs |
| description | Send a local file (PDF, document, archive, code, log, generated HTML, anything non-image) to the user as a native channel attachment by writing standard Markdown link syntax `[label](path)` in your reply. Supported on Discord and WeCom; falls back to plain text on other channels. |
Send local files to the user by writing standard Markdown link syntax inline in your reply text. The platform parses your reply, finds links whose target is a real file on disk, and uploads each one as a native channel attachment — without modifying the text you wrote.
This is the non-image counterpart to send-image: same wiring, same workspace-relative path rules, but for arbitrary file types.
Standard Markdown link:
[label](path)
label — short description (may be empty: [](path)).path — an absolute filesystem path (e.g. {{WORKSPACE}}/media/report.pdf).The link can appear anywhere in your reply, including mid-paragraph. It does not need its own line.
Inline in a sentence:
Here is the analysis [Q1 report](media/q1-report.pdf) — see page 3 for the spike.
On its own line:
Sure, here is the dataset.
[raw data](/Users/me/.nagobot/workspace/media/dataset.csv)
Multiple files in one message:
Two artefacts: [build log](media/build.log) and [bundle](media/dist.zip).
The platform only uploads if the path resolves to a real local file. The following are left as plain Markdown links and not uploaded:
https://..., http://..., anything containing ://)mailto: / tel: schemes#section)This means you can freely intermix hyperlinks ([Discord docs](https://discord.com)) and file attachments ([my report](media/q1.pdf)) in the same reply — only the latter trigger an upload.
| Intent | Syntax | Skill |
|---|---|---|
| Send an image (rendered inline if the channel supports it) |  | send-image |
| Send any other file as an attachment | [label](path) | send-docs (this) |
If you write  to a non-image file, the image dispatcher rejects it (magic-byte check) and nothing is delivered. Use [label](path) for anything that isn't a normal raster image.
If you write [label](path) pointing to an image file, it is uploaded as a generic attachment (filename preserved). Discord shows it as an inline image preview either way, so usually prefer  for images.
Link syntax inside a fenced code block (``` or ~~~) or inline backticks (`) is not parsed as a doc link. The Markdown stays as literal text.
Use `[label](path)` to send a file.
The line above is shown to the user as plain text — no upload.
| Channel | Doc Send |
|---|---|
| Discord | supported (≤25 MB without Nitro boost; oversized uploads fail and are logged) |
| WeCom | supported (≤20 MB; uploaded via aibot media flow as msgtype=file) |
| Telegram | not yet |
| Feishu | not yet |
| Web / CLI / Socket | not yet |
On unsupported channels the Markdown link remains in the message and renders normally (a link to a path the user can't reach). No upload happens. Don't reference doc syntax when the user is on a channel that does not support doc send.
{{WORKSPACE}}. Other relative roots will not resolve.path — choose a meaningful filename when generating the file (e.g. q1-revenue.pdf, not out.pdf).create-html (when the user explicitly wants the file, not a hosted URL).send-image with .create-html (writes file → uploads via upload-html → returns URL).