Lauren Tan's guide to a small, high-quality Bot team

How this helps you

You get Bots that understand your work and keep doing tasks the same way, instead of a crowd of Bots you have to re-explain things to.

✦ Try it

Read this guide and help me improve my Bot team: [paste the guide or link]. First, here's a brain dump of who I am and the work I do: [voice note or notes]. Restate it in your own words so I can confirm you understood. Then list: the Bots I have and whether any should be merged, the copy-paste steps you could take over and what access you'd need, and three skills you should write for yourself from what I've told you. Don't create or delete any Bot until I say yes.

Fill in: [paste the guide or link] is Lauren's post (linked on this page) or your own notes. [voice note or notes] is your brain dump, ideally from voice mode.

What they did

Lauren Tan (@poteto) works on Grok Bot and shared how she creates high-quality Bots and manages her team, suggesting people ask their own Bot to read the post and help improve their team. Her points: add Dr. Eggbot, the Bot designer she uses to create Bots. You don't need many Bots; a few good ones are more useful and easier to manage. Tell your Bots to create skills for themselves as you explain how to do tasks, so they stay consistent over long conversations (you can even have one create a private GitHub repo to keep the skills). Add connectors, use the Vault and give access to the tools you work with; a Bot can also set up its own email and sign up for its own accounts for better separation. Look for steps where you copy and paste information to your Bot, and ask it how it could do them instead. Onboard it like an intern: introduce yourself, describe your work and ask how it can help automate it. Her favourite: use voice mode or transcription to brain dump, then tell the Bot to restate it in its own words so you can confirm it understood.

Who it's for: Anyone starting with Grok Bot, and people with a pile of half-used Bots who want fewer, better ones.

Before you start

Grok Bot with at least one Bot you use regularly.
Ten quiet minutes to talk through your work (voice mode or the transcription button).
The apps you work in, ready to connect in Connect apps.

How to try it

Import Dr. Eggbot from the marketplace and use it to design any new Bot, instead of writing descriptions from scratch.
Open your main Bot and brain dump by voice: who you are, what your work is, what you do by hand every week.
Ask it to restate everything in its own words, and correct what it got wrong.
Ask which steps you copy and paste for it today, and how it could do them itself (connector, Vault login, its own email).
Every time you explain how to do a task, tell it to save that as a skill. Optionally ask it to keep the skills in a private GitHub repo.
Before adding another Bot, ask whether an existing Bot could take the job. Keep the team small.

What to expect

A short restatement of your work with a few questions where it was unsure, then three lists: Bots to keep or merge, manual steps it could take over (each with the connector or login it needs), and three proposed skills with one-line descriptions.

Common mistakes

Building ten Bots on day one. A few good Bots are easier to manage and each one gets more context.
Skipping the restate step. It's the quickest way to catch a misunderstanding before it becomes a rule.
Pasting passwords into chat. Put logins in the Vault and let the Bot use them from there.

Related tips

One job per Bot: Give each Bot one job and a list of things it never does.
Add a ready-made Bot from the Marketplace: Browse Bot templates at x.ai/bot/marketplace, read what each one includes, then add your own copy.
Three questions before you create another Bot: Only make a new Bot if the job needs its own memory, different permissions or its own schedule. Otherwise give it to your chief of staff.
Build a three-Bot starter team: Scout, Shopper and Desk: One Bot researches and checks sources, one shops and stops before checkout, one learns a weekly task by watching you once.