How to share, install, and vet a Grok Bot template

A pasted prompt is a meal. A Grok Bot template is the recipe.

Someone already named a Bot, wrote its job, and published a https://x.ai/bot/… link. You add a copy to your account. Their chats, logins, and cloud computer stay behind. That is the point of a share link, and it is why this site lists live cards instead of dumping other people's prompts.

We are not xAI, SpaceXAI, or Cursor. We do not rehost configs. If you want the official Share a Bot steps, read Create and manage Bots. This page is the directory version: how to find one here, install it, decide if you trust it, and publish your own without leaking a secret.

A template is a recipe, not a meal

A prompt you paste into a chat is gone when the thread is gone. A template is a Bot someone else already shaped. Official docs call this sharing a Bot. You get a copy on your account. You do not get their conversation history, their computer, or their signed-in sessions.

Think of it as software you did not write. The recipe can look tidy and still do something you would never do yourself.

Browse the live catalog. If you want a 5–6 bot desk instead of one card, start from the agent team blueprints. For how a share id maps to a card, see Grok Bot templates: a public directory.

How to install one

You need the Grok Bot app to finish. The page on x.ai is only the look-before-you-leap step. Official docs say the recipient opens a preview and chooses Add to Grok Bot.

1. Pick a card on the templates list. Dewey is a simple Gmail watch. If you want a whole desk, open the one-person desk and install in the numbered order.
2. Use Open on x.ai. That button is the published https://x.ai/bot/… share link.
3. Read the preview before you add anything. Official docs say a public link exposes identity, description, skills, and routines. Product walkthroughs also show plugins (first-party integrations) on that page. Read those too.
4. Choose Add to Grok Bot. Confirm in the app. That creates a copy on your account.
5. Connect only the plugins that job needs. Installed connectors are account-wide, so a "just in case" Gmail login is a bigger gift than it looks.
6. Run one real task while you watch. A weekday brief. A read-only calendar scan. Not a send.

The official FAQ is at docs.x.ai/grok-bot/faq. For a roster with a fence you do not move, see Grok Bot agent teams.

Vet it before you trust it

This is the part most "how to add a bot" posts skip. The shared computer is the part people skip.

Treat the Bot as software you did not write. Shared Bots are created by other users, not by SpaceXAI. Adding one accepts the third-party bot terms. That is in the official Share a Bot docs, not a line we invented.

Then look at the computer. Every Bot on your account uses one persistent cloud computer. They share files, browser sessions, and logins. Official FAQ: do not use separate Bots as a security boundary. The new template can see what your other Bots already signed into.

Do not enable its routines on day one. Official guidance is to test a skill on a real one-time task before you automate it. Watch one safe, read-only task. If you would not let a new hire do it unattended, do not let a stranger's recipe do it on a timer.

Add your own line even if the author omitted it:

Never send, never spend, never publish without my yes.

Put that in the Bot description. Description is for rules that should stay true. Chat is for today's task.

How to share your own

Official path: open the Bot and copy its share link. Send that URL. The recipient previews it on x.ai and can add a copy. They need the app to finish.

Product walkthroughs also show a Share as template flow. Treat that UI name as reported, not as the docs heading. The docs heading is Share a Bot.

Inspect what ships before you send the link. Official docs: the public link exposes identity, description, skills, and routines. Walkthroughs also mention selected memories and first-party integrations. Those same walkthroughs say custom MCP servers, scripts, and code do not travel. The recipient rebuilds those and connects their own accounts.

Strip API keys, internal URLs, customer data, and project names. If you would not paste it into a public document, take it out.

Write setup notes for every plugin the other person must connect. "Needs Gmail, read-only" is useful. "It just works" is not.

The link is public. Anyone who has it can view the shared configuration.

FAQ

What is a Grok Bot template?

A Grok Bot template is a Bot someone already published with a public https://x.ai/bot/… share link. You add a copy to your own account. This site lists those live links. It does not paste prompt bodies.

Is sharing a template safe?

The link is public, not private. Official docs say it exposes identity, description, skills, and routines. Strip API keys, internal URLs, customer data, and project names before you copy it. Shared Bots are third-party, not SpaceXAI. Adding one accepts the third-party bot terms.

Does the recipient get my logins?

No. Adding a shared Bot creates a copy on their account. Official docs: it does not give them your computer, logins, or conversation history. They connect their own plugins.

Template vs prompt vs skill vs routine?

A pasted prompt is one meal in one chat. A template is the published Bot recipe: name, job, skills, routines. A skill is how to do a task. A routine is when one Bot runs that work, on a schedule or after an event. Official FAQ: test the skill on a real one-time task before you turn it into a routine.

Where do I find Grok Bot templates?

Here. Browse the public directory for live cards, or install a roster from agent team blueprints. We only list real x.ai share links.

Are you affiliated with xAI, SpaceXAI, or Cursor?

No. This is an independent public directory of share links. Official product docs live at Share a Bot and the Grok Bot FAQ.