Package your whole Bot setup into one zip you can rebuild from

How this helps you

If you switch tools or lose a Bot, you rebuild from a written copy instead of from memory.

Package my whole setup into one .zip file so a different AI agent can rebuild it exactly.

Include:
- who I am, my preferences and how I like you to talk
- everything you remember about me and my work
- every skill, workflow, routine and scheduled task, with exact steps
- my custom instructions and system prompts, word for word
- every tool and integration you use and how it's set up (never passwords or API keys)
- the files and templates my workflows depend on

Put a README at the top that tells the new agent how to rebuild everything, step by step.

If you're unsure about anything, ask me before you zip it.

What they did

EXM7777 noted that people switch between personal agents often and rebuilding a workflow from scratch each time is a hassle. So he shared a prompt you send to your current agent. It packages your whole setup into one .zip that a different agent can rebuild from: who you are and how you like it to talk, everything it remembers about you and your work, every skill, workflow, routine and scheduled task with exact steps, your custom instructions word for word, every tool and integration and how it's set up (never passwords or API keys), and the files and templates your workflows depend on. A README at the top explains how to rebuild everything step by step, and it must ask you if it's unsure before zipping.

Who it's for: Anyone trying another agent, and anyone who wants a backup they can read.

Before you start

• A Bot that has been working for you long enough to have memory, skills and routines.
• Somewhere private to keep the zip, such as your own Drive.

How to try it

1. Send the prompt below to each Bot whose setup matters (or to your main Bot, naming the others).
2. Answer its questions; the prompt tells it to ask before zipping if unsure.
3. Open the zip and read the README. Check every skill and routine is there with exact steps.
4. Search the files for passwords, tokens and API keys before you store or share it.
5. Repeat it every month or so, or keep the backup-recovery-plan routine running alongside it.

What to expect

A zip with a README, a profile file, a memory file, one file per skill and routine, an integrations list without secrets, and the templates they use.

Common mistakes

• Skipping the secrets check. The prompt says never include keys, but search the files anyway.
• Storing the zip somewhere shared. It describes you and your work in detail.
• Doing it once. Setups change weekly; refresh it.

Related tips

• Back up your whole Bot setup: Have each Bot document its job, rules, skills and routines into a recovery doc, kept current monthly.
• Import what another AI assistant knows about you in four steps: Settings, Import Memory gives you a prompt to run in your old assistant. Paste its answer back and choose Add to Memory, so your Bots start with your preferences and context.
• Share a finished Bot as a template without sharing your accounts: Share as template packages a Bot's rules, skills and routines. A privacy filter strips chat history, email addresses, account IDs, tokens and keys before you publish a link.

Worth knowingThe prompt is quoted from EXM7777's post on X (capitalisation tidied); the steps are ours.

Learn more: How to Use Grok Bot: A Beginner's Guide (2026) · All Grok Bot security & vault tips