Prompt Library

Grok Bot ops prompts for the work you keep putting off

21 copy-paste prompts

Field case: a shop owner handing office-manager work to a Bot in the first 24 hours. These briefs stay on drafts, lists, and unpublished CMS. You still sign and pay.

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.

Louis Corneloup
By Louis Corneloup · Founder, Techpresso
Last updated ·Hand-curated & tested by the AI Academy team

Office manager, day one

4 prompts

Inbox plus calendar plus invoices

1/21

✨ What it does

The Bot builds a first-day ops pack from [INBOX], [CALENDAR], and invoices due in [14] days, sorted into fire, wait, and ignore. You act on the fires.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: First-day ops pack: inbox fires, calendar conflicts, invoices due in [14] days. Do not pay or send. Sources: [INBOX], [CALENDAR], [AP]. 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 pay, send, or cancel anything. Deliverable: Fire / wait / ignore, with links and drafts. Review point: I act on fire.

💡

Pro tip: Jon-style plumbing-shop office manager. Cap the pack or day one is a novel.

Vendor list from the last 90 days

2/21

✨ What it does

The Bot lists vendors paid in the last [90] days, what they are for, the last amount, and any missing contract or tax form. You send the document requests.

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 vendors paid in [90] days, purpose, missing contract or tax form. Sources: [BANK OR AP], [INBOX], [FOLDER]. 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 email vendors. Do not pay. Deliverable: Vendor, purpose, last amount, missing docs, draft request. Review point: I send requests.

💡

Pro tip: You cannot manage vendors you have not named.

Subscription cancel list

3/21

✨ What it does

The Bot lists paid subscriptions it finds in [INBOX] and [STATEMENTS] over [90] days and flags the unused ones, without canceling anything. You click cancel.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Paid subs from [INBOX + CARD] in [90] days. Flag unused. Do not cancel. Sources: [INBOX], [STATEMENTS]. 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 cancel or chat with vendors. Deliverable: Keep / review / cancel recommendation. Review point: I cancel.

💡

Pro tip: Cancellations are irreversible enough.

SOP from a messy week

4/21

✨ What it does

The Bot turns this week's notes into a draft SOP for [PROCESS], with an owner and a definition of done. You publish it internally.

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 week's notes into an SOP for [PROCESS] with an owner and a definition of done. Sources: Notes I paste, [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 email the team the SOP. Deliverable: SOP draft, owner, exceptions. Review point: I publish internally.

💡

Pro tip: SOPs without owners are posters.

Prompts get you started. Tutorials level you up.

A growing library of 300+ hands-on AI tutorials. New tutorials added every week.

Start 7-Day Free Trial

CMS and site

4 prompts

Unpublished CMS draft

5/21

✨ What it does

The Bot creates an unpublished draft in [CMS] from [BRIEF] and [BRAND], and leaves the live pages alone. You hit publish.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Create an unpublished draft in [CMS] from [BRIEF]. Do not publish. Sources: [CMS], [BRIEF], [BRAND]. 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 or change live pages. Deliverable: Draft URL, diff vs brief. Review point: I publish.

💡

Pro tip: Teach a task after one good unpublished draft.

Broken links on the marketing site

6/21

✨ What it does

The Bot crawls [SITE] from [START URL] like a person clicking links and reports 404s and redirect chains. You assign the fixes.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Crawl [SITE] from [START URL]. Report 404s and redirect chains. Sources: Cloud browser. 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 edit the site. Deliverable: URL, issue, screenshot if visual. Review point: I assign fixes.

💡

Pro tip: Stay inside the domain. Do not submit the site to a third-party auditor as me.

Domain and DNS change plan

7/21

✨ What it does

The Bot writes a plan for DNS and redirect changes on [DOMAIN] toward [TARGET], including current versus proposed and a rollback. You apply the DNS yourself.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Plan DNS / redirect changes for [DOMAIN] to [TARGET]. Do not change DNS. Sources: [DNS HOST], [CURRENT RECORDS I PASTE OR YOU READ]. 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 edit DNS, nameservers, or registrar settings. Deliverable: Current vs proposed, rollback, risk. Review point: I apply.

💡

