القائمة
Activate when the user wants a one-time message sent to them at a specific future time (e.g. "提醒我明天早上九點喝水"). Not for recurring work — use create-regular-work for that.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Activate for ANY request involving specialist delegation — single or multi-step. Contains the complete orchestration SOP: plan-and-confirm format, sequential execution rules, how to write a complete `request` argument, recovery from errors, retry limits, file delivery rules, and output presentation.
Activate when a multi-agent orchestration goes wrong. Contains: recovery from `ValueError: Tool '<name>' not found`, the full forbidden-tool reference for each specialist, retry limits and abandon criteria, recovery if you accidentally invoked two specialists in parallel, and the catalogue of historically-reproduced mistakes. Pair with `multi-agent-chain` (the always- loaded core skill) — that one has the happy-path rules; this one has the escape hatches.
Use when delegating report generation, PDF creation, chart visualization, or data interpretation to the business analysis expert. Load this skill before calling `business_analysis(request='...')` so you know what to send, what it returns, and which tools are internal to that specialist (and must NEVER be called directly).
Use when delegating any task to the coding expert — Python scripting, data analysis, SVM / ML algorithms, file I/O, package installation, git operations, or running tests. Load this skill before calling `coding(request='...')` so you know what to send and how to read the response.
Use when a task involves database operations — SQL queries, schema inspection, data retrieval, record insertion/update/deletion, or database health checks. Load this skill before calling `database(request='...')`. IMPORTANT: This specialist may not be deployed — check the registered tool spec first.
Run before marking any task as done. Parses the task spec for output file paths and verifies each file actually exists on disk. If any required file is missing, requeues the task instead of closing it. Skip for tasks with no file output.
| name | create-reminder |
| description | Activate when the user wants a one-time message sent to them at a specific future time (e.g. "提醒我明天早上九點喝水"). Not for recurring work — use create-regular-work for that. |
Do NOT use for recurring work (e.g. "每天提醒我") → activate create-regular-work instead.
get_current_time() to calculate the correct absolute datetime.create_reminder_tool with all of these parameters:
user_id: the hashed_id from the current session (a 16-character hex string, e.g. c9e4719ba839d6b6). This is the same identifier you receive in every tool call. Never put the user's display name (e.g. "Simon") here.session_id: the current session_id (e.g. tg_12345).channel: "telegram" / "discord" / "line" — derive from the session_id prefix (tg_* → telegram, dc_* → discord, line_* → line).recipient: same as user_id (the hashed_id). The notifier will resolve it to the real chat_id via the IdentityMap. Do NOT put the user's name here.message: The exact text to send at that time.run_at: ISO 8601 datetime string, e.g. "2026-04-10T09:00:00".Important:
recipientis an internal routing key, not a human-readable name. Always pass the same hashed_id you got fromcheck_identity/ session context.
| User says | run_at | message |
|---|---|---|
| "提醒我明天早上九點喝水" | next day 09:00 | "該喝水了！" |
| "下午三點提醒我開會" | today 15:00 | "會議時間到了！" |
| "一小時後提醒我回 email" | now + 1h | "記得回覆 email" |