Prompt Library

Grok Bot roster prompts: specialists, not 12 clones

21 copy-paste prompts

Field pattern: named specialists plus an orchestrator. They can message each other and sit in a Channel. They still share one computer, so a second Bot is not a sandbox.

In short: This page contains 21 copy-paste ready prompts, organized into 5 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.

By Louis Corneloup · Founder, Techpresso

Last updated August 28, 2026·Hand-curated & tested by the AI Academy team

Design the roster

5 prompts

Four-Bot week

1/21

✨ What it does

The Bot designs a four-Bot roster for a [FOUNDER / SALES / ENG] week, with one job each and one group chat, sized to [N] review minutes a day. You create three of them, not twelve.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Design a 4-Bot roster for a [FOUNDER / SALES / ENG] week. One job each. One group chat. Sources: My tools [LIST], recurring work [LIST], review minutes per day [N]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not create the Bots until I pick. Remind me they share one computer. Deliverable: Table: name, job, inputs, output, approval, who they message. Review point: I create three, not twelve.

💡

Pro tip: Nate-style 12 Bots in eight hours is a demo. Four that you review is an operating system.

Webby / Shotry / Writey pattern

2/21

✨ What it does

The Bot turns [WORK STREAMS] into three specialists and one assigner, with verb names so you can tell who owns the last click. You name them and create them.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Translate my work into 3 specialists and 1 orchestrator with verbs for names. Sources: [WORK STREAMS]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not create them yet. Deliverable: Names, jobs, group-chat rules, never-do shared by all. Review point: I name them.

💡

Pro tip: Give them verbs for names if that helps you remember who owns the last click.

Per-account experts

3/21

✨ What it does

The Bot designs one chief of staff plus [N] account-expert Bots for [ACCOUNT LIST], and each expert refuses to talk about other accounts. You create one expert first.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Design one CoS plus [N] account-expert Bots for [ACCOUNT LIST]. Experts refuse other accounts. Sources: [STRATEGIC ACCOUNTS], [CRM]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not contact the accounts. Deliverable: Roster, refuse-list per expert, weekly output. Review point: I create one expert first.

💡

Pro tip: An expert Bot that will not talk about other accounts is the point.

Implement vs verify split

4/21

✨ What it does

The Bot splits [ENGINEERING WORK] into an implement Bot and a verify Bot, and neither of them merges. You create both.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Split [ENGINEERING WORK] into implement Bot and verify Bot. Neither merges. Sources: [REPO RULES], [TICKET]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Verifier must not be the implementer. Neither merges. Deliverable: Two Bot descriptions and the handoff note. Review point: I create both.

💡

Pro tip: If one Bot writes and approves, you shipped theater.

Do not hire a $200 desk by accident

5/21

✨ What it does

The Bot challenges the draft roster against [PLAN I AM ON]: what you will still do yourself, what usage it will burn, and what fails because every Bot shares one computer. You cut first, then create.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Challenge this roster: what I will still do myself, what usage it will burn, what fails if the computer is shared. Sources: The draft roster, [PLAN I AM ON]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not create Bots as a way to "use the seat". Deliverable: Keep / cut / merge, and a weekly review ritual. Review point: I cut first.

💡

Pro tip: Pricing moved. Do not hardcode $200. Check the plans page. Still ask what you will review.

Handoffs and group chat

4 prompts

Ownership handoff note

6/21

✨ What it does

The Bot hands [TASK] to [OTHER BOT] with context, a done definition, and an approval line, and they stop before send, merge, or pay. You read their result.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Hand [TASK] from this Bot to [OTHER BOT] with context, done-definition, and approval line. Sources: This thread, [FILES]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - They stop before [SEND / MERGE / PAY]. Deliverable: The note you sent and what you expect back. Review point: I read their result.

💡

Pro tip: You should not be the router. Official: they pass ownership so you are not.

Channel operating rules

7/21

✨ What it does

The Bot writes six short rules for Channel [NAME] with Bots [LIST] and you, capped at six Bots, for [ONE JOB THE CHANNEL EXISTS TO FINISH]. You paste the rules into the Channel topic.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write rules for Channel [NAME] with Bots [LIST] and me. Max 6 Bots. Sources: [ONE JOB THE CHANNEL EXISTS TO FINISH]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not add a seventh Bot. Do not @ everyone on every update. Deliverable: 6 rules: ownership, cadence, when to @ me, what stays out of the channel. Review point: I paste the rules in the Channel topic.

💡

Pro tip: A thread view that keeps main chat visible is still evolving. Keep rules short.

Standup the Bots run

8/21

✨ What it does