Pro tip: DNS is production. The Bot writes the plan. You apply it.

Status page draft

8/21

✨ What it does

The Bot drafts a status-page note for [INCIDENT] from [INCIDENT CHANNEL] and [MONITORING], with no invented arrival time. You publish the status.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft a status-page note for [INCIDENT]. No invented ETA. Do not publish. Sources: [INCIDENT CHANNEL], [MONITORING]. 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 the status page. Deliverable: Draft, what is unknown. Review point: I publish.

💡

Pro tip: No fake ETAs. Unknown is allowed.

People and vendors

4 prompts

Contractor quote pack

9/21

✨ What it does

The Bot collects quotes for [JOB], compares them to [MUST-HAVES] and [BUDGET], and recommends one without accepting it. You send the yes.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Collect quotes for [JOB]. Compare to [MUST-HAVES]. Recommend one. Do not accept. Sources: [INBOX], [RFPS], [BUDGET]. 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 accept or pay a deposit. Deliverable: Table, gaps, draft yes/no. Review point: I send the yes.

💡

Pro tip: Must-haves in the brief or it picks the pretty PDF.

Insurance or compliance reminder list

10/21

✨ What it does

The Bot lists insurance, licenses, and filings due in [90] days from [FOLDER], [CALENDAR], and [INBOX], and marks unknown when a date is missing. You file 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: List insurance, licenses, and filings due in [90] days. Unknown if no date. Sources: [FOLDER], [CALENDAR], [INBOX]. 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 file anything. Do not email the agency as me. Deliverable: Item, due or unknown, draft reminder to me. Review point: I file.

💡

Pro tip: If a date is missing, unknown. Do not invent a renewal.

Office supply or parts reorder draft

11/21

✨ What it does

The Bot reads [INBOX] and [INVENTORY] for what you are low on and drafts an order from [PREFERRED VENDOR] without placing it. You buy.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: From [INBOX + SHEET], what we are low on. Draft an order. Do not place it. Sources: [INBOX], [INVENTORY], [PREFERRED VENDOR]. 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 checkout. Hand me the computer at payment. Deliverable: Items, qty, vendor, cart URL if any. Review point: I buy.

💡

Pro tip: Hardware field cases exist. Ordering is still you.

Facilities or landlord thread

12/21

✨ What it does

The Bot drafts a note to [LANDLORD OR FACILITIES] about [ISSUE] from [LEASE OR THREAD] and any photos you attach, and will not accept charges. You send it.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft a note to [LANDLORD OR FACILITIES] about [ISSUE]. Do not send. Do not accept charges. Sources: [LEASE OR THREAD], photos I attach. 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 send. Do not pay. Deliverable: Draft and a do-not-accept list. Review point: I send.

💡

Pro tip: Do not let it accept a charge or a timeline.

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

Internal tools

3 prompts

Spreadsheet that actually reconciles

13/21

✨ What it does

The Bot rebuilds [TRACKER] from [SOURCES] for [PERIOD] into a new file and says whether the totals tie or where they gap. You replace the old sheet only if it ties.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Rebuild [TRACKER] from [SOURCES] for [PERIOD]. Totals must reconcile. If not, show the gap. Sources: [SHEET], [INBOX], [SYSTEM]. 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 email the sheet. Do not overwrite the only copy. Write a new file. Deliverable: New file path, reconciling yes/no, gap. Review point: I replace the old one if it ties.

💡

Pro tip: If it cannot tie, it says so. Pretty sheets that lie are anti-ops.

Access list: who has what

14/21

✨ What it does

