How this helps you
You hand over a working setup in one link, without giving anyone access to your email or accounts.
Before I publish this template, list every rule, memory, skill and routine it includes, and quote any line that mentions a person, client, email address, account, price or internal link. Suggest a neutral replacement for each one.
Fill in: No placeholders. Run it in the Bot's chat right after Share as template.
What they did
After building a weekly research Bot, Mikey No Code shows how to reuse it or hand it to someone else. From the chat, Share then Share as template asks the Bot to package itself. It lists what's included: its memories and preferences (delivery rules, the 7-day research format, briefing details, the hand-off to another Bot), the research and report skill, the Monday routine, and a note that Gmail must be connected. A privacy filter removes private conversation history, email addresses, internal account IDs, OAuth tokens, API keys and other credentials. A card appears; View details lets you inspect it, Publish makes a shared link, and Copy link gives you the URL.
Who it's for: Team leads, consultants and anyone who built a Bot a friend or colleague wants.
Before you start
- A Bot that already works the way you want.
- Someone to share it with, or a second account where you want the same setup.
How to try it
- Open the Bot's chat and click Share in the top right, then Share as template.
- Read the list of what the template will include. Ask the Bot to drop anything you don't want shared.
- Click View details on the card and check the rules and skills for anything personal, such as names or client details in a prompt.
- Click Publish, then Copy link.
- Send the link. The other person connects their own apps (Gmail here) after importing.
What to expect
A short list of included parts and two or three flagged lines, such as a client name inside a skill, with a suggested generic wording.
Common mistakes
- Trusting the filter with details written into instructions. It removes credentials and history; names you typed into a skill can stay. Read View details.
- Sharing a Bot that still has bugs. Fix it first; every copy inherits the problem.
- Forgetting the connections. The template notes required apps, but the other person has to connect their own.
Related tips
- 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.
- Build a weekly research briefing Bot from scratch, then test run it: Create a research Bot with a clear role, check it understood, connect Gmail, save a report skill, and schedule it for Monday 9:00 a.m. Then press Test run instead of waiting a week.
- 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.
- 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 knowingCarved from a segment of this video starting at 19:23. Paraphrased by us; watch the original for the full walkthrough.Next in Multi-bot setups →Promote a Bot to director and let it build and run its own team
Learn more: How to Use Grok Bot: A Beginner's Guide (2026) · All Grok Bot multi-bot setups tips