Skip the blank prompt box with free Grok Bot templates

GrokTemplates publishes free Grok Bot templates as plain text, so installing one means pasting a profile, saving a skill, and adding a routine that already has its schedule set.

A Grok Bot runs on a persistent cloud computer, so a routine set for 07:30 fires at 07:30 whether your laptop is open or shut. Every template on this site names its trigger, the source it reads and the place it writes, and every routine states what to do when it finds nothing. Change the times, the names and the channels to yours before the first run.

Hand-picked to install first

All templates

Browse by category

What is a Grok Bot template?

A Grok Bot template is a written profile, skill and routine that you paste into Grok Bot to create a named agent that runs on a schedule.

xAI defines a Bot as a single persistent, named agent. The Profile carries the name, description and avatar. The Skill holds reusable instructions the Bot calls by name. The Routine sets the trigger, either a clock time or an event. A template supplies the text for all three parts, so nothing is left for you to invent.

Open any category on this page and read the routine text before you install it.

How do I install a Grok Bot template?

You install a Grok Bot template by creating the Bot, pasting the profile under Bot actions then Edit Profile, saving the instructions as a skill, adding the routine, and running it once by hand.

Grok Bot stores the skill on the Bot, so the routine calls it by name on every run and you edit the wording in one place. An account holds up to 50 Bots and group chats combined, and each Bot owns up to 50 routines.

The install guide walks through every screen with the exact button names and ends with the share step.

Are Grok Bot templates free?

Every template on GrokTemplates is free to copy, with no account on this site and no payment for the text.

Running a template needs Grok Bot itself. xAI announced on 26 August 2026 that Grok Bot is included with all SuperGrok, Cursor Pro and Cursor Teams plans, and sign-in uses a Cursor account.

Copy the profile, the skill and the routine from any template page, then paste them into your own Bot.

How is a Grok Bot template different from a prompt?

A Grok Bot template keeps its instructions between runs and fires on its own schedule, while a prompt lives for one message and ends with the chat.

A Bot runs on a persistent cloud computer, so a routine set for Monday 08:00 fires while the app is closed. The app keeps the 20 most recent run records per routine, which means you can read what the Bot did on a day you never opened it. A prompt owns no schedule, no login and no run history.

Read the run records after the first week and tighten the skill wording wherever the output drifted.

FAQ

How many Grok Bots can I create on one account?

One account holds up to 50 Bots and group chats combined, and each Bot owns up to 50 routines. Delete an unused Bot before installing a new template once you hit the limit.

Do I need to keep the Grok app open for a routine to run?

No. A Grok Bot runs on a persistent cloud computer, so closing the app does not stop a routine, and a 06:30 brief lands with your laptop shut.

Can I share a Grok Bot I built from a template?

You share a Bot by public link. The recipient opens a preview on x.ai and chooses Add to Grok Bot, which creates a copy on their account. The link exposes identity, description, skills and routines, so put no API key in any of those fields.

Do separate Bots keep my logins separate?

No. The cloud computer is assigned per user, not per Bot, so a login placed on it is available to every Bot on the account. xAI states it plainly: do not use separate Bots as a security boundary.

What does a routine do when it finds nothing?

Grok Bot documents no default behaviour for an empty result, so the routine text has to state the no-data policy itself. Every template here writes it in as one line that reports nothing matched.

How do approvals work when a Bot wants to act?

Grok Bot takes three answers to a proposed action: Allow once, Deny and Always allow. A Require Approval rule beats an Always Allow rule when both match. An approval governs the action about to happen and does not reverse work already done.