Grok Bot skills and routines: schedules, triggers and testing
A skill is how a Bot does a task; a routine is when it does it. Get a task right once, save it as a skill, then ask for a routine on a schedule or a trigger such as a Slack message, an email or a webhook. Test it, check the first run, and keep it silent when nothing changed.
Make the task reliable first
Do the job once in chat with a real, safe input. Fix the output in plain words until it is right, then say: "Save the process we just used as a skill called Weekly account health. Include the sources, the output format and the rule that customer contact needs my approval."
Ask for the routine in plain words
Ask the Bot that should own the job: "Every weekday at 8:00 AM, run the Weekly account health skill and post a watch list here. Do not contact customers. If a source is unavailable, report the failure instead of using old data."
Before you confirm, check six things: the owning Bot, the schedule and time zone, the input source, the expected result, the approval boundary, and what happens when a source is missing.
Schedules and time zones
- Schedules use the time zone in Settings, under Bot, Timezone. Auto-detect follows your computer.
- Open the routine and read When to run, which shows the saved schedule in words.
- A new routine waits for its next scheduled time; it does not run immediately. Use Test to try it now.
Event triggers
- Slack: when the Bot is mentioned, a phrase appears, you react, or any message. Keep channels and phrases narrow.
- Email to your Bot's own address.
- GitHub, Linear, Sentry and PagerDuty events.
- Webhooks: the routine shows a POST URL and a bearer key. A 200 response means a run started, not that it finished.
- Only new activity counts. Events from before the trigger existed do not start a run.
Test before you trust it
A test run does real work, so use safe inputs and keep write actions behind approval. Check that it picked current inputs, matched the format, left an audit trail, stopped at the approval point and reported failures clearly.
Routine habits that save usage
- Stay silent on no-op runs. A Bot that reports "nothing new" every hour trains you to ignore it.
- Match the schedule to how often things change. Daily reports no one reads waste your weekly pool.
- Ask for the routine to stay paused until you have checked a test run, and say so in the instructions. The docs do not make this a default, so write it in.
- Keep a seen-list file so the Bot only reports new items.
FAQ
Does a new routine run right away?
No. Per the docs, a new routine waits for its next scheduled time. Use Test to run it now.
What can trigger a routine?
A schedule, or an event: a Slack message, an email to the Bot's address, a GitHub, Linear, Sentry or PagerDuty event, or a webhook call.
Can I teach a Bot by showing it?
Where Teach a task is available, you can record a browser workflow of up to ten minutes and the Bot drafts a skill from it.
Related Grok Bot news
- How to write Grok Bot instructions: 12 rules for a reliable Bot
- How to set up Grok Bot as a second brain
- Grok Bot token efficiency and behavior fixes are underway, says Matt Palmer
Keep learning
- Grok Bot instructions best practices: 12 patterns for reliable Bots
- Grok Bot connectors and apps: Gmail, Slack, Notion, X, MCP and more
- How Grok Bot works: computer, memory, skills, approvals and Team Bots