The Bot sets a weekday standup in [CHANNEL] where each Bot posts three bullets: done, blocked, need-human. You are the only one who assigns new work.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Each weekday, each Bot in [CHANNEL] posts 3 bullets: done, blocked, need-human. I am the only one who assigns new work. Sources: Channel, roster. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not start new work from the standup without me. Deliverable: Standup format and a routine per Bot or one orchestrator collect. Review point: I enable one collector, not six routines.

💡

Pro tip: Cap it. Twelve Bots each writing a paragraph is a usage bomb.

Conflict: two Bots, one file

9/21

✨ What it does

The Bot writes a file-ownership rule for [FOLDER] so only [BOT] writes and the others read. You paste that rule into both Bot descriptions.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Write a file-ownership rule for [FOLDER]. Only [BOT] writes. Others read. Sources: [FOLDER], roster. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not move the folder until I agree. Deliverable: Owner, naming, what to do on conflict. Review point: I paste it into both Bot descriptions.

💡

Pro tip: They share files. Two Bots editing the same deck is how you get a silent overwrite.

Installers and directories

4 prompts

Paste-in roster, then edit

10/21

✨ What it does

The Bot rewrites a public roster prompt [PASTE] for your tools, adds approval lines, and strips auto-send or mystery plugins. You create Bots one at a time from the edit.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Here is a public roster prompt: [PASTE]. Rewrite it for my tools and add approval lines. Do not create Bots yet. Sources: The pasted installer, my tools. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not run the installer as-is. Deliverable: Edited installer, what you removed (auto-send, prod, mystery plugins). Review point: I create Bots one at a time from the edit.

💡

Pro tip: One paste that creates 8 Bots will also create 8 routines you do not understand. Edit before enable.

Import a thread as a job

11/21

✨ What it does

The Bot turns a public job post [PASTE] into a Bot description for your computer and adds your never-do list. You create it only if it still fits.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Turn this public job post into a Bot description for my computer: [PASTE]. Add our never-do list. Sources: The post, our never-do. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not contact their customers or use their logins. Deliverable: Bot description, missing access, first safe task. Review point: I create it if it still fits.

💡

Pro tip: A verified run on someone else's computer is not a verified run on yours.

Kill the unused half

12/21

✨ What it does

The Bot audits Bots that have not been messaged in [14] days and recommends pause, merge, or delete later. You pause; it does not delete.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Audit Bots not messaged in [14] days. Recommend pause vs delete vs merge. Sources: Bot list, routine list. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not delete Bots. Deliverable: Keep / pause / merge / delete (later). Review point: I pause.

💡

Pro tip: Deleting a Bot deletes its routines. Pause first.

Grokularity warning

13/21

✨ What it does

The Bot rewrites a "company run by Bots" idea so a human still has to approve publish, pay, and legal. You start with three Bots, not a fake company.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Rewrite this "company run by Bots" idea so humans still approve publish, pay, and legal. Sources: The idea I paste. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not publish a site or take payment. Deliverable: Human gates, Bot jobs, first week roster of 3. Review point: I start with 3.

💡

Pro tip: Humans read. Only proven agents write. That sentence is the product.

Like these prompts? There are full tutorials behind them.

Learn the workflows, not just the prompts. 300+ easy-to-follow tutorials inside AI Academy — and growing every week.

Try AI Academy Free

Identity and badges

3 prompts

Names that state the job

14/21

✨ What it does

The Bot renames the roster so each name is a job a stranger would understand. You apply the names in the app.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Rename this roster so each name is a job a stranger would understand. Sources: Current names and jobs. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not rename in the app until I pick. Deliverable: Old → new, one-line job. Review point: I rename.

💡

Pro tip: Official create flow: short name, one primary job, how it should work.

Icons and mobile grouping

15/21

✨ What it does

The Bot assigns a distinct icon and notification name to each Bot so phone grouping is usable. You set the icons.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Assign a distinct icon and notification name to each Bot so iOS grouping is usable. Sources: Bot list, iOS app. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not change notification settings I did not name. Deliverable: Bot, icon, how it will look in a grouped notification. Review point: I set icons.

💡

Pro tip: If two Bots have the same icon, your phone is a slot machine.

I am the only admin

16/21

✨ What it does

The Bot writes a rule that only you create, delete, or enable routines, and that Bots may only propose. You paste that rule into every description.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Add a rule: only I create, delete, or enable routines. Bots may propose. Sources: Roster descriptions. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not create a Bot as part of this task. Deliverable: The rule text for every description. Review point: I paste it.

💡

Pro tip: Write it. A helpful orchestrator will "just create a fifth Bot".

