What is a Grok Bot template?

A Grok Bot template is a shareable copy of a bot’s configuration. xAI’s Bots documentation says a copied bot carries the profile, settings, enabled skills, routines and avatar, and “does not copy conversation history, learned memory, or chat attachments.” The share link is public: anyone holding it can preview the bot on x.ai and add a copy to their own account.

That is the whole definition. Everything else on this page follows from it, and most of what is wrong in the free directories comes from ignoring it.

What does a template carry?

xAI turned on template sharing on 28 August 2026, with a one-line post: “You can now share templates of your Bots with others” (source). The docs were more specific about what travels.

Scroll sideways for the second column on a narrow screen.

The left column is from the docs’ description of a duplicated bot, which “carries the profile, settings, enabled skills, routines, and avatar.” The right column combines the same page with the security page, which says a public share link “does not share your computer or logins.”

Why does “no memory” matter more than it sounds?

A Grok Bot template arrives with no memory of anything, and that single fact decides what a template is worth. xAI’s docs say a copied bot “does not copy conversation history, learned memory, or chat attachments.” A shared bot is a copy, so the same applies. Whatever the original learned from six weeks of running, the copy has never seen. Some write-ups claim a template can carry selected memories; the docs say otherwise, and a bot built on that claim arrives amnesiac. The consequence for anyone writing a template is a hard rule: anything durable lives in the instructions, in a skill, in a routine, or in a file the bot writes to a system of record. Nothing durable lives in memory. That is why a template that is one paragraph of persona has so little to sell. The persona transfers. The judgment that made the original useful does not, unless someone wrote it down in one of the four places that travel.

What is the difference between a template and a persona?

Most of the free listings are a persona: a name, a tone and a paragraph about what the bot is for. That copies perfectly, which is why nobody pays for it.

A template that is worth money has four things written into the parts that transfer:

• The outcome it owns. One number or one condition that can be true or false. Ledger owns days sales outstanding. Quartermaster owns committed annual vendor spend. “Help with collections” is not an outcome.
• The evidence standard. What counts as knowing something. A bot that never asserts an amount, date or status without naming the system and the record it came from is a different product from one that guesses.
• The authority boundary. What it may do alone, what needs a human, and what it may never do. The approval rules guide covers this in full.
• The stopping condition. When the job is done, and when to stop and escalate instead of continuing.

Skills and routines are where those four things get encoded, because they are what transfers. xAI’s skills page recommends six sections for a skill, and a routine carries six fields; the skills guide and the routines guide walk through each.

Where does a template run once it is copied?

On the recipient’s computer, not yours. xAI’s computer page says “the computer is assigned to your user account, not an individual Bot.” Every bot on one account shares that computer: “browser cookies and signed-in sessions are shared,” “files are visible to every Bot,” and “command-line credentials are shared.” Installed connectors are account-wide too.

Three things follow for a template author.

First, a template cannot assume any login exists. The buyer authorises every connector in their own account, which is why each Botemplate bot ships a SETUP.md that gives the order to do it in. How it works describes that first hour.

Second, two bots on one account see each other’s files. The security page is blunt about it: “Do not use separate Bots as a security boundary.” A template that reads a file another bot wrote must treat that file as untrusted input, because any bot on the account could have written it.

Third, the docs tell you what not to put in a template before you share it: “Remove API keys, internal URLs, customer data, and anything else you would not put in a public document.” The link is public and the docs do not describe a way to revoke it.

Is a share link the same as a duplicate?

Nearly. The docs describe two operations. Duplicating makes a copy inside your own account, named “<name> copy”, for the same role in a different scope. Sharing publishes a public link that lets someone else add a copy to their account. Both produce a bot with the profile, settings, skills and routines and without the history, memory or attachments. The difference is who ends up holding it.

For a buyer that means a template is exactly as good as the text inside it. There is no hidden state, no training, no learned behaviour riding along. What you can read in the preview on x.ai is what you get.

What does that mean for the price of one?

A persona costs twenty minutes to write, so it is free. Encoded judgment about what goes wrong in collections, or in a forecast, or in a vendor renewal, costs years to learn, and it is the part that only transfers if someone wrote it into a skill.

Every Botemplate bot is $20 and ships six documents of that judgment per role: the paste block, six to eight skills in xAI’s six-section shape, five to nine routines that each say what to do when a source is missing, a setup order, a file contract and acceptance tests to run on day one. The five together are $69 as the Operator Pack.