Templates
Grok Bot templates
A Grok Bot template is a shareable blueprint—identity, instructions, skills, routines, and plugin *configuration*—not a prompt dump. You share or install it in the app; recipients reconnect their own logins and run a safe first task before any routine. This unofficial Plays guide shows the mechanism plus curated public examples. Not affiliated with xAI (about).
If you have not run a first bot yet, start with How to use Grok Bot. For sales and engineering loops built on those blueprints, see use cases. Browse more cards on the home page, Crew, and Official.
What a Grok Bot template is
A template packages the shape of a seat:
- Who the bot is (name, title, description / instructions)
- Skills and routines you already taught
- Which plugins the blueprint *expects* (not your live OAuth sessions)
- Optional memory or inclusions the sharer chose to keep
It is not “copy this paragraph into ChatGPT.” A prompt library moves text. A template moves an operating configuration so someone else can recreate a similar bot and then bind it to *their* accounts.
What usually does not travel: the sender’s passwords, active sessions, private mailbox contents, and often custom MCP servers or one-off scripts that lived only on the original computer. Treat the template as a starting blueprint; treat reconnect + review as mandatory install steps.
How to share your bot as a template
Exact click paths live in the app—look for Share / Share as template (or ask the bot to prepare a shareable copy if that flow is available in your build). Before you publish a link:
- 01 Strip secrets
API keys, internal URLs, customer lists, and private memory that should never leave your desk.
- 02 Review inclusions
skills, routines, and plugin *settings* you intend others to see; remove anything that only makes sense on your machine.
- 03 Write a recipient brief
one paragraph on the job, what they must reconnect, and the first safe task to run.
- 04 Prefer reversible checks
share after you have run the job yourself and would sign the method.
Community Plays below show how operators pack templates beyond a private desk. Align with those practices; do not invent menu trees this page cannot verify.
How to install someone else’s template
- 01
Open the share link in the product (or the install surface the link opens).
- 02 Inspect inclusions
instructions, skills, routines, expected plugins—before you accept.
- 03 Reconnect plugins with your own logins
in Plugins settings. You do not inherit the author’s sessions.
- 04
Run a safe first task with send/spend/merge still parked. Confirm the deliverable shape.
- 05
Only then enable or create a routine, with timezone and failure behavior you own.
If anything in the description asks for broad send rights on day one, narrow it. Templates accelerate setup; they do not replace the operator path on How to use Grok Bot.
Template pitfalls
Mark these as third-party observations from public posts and field notes—not guaranteed product bugs, and not a substitute for what you see in the app today:
- Long descriptions may truncate when packed into a template (community reports). Keep the critical contract short; put long lore in a linked doc the recipient controls.
- Custom MCP servers, local scripts, and one-off computer state often do not travel. Recipients must reinstall or recreate those pieces.
- Plugin config ≠ authenticated access. Installers still OAuth with their own accounts.
- Routines that send or write are dangerous to enable before a dry run. Keep the first pass at draft → human sends (or human merges).
When product behavior disagrees with a community post, trust the app and official docs.
Template Plays to copy from
Curated deep-links only (≤7). Each line states the template-related action—share, install, or review—not a generic highlight reel.
You can now share templates of your Bots with others.
**Share:** official note that you can share a Bot template so others add that configuration to their own Grok Bot.
I used to keep every Bot locked to my desk. Sharp for me. Dead weight for anyone who needed the same lane later.
**Share / review:** packing rules for templates that leave your desk without dragging private weight.
You can now turn a workflow you’ve refined inside Grok Bot into a template and share it with others.
**Share:** publish a refined workflow (instructions, memories, skills, routines, plugins) as a template.
Grok Bot templates are the first widely available way to share knowledge work
**Share / install:** template as skills, memories, and plugins—with share, publish, install, and setup covered in the open post/video.
Grok Bot can ship a Bot as a link now.
**Share / review:** ship a bot as a link—preview, reversible task, then routine—and what actually travels.
botify shareable Grok Bot templates
**Review / install:** community field case of shareable Grok Bot templates outside the default catalog.
Bring your @bot with this template
**Share / install:** a shareable template pattern for bringing a bot along into a new thread.
FAQ
What is in a Grok Bot template?
Typically the bot’s identity and instructions, selected skills and routines, and plugin *configuration*—a blueprint of the seat. It is not a bag of one-liner prompts. Logins, live sessions, and many custom computer-only pieces stay with the author unless you rebuild them after install.
How do I share a Grok Bot as a template?
In the app, use Share as template (or the share flow your build shows). Strip secrets and private memory first, check inclusions, and attach a short recipient brief. Prefer sharing after you have run the job yourself. See the Share Plays above for public examples of packing and shipping links.
Will the recipient get my logins?
No. Recipients reconnect plugins with their own accounts and OAuth. Your live sessions, passwords, and mailbox contents do not travel with the template. Treat claims that “sessions transfer automatically” as false unless the product explicitly shows that—and rotate anything sensitive before you share a blueprint anyway.
Templates vs prompt libraries?
Prompt libraries move text you paste into a chat. Templates move an agent configuration meant to become a bot on someone else’s account. Installers still reconnect tools, run a safe first task, and decide when routines may run. Use templates when the seat—not just the wording—is the asset.