You’ll need
A Grok Bot account. Nothing else yet.
Most people use Grok Bot as one long chat that does everything. It works for a week. Then the chat gets long, the bot loses context, and you become the glue that copies work from place to place. This course moves you, one small step at a time, to a setup where each bot owns one job, shares the same house rules, remembers what matters, runs on a schedule and asks you before anything leaves the building.
Steps
See the finish line
By Module 9 you’ll have: one primary bot that coordinates (a “chief of staff”), two to four bots that each own a lane, a shared skills library, at least two routines that run on their own, a backup habit, and a written list of what always needs your approval.
Know the lesson shape
Every lesson has the same parts: a one-line goal, the steps (with a screenshot per step as we add them), a copy-paste prompt, a “check it worked” test, common mistakes, and a short checklist. Tick the boxes as you go. Your progress is saved in this browser.
Go in order, but skip what you have
Modules build on each other: foundations, then skills, memory, connectors, routines, the swarm, templates, full playbooks and a capstone. If you already do something well, read the “check it worked” test. If you pass it, move on.
Keep a notes file
Create one note called “My swarm” where you paste each bot’s job description and what you learn. You’ll turn it into your swarm map in the capstone.
Copy-paste prompt
Paste this to your bot. Replace anything in [brackets].
I’m starting a course on running Grok Bot well. Before we change anything, describe my current setup in a short list: how many bots I have, what each one does, which apps are connected, which skills and routines exist, and anything you think is risky or repeated. Don’t change anything yet, just report.
Check it worked
- You have a short written snapshot of your current setup from your bot.
- You know which module you’ll start with.
Common mistakes
- Trying to build the whole swarm on day one. One bot, one job, then add the next.
- Skipping the “check it worked” tests. They’re how you know a step really stuck.
Checklist
Sources: Grok Bot docs: Skills and routines