A bilingual learning hub for Grok Bot: go from first prompt to a fleet of working bots, with curated use cases you can copy-paste and shareable bots you can add in one click.
The shortest beginner path we can recommend without pretending Grok Bot is simpler than it is.
01
Build the right mental model before you touch prompts, plugins, or shared bots.
02
Get Grok Bot running, set its first role, and verify it can actually do things for you.
03
Turn a one-off prompt into a workflow that runs again tomorrow: role, files, routine, report.
04
Shared bots skip the setup interview — review, click, and it's yours. Here's how to do it safely.
05
The five-minute diagnostic loop that fixes most broken bots before you touch any settings.
Curated from grokbot.dev and the X community: every entry carries the full prompt, a plain-language setup, and credit to its original author.
Vlad Dubchak's team (Maxfusion) open-sourced their marketing department as one skill — Marketing OS. Fourteen modules cover audits scored 0-100, an 18-tactic hook engine, graded copy, ad diagnosis, GEO, email, social, launches and positioning. Hand Grok Bot the repo link and it's ready in minutes.
Get the prompt →Avid's chief-of-staff prompt: it mines everything you've done on your machine — configs, recurring tasks, repeated prompts, the corrections you keep giving — and turns it into a real agent team with role files, skills, a verified run and a handbook, all written to files.
Get the prompt →Teslaconomics built 'Cart' - a Grok Bot that does his Amazon shopping. It signs into his Amazon, reads Buy Again and past orders, and puts the exact products he already buys into the cart; he just checks out. It works for anything on Amazon, and it never places the order or touches payment - those stay with him.
Get the prompt →Paste one prompt into a single Grok Bot, Atlas the chief of staff. It interviews you, writes its own operating manual, then specs and launches four teammates — each on its own cloud computer, with a review gate before anything sends.
Get the prompt →MIT's Markus Buehler ran a three-bot team that turned four reference photos into transferable design principles, an interactive physics simulator, 47 experiments, a scientific report, and two parts sliced and printed on a Bambu H2D — the whole loop overnight.
Get the prompt →Ridark gave Grok Bot his content calendar instead of a to-do list: seven named bots on one shared machine - discovery, research, writing, visuals, distribution, analytics, and Anchor, the chief of staff he DMs. One group chat per post, hard approval fences, and week one shipped 14 of 25 drafts with his inbox at zero.
Get the prompt →Whole packaged bots shared by builders on X. Open the install link and Grok Bot does the rest.
Every weekday morning it assembles a short macro read-out: what the Fed and markets are doing according to X news, with prediction-market FOMC odds folded in as a sentiment gauge. Then it turns to your own timeline and advises whether to quote something, write a fresh post, or sit this one out.
Over time a bot's notes and memory fill with instructions for jobs that no longer exist, and it keeps honouring them. Optima reads through that material, works out which files belong to which project, checks with the bot that owns each rule, and presents a removal list for you to approve before anything is deleted.
Describe a chore you dread, whether paperwork that needs notarising, a return that has to be shipped, or a queue you would rather not stand in, and it works out how a person with money would offload it. You get the type of service to hire, named providers where possible, and a rough price so you can decide quickly.
Foundations, prompt patterns, agent teams, channels and routines, memory, security hardening, and day-to-day operating tips.
teams
When one bot stops being enough: roles, a coordinator, shared channels, and the discipline of small teams.
teams
You installed a shared bot. Now make it yours in five edits — without breaking what the author got right.
tools
A bot with no tools can only talk. Here's how to connect capabilities without losing control.
Start from what failed, narrow the likely causes, and only then change prompts, permissions, or workflows.
Shared bot behaves off-spec
You installed someone else's bot and it's doing something odd. Diagnose, then customize or evict.
Behavior contradicts the prompt
The prompt says one thing, the bot does another. Find which layer is actually in charge.
Report arrives, nobody reads it
The bot runs fine and produces things you never read. Fix the format and the filter, not the schedule.