Grok Bot prompts that hand off real work
Job briefs for an always-on teammate with a browser, files, and terminal. Create a Bot, give it a job, and make it stop for approval. This is not grok.com chat or Grok Imagine.
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.
First jobs that actually finish
6 promptsFive-minute first result (no login)
1/21✨ What it does
The Bot reads the file you attach and writes a short brief with dates, decisions, and open questions, citing the page or heading for each point. You stay signed out of every app and decide what to do with the brief.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: A five-bullet summary of the attached document, plus every date, decision, and open question. Sources: The file I attach in this conversation. No websites, no CRM, no email. 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 source file. Deliverable: Bullets, then a dated/decision/open-question section. Cite the page or heading for each item. Review point: Stop when the brief is ready. Do not file it anywhere.
Pro tip: Use this before you sign the Bot into anything. You learn the deliverable format with zero takeover.
Name a Bot that owns one job
2/21✨ What it does
The Bot turns your notes about [ROLE], [TOOLS I USE], and [WHAT MUST NEVER HAPPEN WITHOUT ME] into a named profile with one job and a never-do list. You paste the profile into Create your own and decide whether that Bot gets created.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: A Bot profile I can paste into Create your own: short name, one job, working style, approval line. Sources: My notes: [ROLE], [TOOLS I USE], [WHAT MUST NEVER HAPPEN WITHOUT ME]. 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: Name, one-sentence job, 8-line description, and a "never do" list of 5 items. Review point: Show the profile. Do not create a second Bot until I approve this one.
Pro tip: Focused Bots beat one catch-all. Official docs: name, one primary job, how it should work.
Hand off a multi-tool research job
3/21✨ What it does
The Bot researches [N] accounts from [CRM VIEW], skips anyone already in a sequence, and drafts email and LinkedIn in your voice. You review the table and send anything 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: Research [N] accounts from [CRM VIEW], skip anyone already in a sequence, draft email and LinkedIn in my voice. Sources: [CRM VIEW], company sites, [SLACK CHANNEL], [NOTES DOC], style examples 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. - Skip anyone already in an active sequence. Do not send or enroll anyone. Deliverable: A review table: account, why now, contacts (up to 3), draft email, draft LinkedIn, sources. Review point: Stop at the review table. Tomorrow morning is fine. Do not send.
Pro tip: Name the CRM view and the "already in sequence" rule or the Bot will redo work you already paid for.
Sign into a tool without pasting secrets
4/21✨ What it does
The Bot opens [APP OR URL] and walks up to the login screen, then hands you the computer for the password and 2FA. You type the secrets yourself and give control back when you are in.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Open [APP OR URL], reach the signed-in home screen, then confirm you can see [WHAT SUCCESS LOOKS LIKE]. Sources: [APP OR URL]. Use Settings → Plugins if a connector exists; otherwise use the 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. - Never ask me to paste a password, OTP, or API key into this chat. Use takeover or the secret card. Deliverable: A one-line status (signed in / blocked / need takeover) plus a screenshot of the home screen. Review point: If login is required, hand me the computer. Resume only after I return control.
Pro tip: Sessions persist on the shared computer. After one takeover, other Bots can use the same login.
Draw the approval line before any send
5/21✨ What it does
The Bot writes a standing policy for send, pay, delete, publish, and production changes, using your tools [LIST] and hard rules such as [E.G. NEVER EMAIL A CUSTOMER]. You paste the policy into the Bot description before any routine runs.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: A reusable approval policy for send, pay, delete, publish, and production changes. Sources: My current tools: [LIST]. My hard rules: [E.G. NEVER EMAIL A CUSTOMER]. 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: A 10-line policy I can paste into the Bot description, plus 4 examples of "stop and ask". Review point: Show the policy. Do not change any existing routines until I paste it.
Pro tip: Put this in the Bot description, not only in one chat. New threads forget informal rules.
Put the API key on the secret card
6/21✨ What it does
The Bot walks you through adding [SERVICE] credentials on the secret card, then runs [ONE READ-ONLY ACTION] to prove the key works without ever seeing the raw secret. You paste the key only into the card, never into chat.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Walk me through adding [SERVICE] credentials on the secret card, then confirm the Bot can call [ONE READ-ONLY ACTION] without seeing the raw key. Sources: [SERVICE], the secret card UI. I will paste the key only into the card, not here. 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 ask me to paste an API key, token, or password into this chat. If a key is already in a file on the computer, stop and tell me the path so I can move it. Deliverable: A 6-step secret-card checklist plus the one read-only test I should run after. Review point: I add the secret. You only confirm the test succeeded or failed.
Pro tip: If you paste a key into chat once, it is now in the transcript. Treat that as leaked and rotate.
Prompts get you started. Tutorials level you up.
A growing library of 300+ hands-on AI tutorials. New tutorials added every week.
Skills, routines, and the computer
4 promptsSave a successful run as a skill
7/21✨ What it does
The Bot writes up the process you just liked as a named skill called "[SKILL NAME]", including when to use it, the steps, and what still needs your approval. You test it on a second input before you hang any schedule on 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: Save the process we just used as a skill called "[SKILL NAME]". Sources: This conversation, the files we produced, and the apps we 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. - Include the rule that external contact always requires my approval. Deliverable: Skill name, when to use, required access, steps, output format, approval line, failure behavior. Review point: Show the skill draft. I will test it on a second input before any routine.
Pro tip: A useful skill states when, inputs, sequence, how to validate, what to return, and what needs approval.
Teach a workflow by demonstration
8/21✨ What it does
The Bot watches you complete [WORKFLOW] once on screen, with no microphone, and writes a skill another Bot could follow. You edit the draft and keep send, pay, or publish out of the recording.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Watch me complete [WORKFLOW] once, then write a skill that another Bot could follow. Sources: The computer view for this conversation. Target site or app: [NAME]. 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. - Teaching records the screen, not the microphone. Stop if a secret would appear on screen. Deliverable: A skill draft plus the steps you think you missed (decision rules, failures, approvals). Review point: I will edit the draft. Do not schedule it yet.
Pro tip: Do not type passwords during the recording. Use takeover for credentials, then resume the demo.
Schedule a weekday routine
9/21✨ What it does
The Bot prepares a weekday run at [08:00] [TIMEZONE] that runs [SKILL NAME] and posts the result here, including what to do if [INPUT LIST OR VIEW] is down. You enable it only after a test run looks right.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Every weekday at [08:00] [TIMEZONE], run [SKILL NAME] and post the result in this conversation. Sources: [INPUT LIST OR VIEW]. If the source is unavailable, report the failure. Do not reuse yesterday's data. 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. - A test run does real work. Use safe inputs. Keep writes behind approval. Deliverable: Routine summary, next run time, and a test-run checklist I can tick. Review point: Create the routine only after I say the test run looked right.
Pro tip: Confirm owner Bot, timezone, input, output, approval, and what to do when the source is down.
Pull a file back from the computer
10/21✨ What it does
The Bot finds [FILE OR FOLDER] from [JOB] on the shared computer, confirms it is the latest version, and stages it for download. You pull the file yourself; the Bot does not email it or Reset the computer.
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 [FILE OR FOLDER] from [JOB], confirm it is the latest version, and stage it for me to download. Sources: The shared Grok Bot computer filesystem. Job name: [NAME]. Approximate date: [DATE]. 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 Reset the computer. If you cannot find the file, list the likely folders instead. Deliverable: Path, modified time, size, and a one-line description of what is inside. Review point: Show the path. Wait for me to pull it. Do not email the file.
Pro tip: Chat history lives outside the box. Files live on the computer. Reset is last resort.
A small roster that does not collide
4 promptsPropose a 4-Bot starter roster
11/21✨ What it does
The Bot proposes four named Bots for a [FOUNDER / SALES / OPS] week, each with one job, plus a group chat and a review window of [E.G. 30 MIN AT 8AM]. You pick which ones to 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: A starter roster for a [FOUNDER / SALES / OPS] week: 4 Bots, one job each, one group chat. Sources: My tools: [LIST]. My weekly recurring work: [LIST]. Hours I can review: [E.G. 30 MIN AT 8AM]. 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. - Every Bot shares one computer. Do not pretend logins are isolated. Deliverable: Table: Bot name, job, inputs, output, approval line, who they message. Plus the group-chat purpose. Review point: Show the roster. Do not create the Bots until I pick which 3 to start with.
Pro tip: The pattern that keeps showing up in the field: named specialists plus a chief of staff, not 12 clones.
Hand work to another Bot
12/21✨ What it does
The Bot messages [BOT NAME] with the context, [FILES], and current status so they can finish [TASK] and stop before [SEND / PAY / MERGE / PUBLISH]. You mark the work done only after you read what came back.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Message [BOT NAME] with everything they need to finish [TASK], and take it off my plate. Sources: This thread, [FILES], and the current status: [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. - They must stop for my approval before [SEND / PAY / MERGE / PUBLISH]. Deliverable: The handoff note you sent, plus what you expect back and by when. Review point: After they reply, summarize in 5 bullets. Do not mark it done until I say so.
Pro tip: You should not be the router. Say who owns the next step and what they must return.
Write a group-chat operating note
13/21✨ What it does
The Bot writes operating rules for a group called [NAME] with Bots [LIST] and you, covering ownership, when to page you, and a daily standup. You edit the rules before anyone pastes them into the group.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Operating rules for a group called [NAME] with Bots [LIST] and me. Sources: The work this group exists to finish: [ONE SENTENCE]. 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: 6 rules: ownership, update cadence, when to @ me, what never happens in public, and a daily standup format. Review point: Paste the rules into the group only after I edit them.
Pro tip: A Channel can hold a handful of Bots. Broad "everyone reply to everything" burns weekly usage.
Marie Kondo the roster
14/21✨ What it does
The Bot audits your current Bots and routines and recommends what to keep, merge, pause, or delete, with one reason each. You pause or delete things yourself; deleting a routine has no undo.
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 my current Bots and routines. Recommend what to keep, merge, pause, or delete. Sources: The Bot list and routine list I paste or that you can see in the 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 delete a Bot or a routine. Deleting a routine has no undo. Deliverable: A keep / merge / pause / delete table with one reason each, and the usage risk of leaving them all on. Review point: I will pause things myself. You only recommend.
Pro tip: Deleting a Bot also deletes its routines. Pause first. Confirm. Then delete.
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.
Jobs from the field (approval-safe)
4 promptsOvernight sales research, drafts only
15/21✨ What it does
The Bot researches the [N] accounts in [CRM VIEW], scores them against your ICP, and drafts email and LinkedIn without sending. You send the ones you want.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Research the [N] accounts in [CRM VIEW]. Score against our ICP. Draft email and LinkedIn. Do not send. Sources: [CRM], [ICP DOC], company sites, [INTENT SOURCE IF ANY], style examples attached. 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. - Skip anyone already in a sequence. Deliverable: Ranked review list with evidence, contacts, and drafts. Review point: Stop at the list. I send.
Pro tip: After this is reliable, hang it on a nightly routine that still stops at the review list.
Inbox triage that waits before delete
16/21✨ What it does
The Bot walks [INBOX] for the last [N] days and sorts mail into delete, archive, and needs-me, with examples. You approve a bucket before anything is deleted or unsubscribed.
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 [INBOX] for the last [N] days. Propose delete / archive / needs-me. Do not delete. Sources: The signed-in inbox on the cloud computer. Filters: [E.G. NEWSLETTERS, RECEIPTS]. 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 delete, mark spam, or unsubscribe without my approval. Do not open mail that looks like credentials. Deliverable: Three buckets with counts and 10 examples each, plus anything that looks like money or legal. Review point: I approve a bucket, then you act on that bucket only.
Pro tip: Field case: 90,000-email purge. The unlock is the computer. The safety is the approval.
Meeting stand-in with a name tag
17/21✨ What it does
The Bot joins [MEETING LINK] at [TIME TZ] as [BOT NAME], announces it is taking notes, and brings back attendees, decisions, and what you owe. You send any follow-up 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: Join [MEETING LINK] at [TIME TZ] as a note-taker named [BOT NAME]. Announce yourself. Do not speak for me. Sources: [CALENDAR EVENT], [AGENDA DOC], [PRIOR NOTES]. 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 action items on my behalf. Do not share the recording or notes outside this conversation. Deliverable: Attendees, decisions, open questions, and anything I owe, each with a timestamp if you can. Review point: Post the notes here. I send any follow-up.
Pro tip: Tell it to announce that it is a Bot taking notes. Silent lurkers surprise people and burn trust.
Refund chase that never hits send alone
18/21✨ What it does
The Bot finds unrefunded returns from the last [N] days in [INBOX] and drafts one merchant note each, with the order and amount. You pick which drafts go out; the Bot never submits a refund on its own.
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 unrefunded returns or failed refunds from the last [N] days and draft one note per merchant. Sources: [INBOX], [ORDER CSV OR STRIPE], [RETURN POLICY]. 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 submit refunds, chargebacks, or merchant emails. Do not store card numbers in files. Deliverable: Table: merchant, order id, amount, evidence, draft message, confidence. Review point: I pick which drafts go out.
Pro tip: Same pattern as Stripe refund field cases: Bot hunts, human confirms, then money moves.
When the computer misbehaves
3 promptsDiagnose "can't reach your computer"
19/21✨ What it does
The Bot turns the error you paste, plus app version [X], [MAC/WINDOWS], VPN [YES/NO], and first-setup [YES/NO], into a ranked checklist: quit, DNS, VPN, then Reset last. You run the steps; the Bot does not Reset the computer.
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 debug a Grok Bot computer that will not connect. Collect symptoms, do not Reset unless I say so. Sources: What I see: [PASTE ERROR]. App version: [X]. OS: [MAC/WINDOWS]. VPN: [YES/NO]. First setup: [YES/NO]. 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 Reset the computer. Reset is last resort and can drop some local state (for example WhatsApp link sessions). Deliverable: A ranked checklist: quit/reopen, DNS, VPN, wait for host, then when Reset is actually justified. Review point: I run the steps. You only diagnose.
Pro tip: Staff notes: bad DNS for *.cursorvm.com can block the computer while the API still works. Try 1.1.1.1 before Reset.
Export before a Reset
20/21✨ What it does
The Bot lists what survives a computer Reset versus what dies, then stages exports for the jobs you name in [LIST]. You download the files, then you decide whether to Reset.
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 what I should export before any Reset, then stage those files for download. Sources: The computer filesystem and my Bot list. Jobs I care about: [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 Reset. Do not delete Bots. Deliverable: Keep vs lose table, plus paths of staged exports. Review point: I download, then I decide on Reset.
Pro tip: Staff: refresh keeps /workspace, the browser profile, and ~/.config. It does not keep ~/.local/state.
Usage that spilled into on-demand
21/21✨ What it does
The Bot looks at the routines you paste and your [SUPERGROK / CURSOR PRO / TEAMS] plan, then explains where this week's usage likely went and which routines to pause first. You pause things in the UI; the Bot does not buy more usage.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Explain where this week's usage likely went and which routines I should pause. Sources: My routine list and what I ran today: [PASTE]. Plan: [SUPERGROK / CURSOR PRO / TEAMS]. 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 routines or test runs. Do not buy anything. Deliverable: A pause-first list, then a lighter weekly roster that still covers [MUST-HAVE JOBS]. Review point: I pause things in the UI. You only recommend.
Pro tip: Grok Bot chat has a separate allowance from Cursor agents the Bot starts. Routines can keep running after 100%.
Free tool
Prompt Optimizer
Turn a rough idea into a structured, professional AI prompt.
Frequently Asked Questions
Is Grok worth paying for?
Read our honest, no-hype breakdown with the real pricing.
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.
Related guides