Grok Bot Skills vs Routines: How to Automate a Recurring Task
- A skill is the method: a reusable set of instructions for how to do a task. A routine is the timing: it tells one Bot when to run a workflow, on a schedule or when something happens.
- The official order is one-time task, then make it reliable, then save it as a skill, then create the routine.
- Every routine run spends usage, and anything that goes out (sending, buying, deleting, publishing) should wait for your approval.
If you're weighing Grok Bot skills vs routines, the short version is that you usually need both. The skill holds how the work is done, and the routine decides when it happens. This page shows how to build each one, in the order the official docs recommend.
What is the difference between a skill and a routine?
A skill is a reusable set of instructions for how to do a task, and a routine tells one Bot when to run a workflow, either on a schedule or when something happens. Put simply, the skill is the method and the routine is the start button that fires on its own.
| Skill | Routine |
|---|---|
| A reusable set of instructions for how to do a task | Tells one Bot when to run a workflow |
| Answers "how is this done?" | Answers "when does this run?" |
| Available across your Bots, though a Bot may need the right app or login to use it | Owned by one Bot, and spends usage on every run |
| Private skills sit in one library shared by all your Bots | A Bot can own up to 50 routines |
| You use it by asking a Bot for it by name | Starts on a schedule or a trigger, such as a Slack message or an email |
Routines run in the cloud, so they keep working while your laptop is closed.
How do you automate a recurring task?
Follow the order the official docs give: start with a one-time task, make it reliable, save the method as a skill, and only then automate it with a routine. Skipping straight to a routine means automating something you haven't seen work yet.
Start here: four steps
- Do it once. Ask a Bot to do the task one time, in chat, with real but safe inputs.
- Make it reliable. Run it again, fix what it got wrong, and tighten your instructions until the result is what you want.
- Save it as a skill. Ask the Bot to save the method as a skill, so you and your other Bots can call it by name.
- Create the routine. Only now give the Bot a schedule or a trigger, using the checklist below.
That order comes from the official skills and routines docs, paraphrased.
The official skills and routines docs describe a Teach a task option that builds a skill from a demonstration, "when Teach a task is available." The official FAQ says the rollout may be gradual, so you may not see it yet. If the control is missing, ask the Bot to create a skill from your written instructions and the task it just completed.
What makes a good skill?
A good skill says when to use it, what inputs and access it needs, the order of the work, how to check the result, what to return, and what needs your approval. Those six things, from the official docs, are what let a Bot repeat the task the same way each time.
- When to use it. The situation that calls for this skill.
- Required inputs and access. What it needs from you, and which app or login.
- The sequence of work. The steps, in order.
- How to validate the result. What a correct result looks like, so the Bot can check itself.
- What to return. The format you want back.
- What requires approval. The points where the Bot stops and asks you.
Remember that skills are shared across your Bots, but a Bot may still need the relevant app or login before it can use one. To run a skill, ask the Bot for it by name.
How do you create a routine?
Ask the Bot for the routine in plain words, then open it and check "When to run," confirming the six items in the checklist below. A new routine doesn't run when you create it; it waits for its next scheduled time, so use Test if you want to try it right away.
Routine checklist (from the official docs)
- The owning Bot. Which one Bot runs it.
- Schedule and time zone. Schedules use the time zone set in Settings under Bot (Timezone).
- Input source. Where the routine gets what it works on.
- Expected result. What it should hand back each run.
- Approval boundary. What it may do on its own, and what waits for you.
- What happens if a source is missing. For example, report that the source was empty rather than guess.
About Test. The skills and routines page is blunt: "A test run performs real work." It can navigate websites, change files and call connected tools, so use safe inputs and keep write actions behind approval. Some routines don't show Test; for those, ask the Bot to do the same work once in chat with a safe input.
To manage routines later, ask the Bot in chat or open the Bot's details on desktop. Each routine can be paused or resumed, run with Test when it's offered, edited or deleted. Deleting a routine stops future runs, and it can't be undone, so pause instead if you might want it back.
What can start a routine?
A schedule, or an event: a Slack message, GitHub, Linear, Sentry or PagerDuty events, an email to the Bot's own address, or a webhook. Keep triggers narrow, because each run spends usage, and the docs advise against listeners that fire on every new message.
Two details from the docs that trip people up:
- Only new activity counts. Events from before the trigger existed don't start a run.
- Trigger connections are separate. Trigger integrations are separate from the Slack or GitHub apps your Bot already uses, and they may need their own connection.
If a trigger doesn't seem to fire, Grok Bot Not Working? Fixes for Routines and Permission Prompts covers what to check.
What do routines cost in usage, and what are the limits?
Every run spends usage, so a routine's cost depends on how often it fires; a routine that never runs spends nothing, but pressing Test does, because a test does the real work. The official limits are 50 routines per Bot and schedules at least five minutes apart.
The limits in full, from the official docs:
| Limit | Official figure |
|---|---|
| Routines per Bot | Up to 50 |
| Run records kept per routine | The 20 most recent |
| Time between scheduled runs | At least five minutes |
| Runs per hour, all routines together | Up to 300 |
| Runs per hour, one routine | Up to 200 |
Those are ceilings, not targets. To keep usage under control, narrow Slack triggers, avoid listeners that fire on every new message, and run on the widest schedule that still does the job. Why Grok Bot Uses So Much Usage (and How to Make It Last) shows how to find which routine is using the most.
How should a routine handle approvals?
Have the routine prepare work, not finish it: draft, reconcile or recommend first, and require your approval for sending, purchasing, deleting, publishing or changing production systems. The docs also advise a policy for when data is missing or out of date, so the routine reports it instead of acting on it.
The Daily Email and Calendar Brief is a good example of that design. It's one of my templates. It reads your email and calendar and gives you a short brief of what today holds and what needs you, leading with what needs action. It runs when you ask, or on a schedule you set. It never replies, RSVPs, deletes or sends anything to anyone but you. See the Daily Email and Calendar Brief page for what it does and never does, and How a Daily Brief Bot Can Start Your Workday for how a morning brief fits into a routine.
My standing rule for any bot that touches the outside world goes one step further: drafts only, a person approves, and for anything that sends or cancels, one yes on the item and a second yes on the exact text and recipient.
FAQ: Grok Bot skills vs routines
Can I schedule a Bot to run at a set time?
Yes. Ask for the schedule in plain words, then open the routine and check "When to run." Schedules use the time zone set in Settings under Bot (Timezone).
Does a routine run while my laptop is closed?
Yes. Routines run in the cloud, so they keep working while your laptop is closed.
Can I stop a routine?
Yes. You can pause or resume it by asking the Bot in chat or from the Bot's details on desktop. Deleting a routine stops future runs and can't be undone, so pause it if you might want it back.
What happens if the source is missing?
That depends on what you told it, which is why "what happens if a source is missing" is on the checklist. The docs advise a no-data and stale-data policy, so the routine reports the gap instead of guessing.
Can I test it first?
Yes, with Test, which runs it right away. A test run does real work, so use safe inputs and keep write actions behind approval. If a routine doesn't show Test, ask the Bot to do the same work once in chat.
If you want a set of ready-to-install bots, in order, that look for money before they ask you to spend more of it, see The Payback Roadmap.
This bot is one piece of a full AI team. See how I run my business with a team of Grok bots. The AI Chief of Staff: How I Run My Business With a Team of Grok Bots