Grok Bot templates: copy, share, and adapt them safely

Grok Bot templates are configured Bots shared publicly. A recipient can review the configuration on x.ai and add a separate copy to their own Grok Bot account.

This guide covers the six published examples in the original thread. Its seventh post is a request for additional submissions and does not contain another template.

What a template copies

xAI documentation calls the feature Share a Bot. A public preview can expose the Bot’s identity, description, skills, and routines. Adding it creates a separate copy under the recipient’s account.

The recipient does not receive the creator’s:

• Agent Computer
• Browser sessions or command-line credentials
• Conversation history, learned memory, or chat attachments
• Existing access to connected accounts

Adding a template therefore does not make it ready to run. Inspect the instructions, connect only the tools it needs, sign into services yourself, and validate one reversible task first.

A share link is public to anyone who has it. Remove API keys, internal URLs, customer data, private rules, and anything else that does not belong in a public document before sharing.

How to add and use a template

1. Open it from a traceable source

Prefer the creator’s post or a trusted directory. Confirm the author, the problem it is meant to solve, and the publication date before following the share link.

2. Review the x.ai preview

Inspect the Bot’s:

• Name and intended outcome
• Durable rules in its description
• Included skills
• Included routines
• Unknown links, vague permissions, or instructions that ask for secrets

Turn automatic sending, publishing, production changes, and physical-device control into draft, preview, or read-only behavior before the first run.

3. Choose Add to Grok Bot

The Grok Bot app is required to finish adding it. The result is your copy: renaming it or narrowing its scope does not change the creator’s Bot.

4. Rewrite the operating boundary

At minimum, define:

Scope: which project, city, channel, folder, or device may it touch?
Sources: which systems are authoritative?
Deliverable: which file, list, draft, or link should it return?
Approval: which sends, publishes, purchases, deletions, production changes, or physical actions must stop?

If the copy includes routines, review their schedule, timezone, inputs, and external actions. Do not enable a schedule before the one-time workflow passes.

5. Connect your own tools

The template does not carry the creator’s logins. Connect only necessary plugins or services, starting with read-only access. Take over the Agent Computer to sign in; never place a password or one-time code in the conversation.

6. Run a small acceptance task

Initial test message:

This Bot was added from a public template. Do not send, publish, purchase, delete,
change production, or control a physical device yet.

1. Summarize the problem you solve, your expected output, skills, routines, and required tools.
2. Identify every external write, sensitive-data path, and high-risk action.
3. List missing accounts, permissions, and inputs.
4. Propose one minimal, read-only task that I can verify in 15 minutes.

Wait for my confirmation before running it.

Review the artifact and its sources rather than accepting “done” as evidence. Check inputs, outputs, external actions, failure behavior, and rollback.

Six public examples

These uses come from public descriptions by community creators. Results depend on inputs, connected services, permissions, and the current configuration; this site has not run independent performance tests.

Case 1: Clip Bot — edit clips from long videos

The public description says the Bot accepts a YouTube link, identifies clips, and produces short videos for podcasts and other long-form content. Reported time savings have not been independently measured by this site.

Start with one short video and request candidate timestamps, selection reasons, draft captions, and preview files before allowing batch export.

Source: original post by @ThisWeeknAI; official x.ai preview.

Case 2: HouseBot — search and filter listings

Shared by shub, this Bot is summarized as a house hunter. A useful adaptation would take a city, budget, commute, property type, and hard constraints, then return a sourced shortlist.

Keep the first run to public research. Do not let it pay a deposit, submit an application, or send personal documents. Require timestamps, currencies, fee definitions, and explicit unknowns.

Source: original post by @shubgaur; official x.ai preview.

Case 3: Home Robots — control mowers, vacuums, and other devices

Sawyer’s Home Robots template is intended to control connected household devices from Grok Bot.

This is the highest-risk example in the set. Begin by reading device status and drafting an action plan. Physical movement, unlocking, blade activation, safety-zone changes, and actions that affect another person should require approval every time. Do not give the Bot an unrestricted household administrator account.

Source: Sawyer Merritt’s original post; official x.ai preview.

Case 4: Webby — website maintenance

Farzad’s Website Manager is described as automatically maintaining and updating a website. Narrow it to broken-link checks, dependency updates, stale content, build failures, and SEO metadata, then have it produce reviewable changes.

A staging environment or isolated branch is the safe starting point. Let it inspect and draft, but not change production DNS, billing, ads, secrets, or live content. Treat “the page loads” and “the change is safely deployed” as separate acceptance checks.

Source: original post by @farzyness; official x.ai preview.

Case 5: Sable: Game Art — generate and prepare game art

Danny describes a broader asset workflow:

• Generate 2D assets in a specified style
• Produce samples in several styles from a game idea
• Crop art into separate PNG assets
• Create 3D-model concept art, then work in Tripo or Meshy after the user signs in
• Remember personal preferences and a specific workflow

The creator also says style consistency is not perfect and sometimes requires regeneration or a request for lower detail. Establish one reference image first, generate small batches, and review them manually.

Source: Danny Limanseta’s original post and consistency note; official x.ai preview.

Case 6: Alfred — design and govern a Bot organization

Alfred audits and plans a set of Bots, skills, and routines, then recommends configuration changes.

The creator describes capabilities that include:

• Designing a Bot hierarchy and collaboration model from scratch
• Auditing existing Bots, skills, routines, owners, and handoffs
• Recommending which configurations to improve, merge, pause, or retire
• Running a safety check before a template is shared publicly
• Reviewing high-impact improvements, unused configurations, duplication, and collaboration patterns on a schedule

Use this class of Bot to produce advice and audit reports. It should not delete Bots, disable routines, or expand permissions without human approval.

Source: Robin’s Alfred post; official x.ai preview.

Case count

The seventh thread post asks readers to contribute examples, so this guide includes the six published templates.

Share your own template

After a Bot has been tested, use its sharing action to copy a public link. Reinspect the identity, description, skills, and routines first, and remove internal URLs, customer names, secrets, private prompts, and automation that is unsafe outside your environment.

A useful share page should explain:

• What the Bot does and does not do
• Required tools or accounts
• A safe first test task
• Actions that always require approval
• Known limitations and rollback
• Creator, publication date, and last verification date

A public template should provide a tested, reviewable configuration with documented use, inputs, outputs, limitations, and approval requirements.

Sources and verification

Last verified: August 29, 2026.

• Create and manage Bots: duplicate and share (xAI)
• Approvals, security, and privacy (xAI)
• Grok Bot template example thread (Dan)