Grok Bot Templates: How Sharing and Installation Work

An installable Grok Bot Template is a creator-published public link shaped like https://x.ai/bot/<id>. The link opens a preview, and an eligible user can choose Add to Grok Bot to create a copy on their own account.

Adding the Template does not give the recipient the creator’s cloud computer, logins, conversation history, or attachments. It copies the shared Bot configuration as a starting point.

Template and Use Case are not the same thing

Grokbotlist uses two labels because public evidence has two different strengths:

• Template: the creator published a verified x.ai/bot/<id> link.
• Use Case: a public post or guide documents the workflow, but no installable Template link is available.

For a Use Case, the directory can summarize the documented job and offer a clearly reconstructed prompt. It cannot claim to know the creator’s hidden configuration, private instructions, credentials, or files.

This distinction protects the reader from a common failure: treating any social post about a Bot as if it were an installable Template.

What a public share link exposes

A public link can expose the shared Bot’s identity, description, skills, and routines to anyone who receives it.

Before sharing your own Bot, remove anything you would not put in a public document:

• API keys or credentials;
• internal URLs;
• customer or employee data;
• private source-system names;
• confidential instructions;
• secrets embedded in a skill or routine.

A public link is not access control. Treat it as publishable information.

What does not transfer to the recipient

Adding a shared Bot creates a copy. The recipient does not receive the creator’s:

• signed-in browser sessions;
• cloud-computer files;
• conversation history;
• chat attachments;
• passwords or connector authorizations.

The recipient must connect the tools and provide the context needed for their own copy. That is why even an installable Template still needs setup and review.

How to evaluate a Template before adding it

Use a short evidence check:

1. Verify the destination. The install link should be on x.ai and follow the public Bot link shape.
2. Identify the creator. Open the original public source when it is available.
3. Read the job and boundaries. Know what the Bot is expected to access, produce, and change.
4. Inspect skills and routines. Remove or edit instructions that do not fit your environment.
5. Connect the minimum tools. A Template does not need every integration its creator used.
6. Test one task. Confirm the output and approvals before enabling recurring work.

Adding a third-party Bot means accepting the applicable third-party Bot terms. A template is a starting configuration, not an endorsement or proof that every integration is safe or available for your account.

How Grokbotlist verifies a Template

The directory’s editorial rule is deliberately narrow:

1. A credible public source must document the Bot or workflow.
2. The Template URL must be creator-published and use https://x.ai/bot/<id>.
3. The link must resolve to the intended Bot.
4. Grokbotlist links to the preview; it does not scrape, unpack, or rehost the configuration.
5. If the link is absent, invalid, or unrelated, the listing remains a Use Case.

You can inspect that provenance on each listing. For example, the LGTM and ChatPRD pages include installable Templates and their original public sources.

Compare verified Grok Bot Templates

These examples cover different jobs, but each listing includes both a creator-published x.ai/bot link and the public source used to verify it:

Template	Best fit	Tools named in the public workflow
LGTM	Pull-request triage, merge readiness, and CI follow-up	GitHub
ChatPRD	Product specs that stay aligned with meetings, issues, and shipped work	ChatPRD and GitHub
Vet	Review a public Grok Bot Template before installing or running it	Grok Bot

Open the listing before the Template link. It shows the documented job, setup sequence, integrations, and original source so you can decide whether the Bot matches your workflow before adding it.

Install a Template safely

After opening a verified Template:

1. Review the public preview.
2. Choose Add to Grok Bot.
3. Rename or rescope the copy for your actual job.
4. Remove tools, skills, or routines you do not need.
5. Connect accounts yourself.
6. State the approval boundary in the Bot description.
7. Run one bounded task before enabling routines.

If no verified link exists, copy the directory’s reconstruction as a draft and ask the Bot to walk through missing setup context. Do not assume the reconstructed prompt is the creator’s original prompt.

Browse verified Templates and documented Use Cases

Use the Grok Bot directory to compare the job, category, integrations, source, and install status. You can also browse category guides when you know the outcome you want, or use the directory landscape to compare the current mix of Templates and documented Use Cases. The difference between Template and Use Case matters more than the amount of promotional copy around a Bot.

Sources and verification

Checked on September 22, 2026 against xAI’s Create and manage Bots and Grok Bot FAQ documentation.

The Template-versus-Use-Case labels and verification method are Grokbotlist editorial policy, implemented in this site’s contribution rules.