Shared-computer reality

5 prompts

Same logins, say it out loud

17/21

✨ What it does

The Bot lists every login on this computer and which jobs it is too powerful for, because a second Bot is not a sandbox. You remove the worst logins.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: List every login on this computer and which jobs it is too powerful for. Recommend splits that are actually possible (they are not, unless I use another account). Sources: Browser sessions, plugins. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not log out of everything. Do not Reset. Deliverable: Login, risk, mitigate (approval / do-not-use / separate human account). Review point: I remove the worst logins.

💡

Pro tip: If the shopping Bot is logged into the bank, the intern Bot is too.

Too many computers

18/21

✨ What it does

The Bot helps you map Cursor devices that might be Grok Bot versus your laptop versus the cloud workspace, and will not log out of your laptop. You revoke the extras.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Help me list Cursor devices that might be Grok Bot vs my laptop vs the cloud workspace. Do not log out of my laptop. Sources: Cursor device list if visible, what I know. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not revoke my laptop session. Deliverable: Likely device map and what I should revoke if I have to. Review point: I revoke extras.

💡

Pro tip: If Cursor says too many computers, the Bot and the cloud workspace may be why.

Empty workspace after rebuild

19/21

✨ What it does

The Bot looks at what you see [PASTE] and tells you to quit and reopen instead of creating a new first Bot. You quit and reopen.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: If the workspace looks empty after a rebuild, do not create a new first Bot. Tell me to quit and reopen. Sources: What I see: [PASTE]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not create Bots. Do not Reset. Deliverable: Wait / quit-reopen / actually missing, with why. Review point: I quit and reopen.

💡

Pro tip: Quit and reopen. Do not create your first Bot in that window.

Farzad pattern: named specialists plus orchestrator

20/21

✨ What it does

The Bot designs [N] named specialists plus one assigner for [COMPANY TYPE], with one job each and a shared never-do footer. You create them.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Design a roster of [N] named specialists plus one orchestrator for [COMPANY TYPE]. One job each. Sources: My work: [LIST]. Tools: [LIST]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not create the Bots. I create them. Deliverable: Names, jobs, what the orchestrator may assign, never-do footer. Review point: I create them.

💡

Pro tip: The orchestrator assigns. It does not do the work. That is how context stays clean.

Twelve-job Gota audit

21/21

✨ What it does

The Bot audits roster [PASTE] and marks keep, merge, or pause by whether you reviewed an artifact last week. You pause the hobbies.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Audit this roster [PASTE]. Mark keep / merge / pause by whether I reviewed an artifact last week. Sources: The list, my notes: [WHAT I ACTUALLY OPENED]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not delete or pause Bots. Deliverable: Keep / merge / pause with a one-line reason. Review point: I pause.

💡

Pro tip: A Bot that has not produced a reviewed artifact in 7 days is a candidate to pause.

Free tool

Prompt Optimizer

Turn a rough idea into a structured, professional AI prompt.

Try it free →

Frequently Asked Questions

Grok Bot is an always-on AI teammate from xAI / SpaceXAI that runs on a persistent cloud computer (browser, files, terminal). You message it like a coworker and it finishes work inside the apps you already use. Grok on grok.com or in the X app is a chat assistant with live search and Grok Imagine. These pages are only for the teammate product. For chat and Imagine prompts, use the Grok prompts library.

Yes. Official docs are explicit: isolation is per user, not per Bot. Files, browser logins, and plugins on the computer are visible to every Bot on your account. Do not treat a second Bot as a security boundary. Put irreversible actions (send, pay, delete, production changes) behind approval.

Access has expanded since the August 2026 launch. It is included with SuperGrok plans and with Cursor Pro and Cursor Teams, plus a limited free trial for everyone else at times. Plans and weekly usage change. Check the official Grok Bot plans page before you buy a seat for this product.

Start with one focused Bot. Official create flow: short name, one primary job. Field cases that look like teams still use named specialists plus an orchestrator, not twelve clones. Every Bot shares the same computer, so adding Bots does not add isolation. It adds usage and confusion.

Yes. They can message each other, sit in group chats or Channels (a handful of Bots per named space), and pass ownership. You still approve send, pay, merge, and publish. Write a rule that only you create Bots and enable routines.

Prompts are the starting line. Tutorials are the finish.

A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.

Start 7-Day Free Trial AI training for teams

7-day free trial. Cancel anytime.

Browse All Prompt Collections

Popular prompt collections

AI Photo Editing Prompts ChatGPT Jailbreak Prompt Best ChatGPT Prompts Funny Hinge Prompts ChatGPT Caricature Prompts