Prompt Library

Grok Bot prompts for marketing work that stays on your side of publish

21 copy-paste prompts

Campaign reads, GTM research, and launch checklists that run on the Bot computer. Budgets and sends stay behind approval, the way the official paid-media use case is written.

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

Campaigns and budget (recommend only)

4 prompts

Weekly paid + organic read

1/21

✨ What it does

The Bot pulls current spend and performance, compares them to [MONTHLY BUDGET] and [TARGET CAC], and drafts a Slack update with recommended moves and the math. You send the update and you change budgets.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Pull current spend and performance by campaign. Compare to [MONTHLY BUDGET] and [TARGET CAC]. Sources: [ADS PLATFORMS], [ANALYTICS], [BUDGET SHEET], [SLACK CHANNEL 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. - Do not change bids, budgets, or status. Do not send the Slack message. Deliverable: What moved, recommended reallocations with math, draft Slack update, source links. Review point: I send the update. I change budgets.

💡

Pro tip: Official paid-media use case: recommend reallocations with numbers. Do not change budgets or send.

Creative fatigue report

2/21

✨ What it does

The Bot finds creatives in [ACCOUNT] that look tired by [RULE] and suggests five replacement angles from the last 14 days. You brief the designer; the Bot does not pause or upload ads.

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 creatives in [ACCOUNT] that look fatigued by [RULE]. Suggest 5 replacement angles. Sources: [ADS MANAGER], [BRAND BRIEF], last 14 days of performance. 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 or upload ads. Deliverable: Creative, frequency, CTR trend, why it looks tired, replacement angle. Review point: I brief the designer.

💡

Pro tip: Give it the fatigue rule (frequency, CTR drop) or it will flag everything older than a week.

UTM and landing-page mismatch hunt

3/21

✨ What it does

The Bot clicks every live campaign URL in [SHEET] and flags 404s, the wrong offer, or a missing UTM, with a screenshot path. You fix the live 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: Check every live campaign URL in [SHEET] and flag 404s, wrong offer, or missing UTM. Sources: [CAMPAIGN SHEET], the live pages 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 edit pages or ads. Deliverable: URL, status, mismatch, screenshot path, suggested fix. Review point: I fix the live ones.

💡

Pro tip: Computer-use job. No API required. It clicks like a person.

Budget reallocation memo

4/21

✨ What it does

The Bot writes a one-page memo for [MONTH] from [SOURCE OF TRUTH]: current spend, a proposed shift, the risk, and how to undo it, with links under the numbers. You take it to the meeting; the Bot does not move any sliders.

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 reallocation memo for [MONTH] using [SOURCE OF TRUTH]. Sources: [ADS], [ANALYTICS], [BUDGET SHEET], [TARGET CAC]. 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 any platform settings. Deliverable: One page: current, proposed, risk, rollback, links. Review point: I take it to the meeting.

💡

Pro tip: Cite the exact report URL under every number. Memos without links get ignored.

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

GTM and launch

4 prompts

Launch checklist across tools

5/21

✨ What it does

The Bot builds a launch checklist for [FEATURE] on [DATE] across [WEB, EMAIL, IN-APP, SOCIAL, SALES], with an owner and a done-definition for each row. You tick the boxes; the Bot does not publish or send.

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 launch checklist for [FEATURE] on [DATE] across [WEB, EMAIL, IN-APP, SOCIAL, SALES]. Sources: [LAUNCH DOC], [FIGMA], [CMS], [EMAIL TOOL], [SALES DECK]. 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, schedule, or send. Deliverable: Checklist with owner, tool, done-definition, and a red-flag if the asset is missing. Review point: I tick boxes.

💡

Pro tip: Name every tool. "Make sure we launched" is how a Bot tweets from a staging URL.

Competitor launch teardown

6/21

✨ What it does

The Bot tears down [COMPETITOR] launch of [THING] into facts, claims, and rumor, with screenshots from their site, changelog, and X. You decide whether to respond; the Bot does not post or email their customers.

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] launch of [THING]. Facts vs claims vs rumor. Sources: Their site, changelog, X, [REVIEW SITES], our positioning doc. 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 a response. Do not email their customers. Deliverable: What shipped, proof, how they framed it, where we can answer, links and screenshots. Review point: I decide if we respond.

💡

Pro tip: Ask it to separate screenshotable claims from rumor. Live web plus X is the Bot's edge, not vibes.

Sales enablement one-pager

7/21

✨ What it does

The Bot writes a one-pager for [FEATURE] for [SDR / AE], including the demo path, objections, and a do-not-say list. You drop it in the enablement folder; the Bot does not post it to the 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: Write a one-pager for [FEATURE] for [SDR / AE]. Include do-not-say. Sources: [LAUNCH DOC], [PRICING], [OBJECTION DOC], [CUSTOMER QUOTES WITH SOURCE]. 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 to Slack or email the team. Deliverable: Problem, who it is for, demo path, objections, do-not-say, links. Review point: I drop it in the enablement folder.

💡

Pro tip: Include the "do not say" list. Enablement without guardrails becomes discounting.

Waitlist or signup QA

