What is a Grok Bot template?

First, what a Grok Bot is

Grok Bot is xAI’s product for persistent AI teammates, in beta since 11 August 2026. A Bot is a named agent with a defined job, its own conversation and memory, and access to applications through connectors or a browser. It runs on a persistent cloud computer — a managed Linux machine with a filesystem, terminal and browser sessions — so it can keep working while your laptop is closed.

Every user gets one cloud computer, and all of that user’s Bots share it. Two Bots are not separate security boundaries: they share files, browser cookies and command-line credentials. That shared-computer model is the single most important thing to understand before you install anything.

A Bot is built from a few parts: instructions (its role and when to act), memories (what it knows about how you work), skills (reusable step-by-step methods), and routines (a skill placed on a schedule or an event trigger). A template packages those parts.

What a template contains

When you choose “Share as template” — or ask the Bot to pack itself — Grok Bot reviews the Bot’s configuration and stages an unpublished draft. It tries to keep the parts a stranger needs and strip anything personal. Nothing is public until you inspect the draft and publish it, either to your team or as a public link.

• The Bot’s instructions and role
• Selected memories — the author chooses which ones travel
• Skills — the reusable methods the Bot uses to do its work
• Routines — schedules and event triggers
• References to first-party Grok Bot integrations (the connector, not your credentials)

What a template does not contain

A template is not a clone. Several things are excluded by design, and this is what makes a bare share link an incomplete setup for anything non-trivial:

• Conversation history
• The cloud computer and its files
• Signed-in sessions and logins
• API keys and other secrets
• Custom MCP servers, scripts and code

Why the exclusions matter

If a Bot depends on a custom MCP server, a script, or a connector that is not first-party, none of that travels in the link. The recipient gets the instructions and skills but has to rebuild the wiring themselves.

This is why a complete template — the kind worth paying for — ships with a written setup guide: which connectors to add, which accounts and API keys to create, which scripts or MCP servers to install, the order to do it in, and how to test the Bot safely before pointing it at a live system. xAI’s guidance tells template authors to have the Bot generate exactly these instructions. The guide and the extra files are the real deliverable; the link on its own is not.

Template vs prompt vs skill

A prompt is a single instruction. A skill is a reusable method for one task — steps, decision rules, expected output, safety boundaries. A template is a whole Bot: a role plus one or more skills plus routines plus the integration setup around them.

So a template is closer to “a bundle of skills with the wiring done” than to a single prompt. That is also why templates command higher prices than prompt packs — there is more in the box and more work to reproduce it.

How installing a template works

Open the share link. Grok Bot shows a preview on x.ai with the Bot’s configuration and the integrations it expects. Review it — the link exposes whatever the author put in it. Then click “Add to Grok Bot” and Grok Bot creates a new, independent Bot in your account from that recipe.

Adding a shared Bot means accepting xAI’s third-party bot terms. After install, follow the setup guide to connect accounts and add any scripts or MCP servers, then run the Bot on a safe test before giving it real work.

Free and paid templates

Templates can be free or paid. A free template is usually a lighter setup with no custom scripts — enough to get a useful Bot running. A paid template adds the full setup guide, the scripts and MCP configuration the link cannot carry, a recorded example of the Bot working, and a dated changelog that tracks which Grok Bot build it was last verified against.

That changelog matters because Grok Bot is a fast-moving beta. A setup that worked last week can break this week, so a maintained template is worth more than a one-off link found in a directory.