Recipe

Write Grok Bot instructions

Put rules that should stay true in the bot's description. Put the task you want done now in the message. A useful task names the outcome, the sources, what to avoid, what to hand back, and when to stop for you. That split is how the Grok Bot docs separate a description from a conversation. The steps below follow those two pages.

Checked 16 Oct 2026. Each claim below links to the page it comes from.

1. 01

   Write the description as standing rules

   The bots page says to use the description for rules that should remain true, and the conversation for the task in front of you. A description can name the job, the sources, and a boundary such as never sending a message without approval.

   Create and manage Bots

2. 02

   Name one job

   The same page says a clear job has its own goal, tools, working style, approval boundary, or schedule. A catch-all job such as a general helper gives the bot less to reuse.

   Create and manage Bots

3. 03

   Put the task in the message

   Say what finished looks like, which files or apps matter, what it must not change, what it should hand back, and when it should stop. The get-started page lists those five parts as a strong request.

   Get started

4. 04

   Keep safety rules in the description

   The bots page says memory is not a substitute for an authoritative source, and that explicit safety boundaries belong in the bot description. Correct a stale assumption in the conversation when you see one.

   Create and manage Bots

5. 05

   Share only what you would publish

   If you later share the bot as a template, the bots page says a public link shows the identity, description, skills, and routines. Remove API keys, internal URLs, and customer data before you copy the link.

   Create and manage Bots

To do this on a new bot, start with create your first Grok Bot.