Prompt Library

Grok Bot engineering prompts that stop before production

21 copy-paste prompts

Official bug-reproduction and product-performance shape: reproduce in staging, return steps, screenshots, and links. Separate facts from hypotheses. Do not change alerts or production.

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

Reproduction packs

4 prompts

Staging repro from a ticket

1/21

✨ What it does

The Bot reads [TICKET], tries the bug on [STAGING URL] with a fresh test account, and returns exact steps, expected vs actual, and screenshots. You attach the pack to the ticket.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Read [TICKET]. Reproduce in staging with a fresh test account. Return exact steps, expected vs actual, screenshots, browser/OS, console or network notes, and a minimal case if possible. Do not use production customer data. Sources: [ISSUE TRACKER], [STAGING URL], browser and network tools on the computer. 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 production customer data. Do not change production. Credentials via secret card or takeover, not chat. Deliverable: Repro pack in the ticket format we use, plus screenshot paths. Review point: I attach it to the ticket.

💡

Pro tip: Hand test credentials through the secret card, not chat.

Cannot-repro is a result

2/21

✨ What it does

The Bot stops after [N] minutes if it cannot reproduce [TICKET] and writes what it tried, what differed, and what would help. You ask the reporter.

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 you cannot repro [TICKET] in [N] minutes, stop and write a cannot-repro pack. Sources: [TICKET], [STAGING], [LOGS YOU CAN ACCESS]. 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 retrying past the time box. Do not touch production. Deliverable: Tried, differed, missing info, suggested next question for the reporter. Review point: I ask the reporter.

💡

Pro tip: Force a cannot-repro template or the Bot will keep clicking until usage dies.

Flake bisect notes

3/21

✨ What it does

The Bot looks at flake [TEST OR JOB] from [CI LINKS], estimates how often it fails, and names one next experiment. You decide whether to run that experiment.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Investigate flake [TEST OR JOB] from [CI LINKS]. Estimate rate. Do not rerun CI in a loop. Sources: [CI], [REPO IF PERMITTED], [RECENT RUNS]. 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 merge, revert, or change CI config. Deliverable: Job, rate, last green, suspected area, next experiment (one). Review point: I decide the experiment.

💡

Pro tip: Ask for the exact job name and a link to two runs.

Slack "needs repro" listener (narrow)

4/21

✨ What it does

