Grok Bot content prompts that stop at unpublished
Podcast kits, CMS drafts, changelogs, asset folders. Field cases include 74 game assets and 15-second podcast summaries. These prompts still leave publish, schedule, and send on your side.
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.
Repurpose
4 promptsPodcast to kit
1/21✨ What it does
The Bot turns [EPISODE] into a kit with a summary, eight timestamped quotes, a newsletter blurb, and five social cuts in [VOICE], and does not publish. You publish what you want.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: From [EPISODE], produce summary, 8 timestamped quotes, newsletter blurb, 5 social cuts. Do not publish. Sources: URL or file, [SHOW NOTES], [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. Deliverable: One kit doc plus quote timestamps. Review point: I publish.
Pro tip: Timestamps. Fifteen seconds to a summary is real. Publishing still needs your name.
Talk or webinar to thread
2/21✨ What it does
The Bot turns [TALK] into an [X / LINKEDIN] thread of [N] self-contained posts with source timestamps, and does not post. You post.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Turn [TALK] into an [X / LINKEDIN] thread of [N] posts. Self-contained points. Do not post. Sources: Transcript or deck, [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 post. Deliverable: Numbered posts, source timestamps. Review point: I post.
Pro tip: Each post self-contained. No invented audience quotes.
Changelog to customer email
3/21✨ What it does
The Bot drafts a customer email from [CHANGELOG RANGE], skips internal-only changes, and includes a subject, a body, and a do-not-say list. You send 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: From [CHANGELOG RANGE], draft a customer email. Skip internal-only. Do not send. Sources: [REPO OR CHANGELOG], [LAST EMAIL]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not send. Do not invent features. Deliverable: Subject, body, do-not-say. Review point: I send.
Pro tip: Skip the rename. Lead with what they can do now.
One piece, five formats
4/21✨ What it does
The Bot remakes [SOURCE] as LinkedIn, an X thread, a newsletter, a carousel script, and a 60-second video script, each with a different angle. You pick two.
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 [SOURCE], make LinkedIn, X thread, newsletter, carousel script, 60s video script. Do not publish. Sources: The source, [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. Deliverable: Five pieces, each with a different angle. Review point: I pick two.
Pro tip: Ask it to change the angle per channel. Same sentence five times is waste.
Prompts get you started. Tutorials level you up.
A growing library of 300+ hands-on AI tutorials. New tutorials added every week.
CMS and site
4 promptsUnpublished draft in the CMS
5/21✨ What it does
The Bot creates an unpublished [CMS] draft from [BRIEF], [BRAND], and images in [FOLDER], and does not publish or schedule it. 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 [CMS] draft from [BRIEF]. Do not publish or schedule. Sources: [CMS], [BRIEF], [BRAND], 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. Do not change live pages. Deliverable: Draft URL, slug, diff vs brief. Review point: I hit publish.
Pro tip: Publish is the approval. Do not include it in the taught skill.
Refresh vs SERP
6/21✨ What it does
The Bot writes a refresh plan for [URL] versus today's search results for [KEYWORD], lists keep, change, and cut, plus a draft intro and FAQs, without editing the live page. You edit 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: Refresh plan for [URL] vs today's SERP for [KEYWORD]. Do not edit live. Sources: Live page, SERP, [ANALYTICS]. 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. Do not edit live. Deliverable: Keep / change / cut, draft intro and FAQs. Review point: I edit.
Pro tip: Keep what already ranks. Change the rotting parts.
OG and share-card QA
7/21✨ What it does
The Bot checks [URLS] for title, description, and share image, and screenshots anything missing. You fix the misses.
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 [URLS] for title, description, OG image. Screenshot misses. Sources: Pages in 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 edit the CMS. Deliverable: URL, missing field, screenshot. Review point: I fix.
Pro tip: A missing OG image is a content bug, not a "later".
Internal link pass
8/21✨ What it does
The Bot suggests internal links for [DRAFT] only to URLs on [SITE] it can open, and marks unknown if a target 404s. You add the working links.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Suggest internal links for [DRAFT] only to URLs you can open. Unknown if they 404. Sources: The draft, [SITE] in 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 edit live pages. Deliverable: Anchor, target, 200/404. Review point: I add the 200s.
Pro tip: If you are not sure the URL exists, say unknown.
Assets
4 promptsAsset factory, human art-direct
9/21✨ What it does
The Bot produces [N] assets for [FEATURE] into [FOLDER] with [NAMING] from [BRIEF] and [BRAND], and does not ship them into the product. You pick the winners.
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] into [FOLDER] with [NAMING]. Do not ship into the product. Sources: [BRIEF], [BRAND], [ART TOOL]. 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. No real-person likeness without my ok. Deliverable: Paths, what needs a human pass. Review point: I pick winners.
Pro tip: Naming conventions in the brief or you get img_final_final.
Crop and rename only
10/21✨ What it does
The Bot crops and renames files in [FOLDER] to [SPEC], keeps the originals, and lists anything that failed. You spot-check the edges.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Crop and rename files in [FOLDER] to [SPEC]. Keep originals. Do not overwrite the only copy. Sources: [FOLDER], [SPEC]. 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 originals. Deliverable: New paths, leftovers that failed. Review point: I spot-check.
Pro tip: Transparent PNG crops, consistent names. You still check edges.
Brand-voice lint
11/21✨ What it does
The Bot checks [DRAFTS] against [VOICE DOC], rewrites lines that are off voice, and leaves everything unpublished. You accept the rewrites.
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 [DRAFTS] against [VOICE DOC]. Rewrite off-voice lines. Do not publish. Sources: [VOICE], drafts. 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 rewrites. Deliverable: Line, why, rewrite. Review point: I accept.
Pro tip: Attach the voice doc. "On brand" without a doc is a personality quiz.
Thumbnail or cover brief
12/21✨ What it does
The Bot writes a cover brief for [PIECE] with size, text on the image, do-nots, and reference links, without generating a final unless you ask in a separate job. You design it or you commission 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: Write a cover brief for [PIECE]: size, text on image, do-not, reference links. Do not generate the final unless I ask in a separate job. Sources: [PIECE], [BRAND]. 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 cover. Deliverable: Brief a designer could use. Review point: I design or I commission.
Pro tip: Link to grok-image-prompts if they want Imagine. Here we stay on the teammate.
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.
Calendar and ops
3 prompts30-day calendar with holes
13/21✨ What it does
The Bot builds a 30-day calendar for [CHANNELS] from [PILLARS] and marks days blocked by missing assets, without scheduling anything. You schedule the real 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: 30-day calendar for [CHANNELS] from [PILLARS]. Mark days blocked by missing assets. Do not schedule. Sources: [PILLARS], [ASSET FOLDER], [LAUNCH DATES]. 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 schedule posts. Deliverable: Calendar, blocked days, why. Review point: I schedule the real ones.
Pro tip: If an asset is missing, the day is blocked, not filled with a ghost post.
Newsletter edition
14/21✨ What it does
The Bot writes this week's newsletter on [TOPIC] in [400-500] words, plus three subject lines and a reply prompt, and does not send it. You send 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: Write this week's newsletter on [TOPIC] in [400-500] words. 3 subject lines. Do not send. Sources: [TOPIC], [VOICE], [LIST STATS IF ANY]. 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. Do not invent list stats. Deliverable: Subjects, body, reply prompt. Review point: I send.
Pro tip: No Happy Tuesday. Under a word cap.
Legal or claims lint
15/21✨ What it does
The Bot checks [DRAFT] for guarantees, medical claims, and earnings claims against [CLAIMS WE ARE ALLOWED TO MAKE], and flags lines to cut or send to counsel. You ask counsel or you cut the line.
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 [DRAFT] for legal-looking claims (guarantees, medical, earnings). Flag. Do not publish. Sources: The draft, [CLAIMS WE ARE ALLOWED TO MAKE]. 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 publish. Deliverable: Line, risk, rewrite or "ask counsel". Review point: I ask counsel or I cut.
Pro tip: Not legal advice. Flag and stop. You talk to counsel.
Make the content Bot durable
6 promptsContent Bot description
16/21✨ What it does
The Bot writes a content Bot description named [NAME] covering [CMS], [VOICE], and [CHANNELS], with never publish, never schedule, and never send. 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 content Bot description named [NAME]. Sources: [CMS], [VOICE], [CHANNELS]. 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 publish, schedule, or send. Deliverable: Description and kit format. Review point: I create it.
Pro tip: Write the CMS and the voice doc in the description.
Monday kit routine
17/21✨ What it does
The Bot writes a Monday routine that builds a kit if [SOURCE] has a new episode or changelog, or writes nothing to repurpose if not, and does not publish. 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: Mondays, if [SOURCE] has a new episode or changelog, build a kit. If not, post "nothing to repurpose". Do not publish. Sources: [FEED OR CHANGELOG]. Fail closed if missing. 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. Deliverable: Routine card. Review point: I enable.
Pro tip: If nothing shipped, the routine says so. Do not invent a podcast.
What content Bots never do
18/21✨ What it does
The Bot writes a twelve-item list of things content Bots must not do, including publishing, scheduling, emailing the list, inventing quotes, editing live pages, and faking metrics. You paste that list before you teach WordPress.
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 content 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 before you teach WordPress.
15-second podcast summary, then the real kit
19/21✨ What it does
The Bot first writes a five-bullet summary of [EPISODE], then builds the full kit only after you say go, and publishes neither. You say go or you skip.
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 a 5-bullet summary of [EPISODE]. If I say go, then the full kit. Do not publish either. Sources: URL or file. 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. Do not invent guest quotes. Deliverable: Summary first, kit only after I say go. Review point: I say go or I skip.
Pro tip: Do not ship the 15-second version. Use it to decide if a kit is worth it.
WordPress draft taught once
20/21✨ What it does
The Bot writes a shot list for teaching create an unpublished draft from [BRIEF] in [CMS], and names the Publish click you must never include in the recording. You record the skill.
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 teach "create unpublished draft from [BRIEF]" in [CMS]. List what to show and the click I must never include. Sources: [CMS], [BRIEF]. 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. Do not include Publish in the taught skill. Deliverable: Shot list and the never-click. Review point: I record.
Pro tip: If the skill includes Publish, a nap becomes a live page.
Grokularity rule: humans read, proven agents write
21/21✨ What it does
The Bot writes a publishing rule for [SITE] covering what a Bot may draft, what a human must read, and what proven means, with four examples. You paste that rule into every content 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 publishing rule for [SITE]: what a Bot may draft, what a human must read, what "proven" means. Sources: My site and who can publish: [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 publish. Do not give a Bot a "proven" badge. Deliverable: The rule, 4 examples. Review point: I paste it into every content Bot.
Pro tip: If nobody read it, it is not proven. Do not let a Bot mark its own work proven.
Free tool
Prompt Optimizer
Turn a rough idea into a structured, professional AI prompt.
Frequently Asked Questions
Prompts are the starting line. Tutorials are the finish.
A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.
7-day free trial. Cancel anytime.
Related guides