Grok Bot Templates: How to Set Up a Persona as Your Bot (5 Examples)

Updated: November 2, 2026 · By Brian Arrington, AI consultant and business coach

The short answer

In Grok Bot, give each persona its own Bot. Paste the persona's Persona / System Prompt into your first message and ask the Bot to remember it as its lasting rules. Then connect the apps it lists and send its first task. Below are 5 ready-made examples built from BotPlaybooks personas.

A Bot with a vague job gives vague work back. The fix is a clear job, written once and kept as lasting rules. This guide shows you how to set that up, step by step, with five examples you can copy.

What a persona template gives your Bot

A BotPlaybooks persona is one plain Markdown file. It has a role, what you give it, what it gives back and the guardrails it must follow. In Grok Bot, the persona becomes the Bot's lasting rules, and your later messages carry the day's work.

Lasting rules (from the persona) A normal message
The job the Bot owns Today's task
Inputs it should expect The files or list for this task
What it hands back A deadline for this one task
Rules that stay true (approvals, never invent facts) One-time exceptions

A simple test: if you would want the rule next month, ask the Bot to remember it as a lasting rule. If it is only for today, just say it in chat.

How to set up a persona in Grok Bot

These are the same steps as our setup guide.

  1. Choose New Bot (+) at the top of the sidebar.
  2. Name it after the persona, then choose Create. One persona per Bot keeps each job clear.
  3. Paste the persona in your first message. Copy the persona's Persona / System Prompt section, paste it in, and ask the Bot to remember it as its lasting rules.
  4. Connect the apps the persona lists. Use Connect apps in the sidebar, and connect only the tools under the persona's Tools and Connectors.
  5. Send the persona's Example First Task. Review what comes back before you act on it.

If you bought a persona and need the download and unzip steps, see setup.

Good roles own a repeatable outcome, not a loose category of questions. Start with read-and-prepare work, review the result, then add more once you trust it.

5 Grok Bot persona examples

Each example below is written from the public details on the persona's page: its summary, tools, what you give it, what you get back and its guardrails. Paste it in your first message and ask the Bot to remember it as its lasting rules. Example tasks use bracketed placeholders for your own data. The full persona file has the complete Persona / System Prompt and its own Example First Task.

the agent called "Chief"

Good for a founder or leader who keeps dropping follow-ups between meetings.

You are my Chief of Staff. You own my operating rhythm: priorities,
meeting prep, follow-through and decisions.
I give you: my calendar, inbox (read), goals and OKRs, and meeting notes.
You give back: a daily brief, a decisions log, an action tracker and a
weekly summary.
Rules: Drafts only. Never send, post, pay or contact anyone without my
approval. Never invent facts. If something is missing, ask.

Then send the first task: "Act as my chief of staff this week. Start with tomorrow's brief."

The complete persona adds the workflow, output formats and routines: Chief of Staff persona.

the agent called "Scout"

Good for a seller or owner who needs better account research before outreach.

You are my SDR Prospect Researcher. You own account and contact research
for my target market.
I give you: my ideal customer profile, target companies and read access
to my CRM.
You give back: a prospect brief for each account with buying signals and
a suggested angle, plus a weekly ICP prospect list.
Sources: web search, company sites, news and LinkedIn (read only).
Rules: Drafts only. Never send, post, pay or contact anyone without my
approval. Never invent facts.

Then send the first task: "Research these 5 companies [list], find the likely buyer for [product], and give me a one-page brief on each with 2 personalized openers."

The complete persona adds the workflow, output formats and routines: SDR Prospect Researcher persona.

the agent called "Docket"

Good for anyone whose email, team chat and DMs pile up faster than they can read.

You are my Inbox Triage Assistant. You own sorting my email, team chat
and DMs into act, reply, read and archive.
I give you: inbox access, the chat channels and DMs I approve, my
priorities, my VIP list, and whether I want complete triage or the top 3.
You give back: in complete mode, a summary, a sorted list, draft replies and
tasks. In brief mode, only the top 3 urgent items with source links and
one next step each.
Rules: Drafts only. Never send, post, pay or contact anyone without my
approval. Never invent facts.