The Bot reads [ACCESS EXPORT] against [OFFBOARD LIST] and lists people who still have [SYSTEM] after they should not, without revoking anyone. You revoke access.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: From [ACCESS EXPORT], list people who still have [SYSTEM] after [OFFBOARD DATE RULE]. Do not revoke. Sources: The export I attach, [OFFBOARD 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 revoke access. Do not store extra copies of the export. Deliverable: Name, system, last seen, revoke/keep/ask. Review point: I revoke.

💡

Pro tip: Shared computer. Do not dump the company password list into /workspace if you can avoid it.

Runbook drift

15/21

✨ What it does

The Bot compares [RUNBOOK] to the real [TOOL UI] for [PROCESS] and lists the drift with screenshots. You update the runbook.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Compare [RUNBOOK] to [TOOL UI] for [PROCESS]. List drift with screenshots. Sources: Runbook, tool in the browser. 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 edit the runbook or the tool. Deliverable: Step, doc vs UI, screenshot. Review point: I update the runbook.

💡

Pro tip: Same as eng docs drift. Ops runbooks rot faster.

Make the ops Bot durable

6 prompts

Ops Bot description

16/21

✨ What it does

The Bot writes an ops Bot description named [NAME] for [TOOLS], with never pay, never publish, never revoke access, and never change DNS. You create the Bot.

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 an ops Bot description named [NAME]. Sources: [TOOLS], [REVIEW TIME]. 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. - Never pay, publish, revoke access, or change DNS. Deliverable: Description and daily pack format. Review point: I create it.

💡

Pro tip: Office manager is a job, not a key to the bank.

Monday ops pack routine

17/21

✨ What it does

The Bot writes a Monday routine that packs invoices due, site issues, and vendor fires from [AP], [SITE], and [INBOX], without paying or publishing. You turn the routine on.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Mondays, ops pack: invoices due, site issues, vendor fires. Do not pay or publish. Sources: [AP], [SITE], [INBOX]. 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 pay or publish. Deliverable: Routine card. Review point: I enable.

💡

Pro tip: Fail closed if AP or the site is down.

What ops Bots never do

18/21

✨ What it does

The Bot writes a twelve-item list of things ops Bots must not do, including paying, changing DNS, revoking access, publishing live pages, and accepting legal terms. You paste that list on day one.

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 the never-do list for ops Bots. Sources: My rules. 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. Deliverable: 12 never-do items. Review point: I paste it.

💡

Pro tip: Paste this on day one, before the first 24 hours get exciting.

Plumbing-shop office manager, day one

19/21

✨ What it does

The Bot triages today from [INBOX], [PHONE LOG IF ANY], and [AP] into callbacks, invoices, and parts, with drafts of what you should say. You make the calls and you pay.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Triage today's office pile: callbacks, invoices, parts. Draft what I should say. Do not call or pay. Sources: [INBOX], [PHONE LOG IF ANY], [AP]. 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 call customers. Do not pay vendors. Do not post on the site. Deliverable: Three lists with drafts. Review point: I call and I pay.

💡

Pro tip: The first day is triage, not autonomy. Drafts only.

Domain and DNS stay with me

20/21

✨ What it does

The Bot proposes domain, DNS, and redirect steps for [CHANGE], screenshots the screens in [REGISTRAR] and [CLOUDFLARE], and stops before any click. You buy the domain and you point it.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Propose domain / DNS / redirect steps for [CHANGE]. Screenshot the screens. Do not buy or change DNS. Sources: [REGISTRAR], [CLOUDFLARE], [TARGET]. 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 buy a domain. Do not change DNS. Do not change Cloudflare settings. Deliverable: Step list, screenshots, rollback. Review point: I click.

💡

Pro tip: A wrong DNS click is a silent outage. Screenshots, then you click.

Cancel-subscription hunt

21/21

✨ What it does

The Bot finds subscriptions in [INBOX / CARDS] matching [QUERY], drafts the cancel steps, and hands you the computer at the last click. You cancel.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Find subscriptions in [INBOX / CARDS] matching [QUERY]. Draft cancel steps. Do not cancel. Sources: [INBOX], [CARD STATEMENTS], vendor sites. 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 cancel. Do not enter a card. Hand me the computer at the last click. Deliverable: Vendor, amount, cancel URL, last-click warning. Review point: I cancel.

💡

Pro tip: Retention pages lie. Screenshot the final cancel confirm, then hand you the computer.

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.
It can sign in and click like a person, and people have taught it CMS updates once as a skill. These prompts still leave publish, checkout, and DNS on your side. A taught skill that includes Publish is how a typo goes live at 2am.
Safe if it only builds packs: inbox fires, invoices due, vendor lists. Not safe if it can pay, cancel, or email landlords on its own. Write the never-do list before you hand it the inbox.

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.

7-day free trial. Cancel anytime.