8/21

✨ What it does

The Bot walks [SIGNUP URL] as a new user with [TEST EMAIL] and files every friction point with screenshots against [EXPECTED COPY DOC]. You file the tickets; the Bot does not submit a real lead.

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 [SIGNUP URL] as a new user. File every friction point with screenshots. Sources: The live URL on the cloud browser. [EXPECTED COPY DOC]. 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 a real lead. Use [TEST EMAIL]. Do not touch production customer data. Deliverable: Step, expected, actual, screenshot, severity. Review point: I file tickets.

💡

Pro tip: Use a fresh test account. Official bug-repro rule: no production customer data.

Content ops on the computer

4 prompts

Repurpose a podcast into a kit

9/21

✨ What it does

The Bot turns [EPISODE URL OR FILE] into a summary, eight quotes, a newsletter blurb, and five social cuts in one doc. You publish; the Bot does not schedule posts.

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 [EPISODE URL OR FILE], produce a summary, 8 quotes, 1 newsletter blurb, 5 social cuts. Sources: The file or URL, [SHOW NOTES], [BRAND VOICE]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not publish or schedule posts. Deliverable: Kit in one doc, plus timestamped quotes. Review point: I publish.

💡

Pro tip: Fifteen seconds to a summary is real. Publishing still needs your name on it.

CMS draft, not a publish

10/21

✨ What it does

The Bot creates an unpublished draft in [CMS] from [BRIEF], using [BRAND GUIDE] and images in [FOLDER], and reports the draft URL. You hit publish.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Create an unpublished draft in [CMS] from [BRIEF]. Do not publish. Sources: [CMS], [BRIEF], [BRAND GUIDE], images in [FOLDER]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not publish, schedule, or change live pages. Deliverable: Draft URL, slug, title, and a diff vs the brief. Review point: I hit publish.

💡

Pro tip: WordPress-updates-taught-once is a field case. Teaching publish without approval is how you ship typos.

Broken-link and OG crawl

11/21

✨ What it does

The Bot crawls [SITE] starting at [URL], stays inside [DOMAIN], and reports 404s, redirect chains, and missing social images. You assign the fixes; the Bot does not edit the site.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Crawl [SITE] starting at [URL]. Report 404s, redirect chains, and missing OG images. Sources: The live site in the cloud browser. Stay inside [DOMAIN]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not edit the site. Do not submit the site to any auditor as me. Deliverable: URL, issue, screenshot if visual, suggested fix. Review point: I assign fixes.

💡

Pro tip: No sitemap API needed. Computer use is the point.

Asset factory with a human art-direct

12/21

✨ What it does

