Prompt Library

Grok Bot research prompts that cite or shut up

21 copy-paste prompts

The Bot has a live browser and can keep going overnight. These briefs demand sources, rumor vs fact, and a stop when the source is missing. Not grok.com chat, not 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.

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

Daily briefs

4 prompts

Overnight topic brief

1/21

✨ What it does

The Bot writes a brief on what changed about [TOPIC] since [YESTERDAY 17:00 TZ], split into confirmed, disputed, and rumor, each with a link. You decide what is worth acting 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: Brief [TOPIC] since [YESTERDAY 17:00 TZ]. Separate confirmed, disputed, and rumor. Cite each item. Sources: Live web and X in the cloud browser, [MUST-READ URLS]. 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 invent citations. If you cannot open a source, say so. Deliverable: Confirmed / disputed / rumor, links, 5-bullet TL;DR. Review point: I decide what to act on.

💡

Pro tip: Sid-style settlement brief: the day's closed facts, not a vibes thread.

Market or category scan

2/21

✨ What it does

The Bot scans [CATEGORY] for the last [14] days and lists launches, price changes, and shutdowns with a date and a link on every row. You pick which ones to follow up.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Scan [CATEGORY] for the last [14] days: launches, pricing changes, shutdowns. Date every claim. Sources: Vendor sites, changelogs, X, [TRADE PRESS]. 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. - No KD or traffic numbers unless you can see them. Otherwise unknown. Deliverable: Table: who, what, date, link. Review point: I pick follow-ups.

💡

Pro tip: Ask for dates on every claim. "Recently" is not a source.

Regulation or policy watch

3/21

✨ What it does

The Bot lists what actually published in [POLICY AREA] since [DATE], putting official documents first and blogs in a second pile. You send it to counsel if it matters.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: What changed in [POLICY AREA] since [DATE]. Primary sources first. Sources: [GOV OR STANDARDS URLS], press only as secondary. 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. - This is not legal advice. Do not email counsel as me. Deliverable: Change, primary link, what it might mean (labeled guess), questions for counsel. Review point: I send to counsel if needed.

💡

Pro tip: Prefer primary docs. Secondary blogs go in a separate bucket.

Fail closed if the web is thin

4/21

✨ What it does

The Bot either writes a sourced brief on [TOPIC] or, if it finds fewer than [N] independent sources, returns a short thin-sources note listing what it tried. You widen the question or you drop 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 you find fewer than [N] independent sources on [TOPIC], return a short "thin sources" note instead of a long brief. Sources: Live web. 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 pad with generic background. Deliverable: Either a sourced brief or a thin-sources note listing what you tried. Review point: I widen the question or I drop it.

💡

Pro tip: A 12-page brief on three blog posts is fiction.

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

Competitive and accounts

4 prompts

Competitor teardown with screenshots

5/21

✨ What it does

The Bot opens the [COMPETITOR] site for [FEATURE OR LAUNCH], screenshots the claims, and sorts them into facts, marketing, and rumor. You decide whether to respond.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Tear down [COMPETITOR] [FEATURE OR LAUNCH]. Screenshot claims. Facts vs marketing vs rumor. Sources: Their site, changelog, X, [REVIEWS]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not contact them. Do not create an account with my real email unless I provide a test login. Deliverable: Claims, screenshots, gaps, links. Review point: I decide if we respond.

💡

Pro tip: Screenshot the claim. Paraphrase without a picture is how you misquote.

Account research pack

6/21

✨ What it does

The Bot builds a research pack on [ACCOUNT] from the company site, [CRM], and recent news, and labels anything it cannot source. You decide whether to pursue the account.

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 [ACCOUNT]. Business, people, recent news, likely pain vs [OUR OFFER]. Do not contact anyone. Sources: Company site, [CRM], news, [LINKEDIN IF APPROVED]. 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 them. No fake personalization hooks. Deliverable: Pack with sources. Unknowns labeled. Review point: I decide to pursue.

💡

Pro tip: Skip already-in-sequence if you have CRM. Do not invent contacts.

Win/loss secondary research

7/21

✨ What it does

