What goes in a Grok Bot template (and what doesn't)
A share link is half a setup. This is the other half: where the missing pieces live and what a complete template ships to rebuild them.
Last reviewed August 29, 2026
When you share a Bot as a template, Grok Bot packages a recipe: the Bot's instructions, selected memories, skills, routines, and references to first-party integrations. That is enough to recreate the shape of the Bot. It is not enough to make it work.
Everything that touches your accounts, your machine, or your identity is deliberately left out. Those pieces still exist — just not in the link. Knowing where each one lives tells you what a template has to bundle alongside the link to be a working setup rather than a sketch.
What travels in the link
These come across when someone adds your template, though a routine still needs its connector connected and its schedule confirmed before it runs:
- Instructions — the Bot's role and when it acts
- Selected memories — the ones the author chose to include
- Skills — the reusable methods
- Routines — schedules and event triggers
- References to first-party integrations — the connector, never the credentials
What doesn't travel — and where it actually is
Each excluded piece lives somewhere specific. A complete template ships something to rebuild it.
- Connectors, accounts and API keys — live in the recipient's own Grok Bot account; they install the connector and sign in themselves. A template ships a setup guide saying which to add, which accounts to create, and where each key goes.
- Custom MCP servers — not in the template at all; an MCP server is a small service the recipient has to run. A template ships its config plus the code or a one-click deploy.
- Scripts and code — sit on the author's cloud computer, which does not transfer. A template ships the script files and instructions to place them on your Bot's computer.
- Writing style and personal memories — are the author's and would not fit you anyway. A template ships the method instead: a skill that has your Bot build its own style profile from your sent mail on first run.
- Conversation history, the computer, signed-in sessions and secrets — stay in the author's account only. Nothing ships; nothing is needed.
So a complete template is a bundle
The link is one file in it. A template worth paying for also contains the parts the link cannot carry:
- The share link
- A setup guide — connectors, accounts, API keys, the order to do them in, and how to test safely
- Scripts and any MCP server config or code
- A changelog, dated and tied to the Grok Bot build it was last verified against
- Licence terms
Free vs paid, in these terms
A free template is usually just the link plus a light setup note — enough to stand up a simple Bot with no custom scripts. A paid template is the full bundle: the setup guide, the scripts and MCP configuration, a recorded example of the Bot working, and the changelog that keeps it current as Grok Bot changes week to week.
Frequently asked
- Why can't the template include my API keys?
- Secrets are excluded by design so a public link never leaks them. You create your own keys after installing, following the setup guide.
- If scripts don't transfer, how do I get them?
- A complete template bundles the script files and tells you where to put them on your Bot's cloud computer. The bare share link does not include them.
- Do routines work straight after install?
- The routine itself comes across, but it needs its connector connected and its schedule confirmed. Run a test before trusting it.