メニュー
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コマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Review a GitHub PR for unnecessary complexity. For PRs authored by someone else, post short human-sounding inline review comments via gh. For PRs authored by the authenticated gh user ("me"), apply the cuts on the PR branch and push — do not post review comments. Use when the user asks for a lean PR review, /lean-pr-review, /lean-review, or wants over-engineering feedback on a PR.
Produce H.264 MP4 browser video proof for a UI fix, upload it to GitHub user-attachments, and put the URL in a PR description. Use for scroll/ layout/interaction proofs (e.g. /automations expanded-run scrolling), recorded E2E demos, or when a reviewer needs visual evidence on a PR.
Explain any topic like the reader knows nothing: big pictures, few words, concrete metaphors, optional self-contained HTML artifact opened in the browser. Use when the user says ELI5, /eli5, "explain like I'm five", "like I know nothing", wants a visual explainer, or asks for big pictures and few words.
| 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.