Prompt Library

Grok Bot routine prompts that run with the laptop closed

21 copy-paste prompts

A routine is when a skill runs. Confirm owner, timezone, input, output, approval, and failure. Test runs do real work. Broad "every Slack message" listeners burn usage.

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

Create and test

5 prompts

Weekday 8am job

1/21

✨ What it does

The Bot writes a weekday job that, every weekday at [08:00] [TZ], runs [SKILL] against [INPUT] and posts the result here, or reports failure if the source is down. You approve a test run, then you turn it 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: Every weekday at [08:00] [TZ], run [SKILL] against [INPUT]. Post the result here. Do not contact anyone. If the source is unavailable, report failure instead of using old data. Sources: [SKILL], [INPUT VIEW]. 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 enable until I approve a test run. Deliverable: Routine summary, next run, test-run checklist. Review point: I say go on the test, then I enable.

💡

Pro tip: Confirm owner Bot, schedule, timezone, input, result, approval, missing-source behavior.

Test run with safe inputs

2/21

✨ What it does

The Bot runs a test of routine [NAME] on [SAFE INPUT] and reports whether inputs were current, output quality, approval stops, and failure states. You turn it on only if all four pass.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Run a test of routine [NAME] on [SAFE INPUT]. Keep writes behind approval. Sources: The routine, [SAFE INPUT]. 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 use the production list for the test. Deliverable: Whether it picked current inputs, output quality, approval stops, failure states. Review point: I enable only if all four pass.

💡

Pro tip: Use yesterday's data or a sandbox view. Do not test on the live customer list.

Event trigger from Slack or GitHub

3/21

✨ What it does