Then send the first task: "Triage my inbox and my Slack DMs from the last 24 hours, then give me just the top 3 urgent items."

The complete persona adds the workflow, output formats and routines: Inbox Triage Assistant persona.

the agent called "Helm"

Good for an owner who runs several Bots and wants one of them setting the week.

You are my CEO agent. You own strategy, weekly priorities and the
operating rhythm of the business, and you delegate work to my other
agent roles.
I give you: company vision and goals, current metrics, my team and agent
roster, my calendar and open decisions.
You give back: a Monday priorities memo, a delegation table (task, owner,
brief, due date) and a Friday review with a decisions-needed list.
Rules: Drafts only. Never send, post, pay or contact anyone without my
approval. Never invent facts.

Then send the first task: "Act as my CEO agent. Here are our quarterly goals [goals] and the agent roles I run [roster]. Set this week's priorities and delegate them."

The complete persona adds the workflow, output formats and routines: CEO persona.

the agent called "Book"

Good for anyone stuck in back-and-forth about meeting times.

You are my Scheduling Coordinator. You own finding meeting times,
drafting invites and protecting my focus blocks.
I give you: calendar access, the attendee list and my preferences.
You give back: 3 time options, a draft invite and a draft message.
Rules: Drafts only. Never send an invite, post, pay or contact anyone
without my approval. Never invent facts.

Then send the first task: "Find a 45-minute slot next week with these 4 people [names] across 3 time zones."

The complete persona adds the workflow, output formats and routines: Scheduling Coordinator persona.

Running several Bots as a team

Once one Bot works, it is tempting to make ten. Start with the smallest useful roster. Give one Bot ownership of an end-to-end outcome, add another only when a stable specialist role shows up, and keep anything sent, posted or paid behind your approval.

Here is how that looks with the examples above. The agent called "Helm" sets the week and assigns work. The agents called "Chief" and "Docket" report back, so you can see every handoff. Each one still drafts, and you still approve.

If you want a ready set of roles, see the Operations and Admin pack.

FAQ

What is a Grok Bot template?

Here, a template is a ready-made persona you load into a new Bot. It gives the Bot a clear job, inputs, outputs and guardrails, so you do not start from a blank chat.

Where do I put a persona in Grok Bot?

Give the persona its own Bot. Paste the Persona / System Prompt into your first message and ask the Bot to remember it as its lasting rules. Put task details, files and deadlines in later messages.

What should the lasting rules include?

The outcome the Bot owns, what you will give it, what it hands back and what it must never do without approval. Keep it to rules you would still want next month.

Can I change the rules later?

Yes. Tell the Bot in chat what to change and ask it to remember the new version as a lasting rule.

Should I make one Bot or several?

Make a separate Bot when the work has its own goal, its own tools, its own approval boundary or its own schedule. Start small, and add a Bot only when a stable specialist role shows up.

Do BotPlaybooks personas work in Grok Bot?

Yes. Every persona is one plain Markdown file. Create a Bot named after it, paste the Persona / System Prompt in your first message as lasting rules, connect the apps it lists and send its Example First Task.

Give your Bot a job

We add 3 new personas a month, and All-Access includes every persona, including the monthly new ones.

Every persona drafts. You approve anything sent, posted or paid.

Related guides: SOUL.md Templates for Business Agents. Grok Bot doesn't use a SOUL.md file; you paste the persona into your first message instead, and the same role and guardrail parts apply.

Which job will your first Bot own?

Sources

  1. BotPlaybooks setup guide: /setup#setup-grok-bot
  2. BotPlaybooks persona pages: /personas/chief-of-staff, /personas/sdr-prospect-researcher, /personas/inbox-triage-assistant, /personas/chief-executive-officer-ceo, /personas/scheduling-coordinator

AI can make mistakes. Always review outputs before acting. Personas are templates, not legal, financial, tax, medical or HR advice.

BotPlaybooks is independent and not affiliated with xAI, Meta, OpenAI, Nous Research, OpenClaw or any agent platform.

Brian Arrington is an AI consultant and business coach. He founded BotPlaybooks and Arrington Consulting LLC. He is an Air Force veteran and the 2025 Georgia Vetrepreneur of the Year.