The Bot produces [N] assets for [FEATURE] using [ART PAGE OR FOLDER CONVENTIONS] and stages the files with names. You pick the winners; the Bot does not publish them.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Produce [N] assets for [FEATURE] using [ART PAGE OR FOLDER CONVENTIONS]. Stage files, do not ship. Sources: [BRIEF], [BRAND], [EXISTING ASSET FOLDER], [ART TOOL 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 publish assets. Do not generate sexual or real-person likeness without my written ok. Deliverable: File paths, naming, what still needs a human pass. Review point: I pick winners.

💡

Pro tip: You still approve likeness, brand, and anything that looks like a real person.

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

SEO and pages

3 prompts

SERP capture for one keyword

13/21

✨ What it does

The Bot opens the live Google results for [KEYWORD], notes who ranks, and drafts an outline you can actually win, using [EXISTING PAGE IF ANY]. You decide whether to write the page.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: For [KEYWORD], capture the current SERP and draft an outline we can actually win. Sources: Live Google SERP in the cloud browser, our [EXISTING PAGE IF ANY], [POSITIONING]. 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 search volume. If you cannot see a number, say unknown. Deliverable: Who ranks, intent, gaps, outline, internal links to suggest. Review point: I decide if we write it.

💡

Pro tip: Grok Bot can click the SERP. Cite live titles. Do not invent KD numbers.

Refresh a decaying page

14/21

✨ What it does

The Bot compares [URL] to today's results for [KEYWORD] and drafts what to keep, change, or cut, plus a new intro and FAQs. You edit the live page; the Bot does not.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Refresh plan for [URL] vs today's SERP for [KEYWORD]. Sources: The live page, the SERP, [ANALYTICS FOR THAT 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 edit the live page. Deliverable: Keep / change / cut, plus a draft of the new intro and FAQs. Review point: I edit.

💡

Pro tip: Ask for a diff, not a rewrite. Full rewrites kill links you already earned.

Partner or affiliate page QA

15/21

✨ What it does

The Bot checks [PARTNER PAGE URL] against [OFFER SHEET] for dead links, expired dates, and missing disclosures, with screenshots. You update the page and talk to counsel; the Bot does not change the page.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: QA [PARTNER PAGE URL] for dead links, expired dates, and missing disclosure. Sources: The live page and [OFFER SHEET]. 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 the page. This is not legal advice. Deliverable: Issue list with screenshots and suggested copy, plus "ask legal" items. Review point: I update the page.

💡

Pro tip: Money and legal. The Bot flags. You talk to counsel.

Standing marketing Bots

6 prompts

Marketing CoS digest

16/21

✨ What it does

The Bot returns only marketing items since yesterday that map to [PRIORITIES DOC], with source, why it matters, and whether you owe a decision. You act; the Bot does not send messages or change meetings.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Since yesterday, return only marketing items that map to [PRIORITIES DOC]. Sources: [SLACK CHANNELS], [INBOX], [CALENDAR], [ADS], [CMS]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send messages or change meetings. Deliverable: Item, source, why it matters, next step, whether I owe a decision. Review point: Digest here. I act.

💡

Pro tip: Official CoS shape: only items that map to the priorities doc. Otherwise it is a firehose.

Brand-voice linter for drafts

17/21

✨ What it does

The Bot reads drafts in this thread or [FOLDER] against [VOICE DOC], flags off-voice lines, and rewrites them. You accept the rewrites; the Bot does not publish them.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Lint these drafts against [VOICE DOC]. Flag off-voice lines and rewrite them. Sources: [VOICE DOC], drafts in this thread or [FOLDER]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not publish the rewritten drafts. Deliverable: File, off-voice line, why, rewrite. Review point: I accept rewrites.

💡

Pro tip: Attach the voice doc. "Make it on brand" without a doc is a personality quiz.

What marketing Bots never do

18/21

✨ What it does

The Bot writes a never-do list for marketing Bots from your rules, such as [E.G. NO LIVE ADS, NO LIST SENDS, NO LEGAL CLAIMS], plus what a human does instead. You paste it into every marketing 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 the never-do list for marketing Bots on this computer. Sources: My rules: [E.G. NO LIVE ADS, NO LIST SENDS, NO LEGAL CLAIMS]. 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 with the human substitute. Review point: I paste it into Bot descriptions.

💡

Pro tip: Paste this into every marketing Bot. Helpful Bots schedule tweets at 2am.

Live slide update from last night's numbers

19/21

✨ What it does

The Bot updates [DECK] slides [N] with yesterday's [METRIC] from [SOURCE], or leaves the last-good number if the source is stale. You present; the Bot does not email the deck.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Update [DECK] slides [N] with yesterday's [METRIC] from [SOURCE]. Do not present. Do not email the deck. Sources: [DECK], [ANALYTICS]. Fail closed if the source is stale. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send the deck. Do not change the narrative slides, only the number slides I name. Deliverable: What changed, old vs new, file path. Review point: I present.

💡

Pro tip: If analytics is down, the slide stays last-good. Do not invent a chart.

Competitor page diff

20/21

✨ What it does

The Bot screenshots [COMPETITOR URLS] and compares them to last week's pack in [FOLDER], listing what moved and any 404s. You brief the team; the Bot does not post about the competitors.

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 [COMPETITOR URLS] and diff vs last week's pack in [FOLDER]. Do not post about them. Sources: Those URLs, last week's folder. If a URL 404s, say so. 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 competitors. Do not publish the pack. Deliverable: What moved, screenshot paths, unknowns. Review point: I brief the team.

💡

Pro tip: Same URLs every week or the diff is noise.

Launch checklist the Bot cannot tick alone

21/21

✨ What it does

The Bot builds a launch checklist for [CAMPAIGN] against [BRIEF] and marks what it can verify versus what you must do. You launch; the Bot does not publish, schedule, or turn ads 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: Build a launch checklist for [CAMPAIGN] against [BRIEF]. Mark what you can verify vs what I must do. Sources: [BRIEF], [CMS DRAFT], [ADS DRAFT]. 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, schedule, or turn ads on. Deliverable: Checklist with owner = you vs me. Review point: I launch.

💡

Pro tip: UTM, OG, legal, and "who hits publish" stay human.

Free tool

Prompt Optimizer

Turn a rough idea into a structured, professional AI prompt.

Try it free →

Frequently Asked Questions

Grok Bot is an always-on AI teammate from xAI / SpaceXAI that runs on a persistent cloud computer (browser, files, terminal). You message it like a coworker and it finishes work inside the apps you already use. Grok on grok.com or in the X app is a chat assistant with live search and Grok Imagine. These pages are only for the teammate product. For chat and Imagine prompts, use the Grok prompts library.

Yes. Official docs are explicit: isolation is per user, not per Bot. Files, browser logins, and plugins on the computer are visible to every Bot on your account. Do not treat a second Bot as a security boundary. Put irreversible actions (send, pay, delete, production changes) behind approval.

Access has expanded since the August 2026 launch. It is included with SuperGrok plans and with Cursor Pro and Cursor Teams, plus a limited free trial for everyone else at times. Plans and weekly usage change. Check the official Grok Bot plans page before you buy a seat for this product.

It can sign into ads managers and read them like a person. Official paid-media use case still says: recommend reallocations, draft the update, do not change budgets or send the message. Keep campaign changes behind approval even after the analysis becomes a routine.

The community list points to GTM playbooks and skills (for example outbound on Instantly or HeyReach). Treat those as starting points. You still review every list and every send. These prompts stay on the review-list side of that line.

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 marketers

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