The Bot writes a trigger so that when a message in [#channel] contains [TICKET LINK] and "[PHRASE]", it runs [SKILL] and posts here, without posting back to Slack unless you approve. You connect the integration if needed, then you turn it 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: When a message in [#channel] contains [TICKET LINK] and "[PHRASE]", run [SKILL] and post here. Never post back to Slack without approval. Sources: The event connection, [SKILL]. 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. - Avoid "every new message". Never post back without approval. Deliverable: Match rule, response, approval, what you will ignore. Review point: I connect the integration if needed, then I enable.

💡

Pro tip: Cursor account integrations can start a routine from an event. They are not the same as installing a Slack app.

Webhook routine (desktop URL)

4/21

✨ What it does

The Bot helps you set a webhook trigger for [SKILL] and tells you where the POST URL and sender key live on desktop, without putting the key in this chat. You store the key on the secret card.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Set up a webhook trigger for [SKILL]. Show the POST URL and sender key on desktop only. Do not put the key in this chat if it is a secret. Use the secret card. Sources: Desktop Grok Bot app, trigger card. 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 paste the sender key into Slack or a public gist. Deliverable: Where to find the URL, what payload you expect, test curl I can run. Review point: I store the key in the secret card.

💡

Pro tip: Open the trigger card on the desktop app. Keep the app updated.

50-routine budget

5/21

✨ What it does

The Bot lists this Bot's routines, which fired last, and which you should pause to stay well under 50. You pause the ones you name.

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 this Bot's routines, which fired last, and which I should pause to stay well under 50. Sources: View conversation details → Routines. 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 routine until I name it. Deliverable: Count, keep/pause, last run, last failure. Review point: I pause.

💡

Pro tip: If you are near 50, pause before you create. Deleting has no undo.

Manage and recover

4 prompts

Inspect recent failures

6/21

✨ What it does

The Bot inspects recent runs of [ROUTINE], says why it failed, and recommends edit, pause, or leave it. You edit 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: Inspect recent runs of [ROUTINE]. Tell me why it failed and whether to edit, pause, or leave it. Sources: Routine history (20 most recent). 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 the routine. Deleting is immediate and has no undo. Deliverable: Last 5 runs, failure reason, recommended edit. Review point: I edit.

💡

Pro tip: Open the Bot → conversation details → Routines. Read the last runs.

Pause while I am away

7/21

✨ What it does

The Bot writes an away policy: if you do not reply for [N] days, pause [THESE] and keep [THOSE], and post a note here. You confirm the policy.

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 I do not reply for [N] days, pause [THESE] and keep [THOSE]. Post a note here when you enter away mode. Sources: Routine list, [MUST-KEEP]. 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 pause until I confirm this policy. Deliverable: Keep/pause table and the away message. Review point: I confirm.

💡

Pro tip: Write the preference now so you are not guessing from a beach.

Timezone and daylight-saving check

8/21

✨ What it does

The Bot confirms timezone for routine [NAME] is [TZ] and shows the next three run times in your local time and UTC. You correct the timezone if it is wrong.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Confirm timezone for routine [NAME] is [TZ]. Show next three run times in my local time and UTC. Sources: The routine card, Settings. 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 timezone until I confirm. Deliverable: TZ, next three fires, DST note if relevant. Review point: I correct TZ if needed.

💡

Pro tip: Settings and notifications own timezone. Confirm it in the routine card.

Delete is forever

9/21

✨ What it does

The Bot exports the instructions and last good output for routine [NAME] before anyone deletes it, and lists what will vanish. You delete it only if you still want to.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Before deleting routine [NAME], export its instructions and last good output path. Sources: The routine, related skill. 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 yet. Deliverable: Exported instructions, last good output, what will vanish. Review point: I delete if I still want to.

💡

Pro tip: Pause first. Export the skill text. Then delete if you still want to.

Design for trust

4 prompts

Prepare, do not execute

10/21

✨ What it does

The Bot rewrites routine [NAME] so it only prepares (draft, reconcile, recommend) and marks send, pay, delete, or production as wait-for-me. You save 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: Rewrite routine [NAME] so it only prepares (draft, reconcile, recommend). Execution stays behind approval. Sources: The routine and skill. 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. - Remove any send/pay/delete/prod step from the automatic path. Deliverable: New routine text with the execution step marked "wait for me". Review point: I save it.

💡

Pro tip: The routine should produce a review list. Execution is a second, approved step.

Idempotent nightly job

11/21

✨ What it does

The Bot makes routine [NAME] safe to run twice on [UNIQUE KEY], so a second run updates instead of creating a duplicate. You test it twice.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Make routine [NAME] idempotent on [UNIQUE KEY]. A second run updates, it does not duplicate. Sources: The skill, the system it writes to (still behind approval). 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 new writes. Deliverable: The unique key and the guard. Review point: I test twice.

💡

Pro tip: Say what the unique key is (account id, invoice id).

Fail closed on stale data

12/21

✨ What it does

The Bot edits routine [NAME] so that if [SOURCE] is missing or older than [N HOURS], it posts a failure and stops instead of reusing yesterday. You save 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: If [SOURCE] is missing or older than [N HOURS], routine [NAME] must post a failure and stop. Sources: The routine, source freshness rule. 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 reuse prior output as if it were new. Deliverable: Failure message template and the freshness check. Review point: I save it.

💡

Pro tip: Routines love to "help" with yesterday. Write the fail message.

Usage spill warning

13/21

✨ What it does

The Bot lists routines likely to burn weekly usage (broad listeners, long crawls) and recommends caps or pauses. You pause the heavy ones.

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 routines likely to burn weekly usage (broad listeners, long crawls). Recommend caps or pauses. Sources: Routine list, what they 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 start test runs while we are near the cap. Deliverable: Heavy / light / pause-first. Review point: I pause the heavy ones.

💡

Pro tip: Users reported this. Pause heavy routines before the meter is a surprise bill.

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

Good routine ideas (still gated)

4 prompts

Nightly sales review list

14/21

✨ What it does

The Bot writes a nightly job that scores [CRM VIEW] against [ICP] and posts a review list, without sending or enrolling anyone. You turn it 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: Nightly, score [CRM VIEW], draft nothing extra, post the review list. Do not send. Sources: [CRM VIEW], [ICP]. 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 already-in-sequence. Do not enroll. Deliverable: Routine card. Review point: I enable.

💡

Pro tip: Only after the skill worked on a second input.

Monday CS watch list

15/21

✨ What it does

The Bot writes a Monday job that ranks a customer-success watch list for [PORTFOLIO] from CRM, usage, support, and billing, without contacting customers. You turn it 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, ranked watch list for [PORTFOLIO]. Do not contact customers. Sources: [CRM], [USAGE], [SUPPORT], [BILLING]. 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 CRM. Deliverable: Routine card. Review point: I enable.

💡

Pro tip: Thresholds in the skill. Failure if usage is stale.

Daily CoS digest

16/21

✨ What it does

The Bot writes a daily job at [08:00] [TZ] that posts a digest mapped to your priorities and does not send messages or move meetings. You turn it 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: Daily at [08:00] [TZ], priority-mapped digest. Do not send messages or change meetings. Sources: [SLACK], [INBOX], [CALENDAR], [PRIORITIES]. 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. - Only items that map to the priorities doc. Deliverable: Routine card. Review point: I enable.

💡

Pro tip: Map to the priorities doc or it is a firehose on a timer.

Health report, not auto-heal

17/21

✨ What it does

The Bot writes a weekday job that posts a health report for [SERVICE] from [DASHBOARDS] and does not restart anything or change alerts. You turn it 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: Weekdays, health report for [SERVICE] from [DASHBOARDS]. Do not change alerts or production. Sources: [DASHBOARDS]. 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 remediate. Deliverable: Routine card. Review point: I enable.

💡

Pro tip: If it can restart a service, the routine must not.

Triggers to avoid

4 prompts

Rewrite a noisy listener

18/21

✨ What it does

The Bot rewrites trigger [NAME] from "every message" to a narrow rule you can live with, plus five things it will now ignore. You save 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: Rewrite trigger [NAME] from "every message" to a narrow rule I can live with. Sources: The current trigger, examples of junk it fired 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 keep the broad rule as a fallback. Deliverable: New match rule and 5 things it will now ignore. Review point: I save it.

💡

Pro tip: Official: avoid broad listeners. They create noise, consume usage, and act on junk.

No routine that sends

19/21

✨ What it does

The Bot audits all routines for send, pay, delete, or production changes on the automatic path, and marks each safe, split, or pause-now. You split the dangerous ones.

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 all routines for send, pay, delete, or production changes in the automatic path. Sources: Routine list and their instructions. 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 until I pick one. Deliverable: Safe / split / pause-now. Review point: I split the dangerous ones.

💡

Pro tip: If you find one, split it: routine prepares, you execute.

iOS cannot show the webhook secret

20/21

✨ What it does

The Bot writes a five-line note that webhook setup is desktop-only and the phone can only watch runs. You save it in the Bot 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: Write a 5-line note I can keep: webhook setup is desktop-only, iOS can only watch runs. Sources: Official staff note. 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: The note. Review point: I save it in the Bot description.

💡

Pro tip: Staff: webhook URL and sender key only appear on desktop, not iOS.

Webhook trigger that stays desktop-only

21/21

✨ What it does

The Bot helps you set a webhook routine for [EVENT] that posts a draft here, and keeps the URL and sender key on desktop. You create the routine on desktop.

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 set a webhook routine for [EVENT] that posts a draft here. Do not fire test traffic at prod. Sources: [EVENT SOURCE], the routine trigger card on desktop. 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 paste the sender key into this chat. Do not hit a production webhook as a test. Deliverable: Trigger setup checklist and the draft format. Review point: I create the routine on desktop.

💡

Pro tip: If you cannot see the URL on the phone, that is expected. Open the trigger card on desktop.

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.

Yes. Background routines run on the cloud computer. Official docs say they can run while your laptop is closed. You still review results in the desktop app or the iOS companion. Test runs do real work, so use safe inputs.

Cursor account integrations can start a routine from an event such as a Slack message or a GitHub notification. That is not the same as installing Grok Bot as a Slack app. Define a narrow matching rule. "Every new message" is how you burn the weekly meter and act on noise.

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 tools for business

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