How this helps you
If you lose access or a Bot breaks, you have written instructions to rebuild your setup instead of starting from memory.
✦ Try it
Document every Bot's job, rules, memory, skills and routines into a recovery doc in my Drive. Include a table of connections but no passwords or keys. Add a rebuild order where routines are recreated paused. Then set up a monthly routine to keep it current.
What they did
@Michael_Fenech_ wrote a 6-step prompt: map each Bot's job, rules, memory, skills and routines; save a recovery pack in Drive or OneDrive (a connections table, no passwords or keys); set a rebuild order with routines recreated paused; test-restore one workflow; add a monthly update routine; and plan a safe restart with no duplicate sends.
Who it's for: Anyone who relies on several Bots daily.
Before you start
- Google Drive or OneDrive connected, so the pack lives outside your Grok Bot account.
How to try it
- Run the prompt with your main Bot and let it ask each Bot to document its own job, rules, memory, skills and routines. The post warns not to assume one Bot can see what the others learned.
- Check the recovery pack: a readable rebuild doc plus a connections table (app, account, which Bots use it, what they may do) with no passwords, API keys or tokens.
- Review the rebuild order: reconnect apps, create Bots, restore instructions, add skills, then recreate routines paused, with approval rules set before anything is enabled.
- Do a test rebuild of one non-critical workflow with external actions paused, and ask the original and rebuilt Bot the same three questions to compare.
- Approve the monthly update routine, with dated versions and an alert if a backup fails.
- Keep the one-page Start here checklist: what is backed up, what needs manual rebuilding, what to restore first, and what will not come back (such as chat history).
- When the doc exists, point your chief of staff Bot at it and ask for an audit: what each Bot does, overlaps, and Bots you could retire. @jangro did this and retired two Bots.
What to expect
A private folder with a rebuild document, a connections table and a Start here checklist, refreshed monthly.
Common mistakes
- Including passwords or keys in the document.
- Turning rebuilt routines on all at once. The post says to enable them one at a time, checking for duplicate sends.
Related tips
- Keep lasting rules in the description, not memory: Duplicate a Bot and the description comes along; memory starts empty.
- Start with a chief of staff Bot: Talk to one coordinator Bot and let it hand work to your specialist Bots.
- One job per Bot: Give each Bot one job and a list of things it never does.
- Check usage and update your Bot's computer in Settings: Where to see how much of your weekly usage is left, and when to update or reset the Bot's cloud computer.
- Use a group thread to watch Bots work together: Put several Bots in one chat so you can see every handoff instead of hidden Bot-to-Bot messages.
- Turn a Bot into a team Bot your colleagues can use: Share a working Bot with your team as an internal tool, with owners who edit and users who just use it.
- Run a weekly Bot audit to merge or retire extras: Once a week a Bot reviews your whole team and proposes which Bots overlap, which are idle and which do too much. You make the changes.
- Keep a restore skill for when your Bot's computer is updated: Files and logins survive a computer update; installed tools don't. A restore skill puts them back in one message.
- Clean up a messy folder safely: plan first, move after you approve: A cleaner Bot finds exact duplicates and proposes where every file goes. Nothing moves until you approve, and it checks every file is still there afterwards.
- Package your whole Bot setup into one zip you can rebuild from: One prompt makes your Bot bundle your preferences, memory, skills, routines and instructions into a zip with a README, without any passwords or keys.
Worth knowingFollow-up from @jangro: after the backup exists, ask your chief of staff Bot to audit it. He ended up with a list of changes and cleanups, and retired two Bots. Deleting a Bot removes its routines with no undo, so back up first.
Learn more: How to Use Grok Bot: A Beginner's Guide (2026) · All Grok Bot multi-bot setups tips