The Bot writes a trigger that, when a message in [#channel] has a ticket link and "needs repro", opens the ticket, reproduces it on staging, and posts the pack here. You turn the trigger on after a test; the Bot does not post back to Slack unless you approve.

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 a ticket link and "needs repro", open the ticket, repro in staging, post the pack here. Never post back to Slack without approval. Sources: [SLACK EVENT], [TRACKER], [STAGING]. 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 post back to Slack without approval. Never use prod customer data. Deliverable: Routine matching rule, response, approval line. Review point: I enable the trigger after a test.

💡

Pro tip: Avoid "every new message". Broad listeners burn usage and act on noise.

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

Incidents and performance

4 prompts

Latency investigation write-up

5/21

✨ What it does

The Bot investigates [CHECKOUT LATENCY / SYMPTOM] since [RELEASE], names the highest-confidence hotspot, and separates facts from guesses, with chart links. You change production if needed.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Investigate [CHECKOUT LATENCY / SYMPTOM] since [RELEASE]. Identify the highest-confidence hotspot. Separate facts from hypotheses. Do not change alerts or production settings. Sources: [OBSERVABILITY], [ANALYTICS], [INCIDENT TOOL], [COMMIT OR RELEASE LINK]. 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 alerts or production settings. Deliverable: Short write-up, screenshots, direct links, facts vs hypotheses. Review point: I change prod if needed.

💡

Pro tip: Highest-confidence hotspot first. A list of 20 charts is not an investigation.

Incident timeline from tools

6/21

✨ What it does

The Bot builds a timeline for [INCIDENT] between [START] and [END] from status, Slack, monitoring, and deploys, with a link on every event. You run the incident.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Build a timeline for [INCIDENT] between [START] and [END]. Sources: [STATUS], [SLACK INCIDENT], [MONITORING], [DEPLOYS]. 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 page people. Do not resolve the incident in the tool. Deliverable: Timestamp, event, source link, still-unknowns. Review point: I run the incident.

💡

Pro tip: Pin the incident window. Otherwise you get a history of the service.

Error-budget or SLO digest

7/21

✨ What it does

The Bot writes a weekly reliability digest for [SERVICES] with burn, breaches, and related deploys. You take it to the review.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Weekly SLO digest for [SERVICES]. Burn, breaches, related deploys. Sources: [SLO DASHBOARDS], [DEPLOYS], [INCIDENTS]. 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 SLO targets or alerts. Deliverable: Service, SLO, burn, related changes, links. Review point: I take it to the review.

💡

Pro tip: Name the SLOs. "How is reliability" is a vibe.

Postmortem first draft

8/21

✨ What it does

The Bot writes a first-draft postmortem for [INCIDENT] with facts, impact, and unknowns, and no blame. You edit it and you publish 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: First-draft postmortem for [INCIDENT] with facts, impact, unknowns. No blame. Sources: [TIMELINE], [TICKETS], [METRICS]. 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 postmortem. Do not name individuals as the cause. Deliverable: Draft in our template, plus a list of missing facts. Review point: I edit and I publish.

💡

Pro tip: Ban root-cause guesses unless sourced. First drafts that name a person are trash.

PRs and reviews

4 prompts

Review pack, not an approve

9/21

✨ What it does

The Bot writes a review pack for [PR URL] with a summary, risks, and test gaps. You review and you click approve or merge.

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 review pack for [PR URL]: summary, risks, test gaps. Do not approve or merge. Sources: [PR], [TICKET], [CI]. 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 approve, merge, or push. Deliverable: Summary, risk list, suggested tests, nits separately. Review point: I review and I click.

💡

Pro tip: Community profile packs split spec / repro / implement / verify so a Bot never approves itself.

Handoff PR from another Bot

10/21

✨ What it does

The Bot writes a handoff of [TICKET] to [IMPLEMENT BOT] and a test plan for [VERIFY BOT]. You merge if you agree.

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 [TICKET] to [IMPLEMENT BOT] and ask [VERIFY BOT] to write the test plan. I merge. Sources: [TICKET], [REPO 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. - Neither Bot may merge. Verifier may not be the implementer. Deliverable: Handoff notes and the verify plan. Review point: I merge if I agree.

💡

Pro tip: Say who implements and who verifies. Same Bot doing both is how junk lands on main.

Changelog from merged PRs

11/21

✨ What it does

The Bot drafts a changelog for [RANGE] from merged pull requests and skips internal-only work. You publish 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 changelog for [RANGE] from merged PRs. Skip internal-only. Sources: [REPO], [TICKETS], [LAST CHANGELOG]. 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 changelog. Deliverable: User-facing bullets, breaking changes flagged, PR links. Review point: I publish.

💡

Pro tip: Ask it to skip internal-only PRs. Users do not care that you renamed a var.

Dependency or CVE watch

12/21

✨ What it does

The Bot lists new security issues this week from [SBOM OR LOCKFILE] that you actually use, with a suggested action. You bump the library.

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 [SBOM OR LOCKFILE], list new CVEs this week that we actually use, with a suggested action. Sources: [LOCKFILE], [ADVISORY FEED], [REPO]. 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 bump dependencies or open PRs unless I ask. Deliverable: CVE, package, used-by, severity, suggested action. Review point: I bump.

💡

Pro tip: Cap it to dependencies we actually import. The full CVE firehose is noise.

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

On-call and chores

3 prompts

On-call morning scan

13/21

✨ What it does

The Bot scans [TEAM] for open incidents, noisy alerts, and silenced alerts older than [N] hours, with a suggested first action. You acknowledge the pages.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Morning on-call scan for [TEAM]: open incidents, noisy alerts, silenced alerts older than [N] hours. Sources: [PAGER], [MONITORING], [SLACK #incidents]. 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 ack, silence, or resolve alerts. Deliverable: List with links and a suggested first action for me. Review point: I ack.

💡

Pro tip: Do not let it acknowledge alerts. That hides pages from humans.

Staging data refresh notes

14/21

✨ What it does

The Bot reads [STAGING REFRESH RUNBOOK], lists steps that risk production customer data, and proposes a safer version. You run the refresh if it is safe.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Read [STAGING REFRESH RUNBOOK]. List steps that risk prod PII. Propose a safe version. Sources: [RUNBOOK], [STAGING], [DATA 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 run the refresh. Do not copy production customer data. Deliverable: Risky steps, safer alternative, questions for me. Review point: I run it if it is safe.

💡

Pro tip: If the runbook says "dump prod", stop and tell you. That is the point of the prompt.

Docs drift vs the product

15/21

✨ What it does

The Bot compares [DOCS URL] to [PRODUCT URL] for [FEATURE] and lists mismatches with screenshots. You file the doc 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: Compare [DOCS URL] to [PRODUCT URL] for [FEATURE]. List drift with screenshots. Sources: Cloud browser, [DOCS], [STAGING OR PROD READ-ONLY]. 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 docs or the product. Deliverable: Doc claim, product actual, screenshot paths. Review point: I file doc PRs.

💡

Pro tip: Computer use. No API. A screenshot of the mismatch is the deliverable.

Make the eng Bot durable

6 prompts

Repro Bot description

16/21

✨ What it does

The Bot writes a bug-reproduction description named [NAME] that stays on staging, uses the secret card for login, and never touches production data. 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 a bug-reproduction Bot description named [NAME]. Sources: [STAGING], [TRACKER], [TEST ACCOUNT VIA SECRETS]. 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 production customer data. Never change production settings. Deliverable: Description, pack format, never-do. Review point: I create the Bot.

💡

Pro tip: Piper-style official example: investigate, preserve links, never change production.

Health-report routine, not auto-remediate

17/21

✨ What it does

The Bot writes a weekday job that posts a health report for [SERVICE] from [DASHBOARDS] and changes nothing. 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, post a health report for [SERVICE] from [DASHBOARDS]. Do not change anything. Sources: [DASHBOARDS], [ERROR TRACKER]. 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 restart, scale, or change alerts. Deliverable: Routine card, report format, fail-closed if dashboards are down. Review point: I enable.

💡

Pro tip: If it can restart a box, it must not.

What eng Bots never do

18/21

✨ What it does

The Bot writes a never-do list for engineering Bots from your rules, such as [E.G. NO PROD, NO CUSTOMER DB, NO SELF-APPROVE], plus what a human does instead. You paste it into every engineering 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 the never-do list for engineering Bots on this computer. Sources: My rules: [E.G. NO PROD, NO CUSTOMER DB, NO SELF-APPROVE]. 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 and the human substitute. Review point: I paste it into every eng Bot.

💡

Pro tip: Paste this into implement and verify Bots alike.

PR that another Bot must not approve

19/21

✨ What it does

The Bot writes a handoff note from this reproduction pack to [IMPLEMENT BOT] and a separate verify checklist for [VERIFY BOT]. You are the only approver.

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 handoff note from this repro to [IMPLEMENT BOT] and a separate verify checklist for [VERIFY BOT]. I am the only approver. Sources: [REPRO PACK], [REPO]. 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 merge. Do not approve your own work. Do not push to production. Deliverable: Two notes: implement, verify. Review point: I assign the Bots.

💡

Pro tip: A Bot that writes the PR must not be the Bot that says ship.

Incident timeline from the computer

20/21

✨ What it does

The Bot builds a timeline for [INCIDENT] from [LOGS], [DEPLOYS], and [SLACK], facts only, and writes unknown when it cannot open a source. You write the postmortem.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Build a timeline for [INCIDENT] from [LOGS], [DEPLOYS], [SLACK]. Facts only. Sources: Those systems. Fail closed if a source is down. 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 page anyone. Do not restart services. Do not post to status. Deliverable: Timeline, unknowns, suggested next human check. Review point: I write the postmortem.

💡

Pro tip: If you cannot open the log, write unknown. Do not guess the blast radius.

Staging-only repro with secret-card login

21/21

✨ What it does

The Bot reproduces [TICKET] on [STAGING], screenshots the steps, and stays off production customer data. You file the bug or you fix 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: Repro [TICKET] on [STAGING]. Screenshot steps. Do not use prod customer data. Sources: [TICKET], [STAGING URL]. Secret-card or takeover for login. 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 touch production. Do not export customer data. Do not fix the bug yet. Deliverable: Steps, screenshots, pass/fail, env. Review point: I file or I fix.

💡

Pro tip: If staging needs a password, takeover. Never prod dumps in a screenshot.

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 use a browser, terminal, and plugins on its computer, and it can start Cursor agents that burn your Cursor usage. Official product-performance and bug-repro use cases still say: do not change production settings, do not use production customer data. These prompts return packs and write-ups. You change prod.

Staff have said a Grok Bot login is its own Cursor device, and the cloud workspace can count as a second one toward "too many computers". If you hit device limits, that is why. Agents the Bot starts also burn Cursor plan usage, separate from Grok Bot chat allowance.

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