The Bot collects what public sources said you won or lost on after [DEAL OR LAUNCH], with a quote and a link for each theme. You take those themes to product or sales.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: After [DEAL OR LAUNCH], what did public sources say we won or lost on? Sources: Reviews, X, press, [CALL NOTES IF 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 email the customer. Deliverable: Theme, quote, source, confidence. Review point: I take it to product or sales.

💡

Pro tip: Customer quotes need a source. "People say" is out.

Pricing page archive

8/21

✨ What it does

The Bot captures the [COMPETITOR] pricing page as it looks today and stores dated screenshots of the visible plans. You file the pack.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Capture [COMPETITOR] pricing page as of today. Store dated screenshots. Do not create a fake account to see hidden prices unless I provide a test login. Sources: The pricing URL. 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 violate the site terms to see logged-in prices. Deliverable: Path, date, visible plans, caveats (logged-out only?). Review point: I file it.

💡

Pro tip: Date the file names. Memory of "they were $99" is useless in a quarter.

Diligence and docs

4 prompts

Document to cited brief

9/21

✨ What it does

The Bot summarizes the attached document in five bullets and lists every date, decision, and open question with a page or heading cite. You use that brief in the meeting.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Summarize the attached document in 5 bullets. List every date, decision, and open question with a page or heading cite. Do not change the file. Sources: The attached file 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 fetch extra web context unless I ask. Deliverable: Bullets plus cited lists. Review point: I use it in the meeting.

💡

Pro tip: Attach the file. "This PDF" without a file is a stall.

Conflict between two docs

10/21

✨ What it does

The Bot compares [DOC A] and [DOC B] on [QUESTION] and lists the conflicts, without picking a winner unless the newer file clearly replaces the older one. You decide which document wins.

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 [DOC A] and [DOC B] on [QUESTION]. List conflicts. Do not pick a winner unless the newer doc explicitly supersedes. Sources: The two files. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not edit either file. Deliverable: Conflict table, cites, open questions. Review point: I decide.

💡

Pro tip: Same rule as finance packs.

Vendor diligence checklist

11/21

✨ What it does

The Bot fills a public diligence checklist on [VENDOR] from their trust center and security pages, and leaves unknown on anything they do not publish. You send the leftover questions to their sales team.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Public diligence on [VENDOR]: data location, subprocessors, certs they actually publish. Sources: Trust center, DPA, security page. 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. - Not legal advice. Do not email the vendor as me. Deliverable: Checklist, links, unknowns, questions for their sales. Review point: I send questions.

💡

Pro tip: If it is not public, the cell is unknown. Do not invent SOC2.

Podcast or talk to a brief

12/21

✨ What it does

The Bot turns [URL OR FILE] into a brief with a five-bullet summary and timestamped claims you can check against [SHOW NOTES]. You share it only if you 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: From [URL OR FILE], brief with timestamped claims and a 5-bullet TL;DR. Sources: The file or URL, [SHOW 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 publish a recap as me. Deliverable: TL;DR, timestamped claims, quotes to verify. Review point: I share if I want.

💡

Pro tip: Timestamps. A summary without times is a vibes machine.

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

Live web and X

4 prompts

X conversation map

13/21

✨ What it does

The Bot maps the current X conversation on [TOPIC], listing viewpoints, traction, and what people get wrong, with links to the posts. You decide whether to speak.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Map the X conversation on [TOPIC] right now. Viewpoints, traction, what people get wrong. Neutral bullets. Cite posts. Sources: X in the browser. If the official X plugin is connected-but-empty, use 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 post. Do not quote-tweet as me. Deliverable: Viewpoints, example posts, rumor flags. Review point: I decide whether to speak.

💡

Pro tip: This is Grok Bot using a browser, not the grok.com "summarize X" chat. Still ask for wrongness, not a dunk thread.

Fact-check one claim

14/21

✨ What it does

The Bot fact-checks [CLAIM] and returns a verdict plus the strongest evidence on each side, with links. You use the verdict or you drop the claim.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Fact-check: [CLAIM]. Verdict plus strongest evidence on each side. Links. Sources: Live web. Primary > secondary. 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 post the verdict. Deliverable: Verdict, evidence table, leftover doubt. Review point: I use it or I drop it.

💡

Pro tip: Unverified is a valid answer. Force both-sides evidence.

Primary-source hunt

15/21

✨ What it does

The Bot hunts for the original filing, spec, or PDF behind [CLAIM], and if it cannot find one it lists the best secondary source and the gap. You open the primary 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: Find the primary source for [CLAIM]. If you cannot, list the best secondary and the gap. Sources: Web, official domains I name: [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 pay a paywall with my card. Deliverable: Primary URL or gap, plus how you searched. Review point: I open it.

💡

Pro tip: If you only find blogs, say so.

Image or screenshot as evidence

16/21

✨ What it does

The Bot screenshots [URL] as it looks right now, saves it with the date in the filename, and notes anything that looks dynamic or location-specific. You file the image.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Screenshot [URL] as of now. Store it with date in the filename. Note anything that looks dynamic or geo-specific. Sources: The URL in 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. - Do not log in unless I take over. Deliverable: Path, datetime, caveats. Review point: I file it.

💡

Pro tip: Date the file. Tomorrow the page will change.

Make the research Bot durable

5 prompts

Research Bot description

17/21

✨ What it does

The Bot writes a research Bot description named [NAME] covering [BEAT], [MUST-READ URLS], and the rule that unknown is allowed. 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 research Bot description named [NAME]. Sources: [BEAT], [MUST-READ URLS], [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 post. Never invent citations. Never paywalls with my card. Deliverable: Description and brief format. Review point: I create it.

💡

Pro tip: Write "unknown is a valid cell" in the description.

Morning brief routine

18/21

✨ What it does

The Bot writes a weekday routine that briefs [BEAT] at [07:30] [TZ] and stops with a short note if sources are thin or the web is unreachable. 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: Weekdays at [07:30] [TZ], brief [BEAT] since yesterday. Thin-sources rule on. Do not post publicly. Sources: Live web, [MUST-READS]. If the web is unreachable, fail closed. 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 yesterday's brief as new. Deliverable: Routine card. Review point: I enable.

💡

Pro tip: Thin-sources rule in the routine, not only the skill.

What research Bots never do

19/21

✨ What it does

The Bot writes a twelve-item list of things research Bots must not do, including fake citations, paid paywalls, posting, and contacting the people they researched. You paste that list into 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 the never-do list for research 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. Research Bots want to be helpful more than they want to be right.

YouTube researcher with timestamps

20/21

✨ What it does

The Bot writes a brief of [VIDEO] with timestamped claims and three follow-up links it can actually open. You read 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: Brief [VIDEO] with timestamped claims and what to watch next. Do not post. Sources: The URL, transcript if available. 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 invent quotes. Do not post the brief. Deliverable: Claims with timestamps, unknowns, 3 follow-up links you can open. Review point: I read it.

💡

Pro tip: Timestamps or it is a blog post. If the transcript is missing, say so.

X scout, computer not grok.com chat

21/21

✨ What it does

The Bot opens X in the cloud browser, scouts [TOPIC] for [WINDOW], cites posts it can open, and stops if login locks the computer. You decide whether to weigh 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: Scout [TOPIC] on X for [WINDOW]. Cite posts you can open. If login locks, stop and tell me. Sources: X on the cloud browser. 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 post. Do not like or follow. If X locks the computer, stop. Deliverable: Viewpoints, traction, what people get wrong, links. Review point: I decide if we weigh in.

💡

Pro tip: Cloud computers hit site risk controls. If X locks, stop. Do not fight the captcha in a loop.

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.
No. grok.com DeepSearch is a chat mode. A Grok Bot can keep a named research job, open sites in its own browser, take screenshots, and run on a schedule after you close the laptop. These prompts still require citations and allow "unknown". They are not Imagine prompts and not jailbreaks.
Staff have said official X plugin auth can show connected with tools=0 across desktop, Cloud, and Grok Bot. Use the cloud browser, or wait for the fix. Do not paste an X token into chat.

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.