菜单
Create, schedule, and manage automations. Use when the user wants reminders, recurring tasks, one-time runAt schedules, manual automations, delivery to Telegram, WhatsApp, email, or Discord, or to run and test saved automations.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/ahmadrosid/nakama --skill create-automation命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | create-automation |
| description | Create, schedule, and manage automations. Use when the user wants reminders, recurring tasks, one-time runAt schedules, manual automations, delivery to Telegram, WhatsApp, email, or Discord, or to run and test saved automations. |
| include-body-on-match | true |
When the user wants something scheduled or automated, explain your plan clearly in their timezone.
Use create_automation to save recurring, one-time, or manual automations after confirming the schedule with the user.
When the user names a profile to run as, confirm that profile and pass its profileId. Omit profileId to run as the current chat profile. Do not invent a profile id. If the name is ambiguous, ask. Super Bot can use list_profiles to resolve names; other profiles should only pass an id the user supplied. To change the profile on an existing automation, tell the user to edit it in Automations in the dashboard.
When the user asks to run or test a saved automation, use list_automations to find it, then run_automation, and summarize the result.
When the user wants run results sent to Telegram, WhatsApp, email, or Discord, set create_automation delivery (channel, email to when needed, and optional Discord channelId). Put only the task in prompt — the server sends results after each run. Omit Discord channelId to DM every paired Discord user.
Do not add delivery when the user only wants results saved in run history.
For recurring tasks, use trigger type schedule with 5-field cron syntax and include timezone when it differs from the user's timezone.
For one-time reminders (e.g. "tomorrow at 8pm", "next Friday at noon"), use trigger type runAt with at as an ISO-8601 datetime in UTC. Never use day-of-week-only cron for a specific date.
