Grok Bot docs prompts that stop at unpublished
Internal wiki and help-center drafts from files you already have. How-tos, runbooks, ADRs, and product-vs-docs diffs. The Bot writes. You publish. Not a blog kit and not a research brief.
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.
Help-center how-tos
5 promptsHow-to from source files
1/21✨ What it does
The Bot drafts a how-to for [FEATURE] from [SOURCE FILES] with numbered steps, prerequisites, and screenshot placeholders. You publish the page in the wiki or help center.
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 a how-to for [FEATURE] from [SOURCE FILES] only. Numbered steps, prerequisites, screenshot placeholders. Do not publish. Sources: [SOURCE FILES], [VOICE DOC 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 publish or schedule. Do not invent UI that the files do not show. Deliverable: Title, intro, steps, screenshot placeholders, related-link stubs. Review point: I add screenshots and I publish.
Pro tip: Attach the files. "Write docs for the feature" with no source is a stall, then fiction.
Troubleshooting from tickets
2/21✨ What it does
The Bot writes a troubleshooting guide for [ERROR] from [TICKETS] and [PRODUCT DOCS], with a quick-fix list and four causes. You publish it in the help center.
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 troubleshooting guide for [ERROR] from [TICKETS] and [PRODUCT DOCS]. Quick-fix list, four causes, when to contact support. Do not publish. Sources: [TICKETS], [PRODUCT DOCS], [ERROR COPY 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 reply to those tickets. Do not invent a cause the sources omit. Deliverable: Guide draft, cites, leftover unknowns. Review point: I publish.
Pro tip: If tickets disagree with the docs, show both. Do not average them into one fake cause.
FAQ from support themes
3/21✨ What it does
The Bot drafts an FAQ for [PRODUCT AREA] from [SUPPORT THEMES] and [SOURCE FILES], answering only what those files support. You publish the FAQ in the help center.
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 [8-12] FAQ items for [PRODUCT AREA] from [SUPPORT THEMES] and [SOURCE FILES]. Mark unsupported answers unknown. Do not publish. Sources: [SUPPORT THEMES], [SOURCE FILES], [ALLOWED 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. - Do not invent pricing, SLA, or refund policy. Deliverable: Q, A, source cite or unknown. Review point: I publish the grounded ones.
Pro tip: Unknown is a valid answer. A guessed policy line becomes the policy.
Feature reference from spec and UI
4/21✨ What it does
The Bot writes a feature reference for [FEATURE] from [SPEC] and a read-only look at [PRODUCT UI], listing settings, defaults, and limits. You publish the reference on the wiki.
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 feature reference for [FEATURE] from [SPEC] and [PRODUCT UI]. Settings table, defaults, limits. Do not edit the product or publish. Sources: [SPEC], [PRODUCT UI] read-only, [PLAN GATES 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 change settings. Do not publish. Deliverable: Overview, path in the product, settings table, limits, related stubs. Review point: I publish.
Pro tip: Screenshot the setting. A paraphrased default is how the wiki lies for a year.
Click-path with screenshot holes
5/21✨ What it does
The Bot drafts a click-path walkthrough for [TASK] from [SOURCE FILES] and [STAGING UI], with a placeholder after each step. You publish the walkthrough after you add real screenshots.
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 a click-path for [TASK] from [SOURCE FILES] and [STAGING UI]. One placeholder after each step. Do not publish. Sources: [SOURCE FILES], [STAGING UI] 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 capture production customer data. Do not publish. Deliverable: Steps, [INSERT SCREENSHOT] lines, path that still matches staging. Review point: I capture and I publish.
Pro tip: Placeholders beat stock UI. Invented chrome is worse than a hole.
Internal wiki and runbooks
4 promptsRunbook from an incident pack
6/21✨ What it does
The Bot turns [INCIDENT PACK] into an internal runbook with detection, owner, steps, and rollback, citing only that pack. You publish the runbook on the wiki.
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 [INCIDENT PACK] into a runbook: detect, owner, steps, rollback. Cite the pack. Do not publish. Do not page anyone. Sources: [INCIDENT PACK], [EXISTING RUNBOOK 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 change alerts or on-call. Do not publish. Deliverable: Runbook draft, cites, gaps the pack never covered. Review point: I publish.
Pro tip: One pack, one runbook. Do not import folklore from Slack without a cite.
First-week wiki for a role
7/21✨ What it does
The Bot drafts a first-week wiki page for [ROLE] from [EXISTING DOCS] and [CHECKLIST], linking only pages it can open. You publish the onboarding 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: Draft a first-week page for [ROLE] from [EXISTING DOCS] and [CHECKLIST]. Link only URLs you can open. Do not publish. Sources: [EXISTING DOCS], [CHECKLIST], [WIKI] 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 email the new hire. Do not publish. Deliverable: Day plan, open links, unknown list. Review point: I publish.
Pro tip: Dead links fail onboarding. If you cannot open it, write unknown, not a hopeful URL.
ADR from notes and PRs
8/21✨ What it does
The Bot drafts an ADR for [DECISION] from [NOTES AND PRS], with context, options considered, the choice, and what you rejected. You publish the decision page on the wiki.
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 an ADR for [DECISION] from [NOTES AND PRS]. Context, options, choice, rejected. Do not publish. Sources: [NOTES AND PRS] 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 merge PRs. Do not publish. Deliverable: ADR draft with cites and open questions. Review point: I publish.
Pro tip: Leave the rejected options visible. A decision page that hides them is a press release.
Process page from Slack and files
9/21✨ What it does
The Bot writes a process page for [WORKFLOW] from [SLACK THREAD] and [SOURCE FILES], with owners, inputs, and a stop-before-publish line. You publish the process on the wiki.
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 process page for [WORKFLOW] from [SLACK THREAD] and [SOURCE FILES]. Owners, inputs, stop-before-publish. Do not publish. Sources: [SLACK THREAD], [SOURCE 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 post the process in Slack. Do not publish. Deliverable: Process draft, owner, approval line. Review point: I publish.
Pro tip: Name the owner. An ownerless process is a wiki ghost.
Drift and refresh
4 promptsDocs versus the product
10/21✨ What it does
The Bot compares [DOCS URL] to [PRODUCT URL] for [FEATURE], lists claim versus actual, and drafts replacement copy with screenshot paths. You publish the corrected 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: Compare [DOCS URL] to [PRODUCT URL] for [FEATURE]. List drift, draft replacement copy, save screenshots. Do not edit live docs. 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: Claim, actual, screenshot path, replacement draft. Review point: I publish the fix.
Pro tip: Computer use. A screenshot of the mismatch is the evidence. Do not edit live docs.
Stale page audit
11/21✨ What it does
The Bot audits pages in [WIKI SPACE] older than [N] days against [SOURCE FILES] and drafts refresh notes for the stale ones. You publish the updates you accept.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Audit [WIKI SPACE] pages older than [N] days against [SOURCE FILES]. Draft refresh notes for real drift only. Do not publish. Sources: [WIKI SPACE], [SOURCE 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 live pages. Do not delete pages. Deliverable: Page, last update, still-true / drifted, refresh draft. Review point: I publish the refreshes.
Pro tip: Age alone is not stale. A page that still matches the files can stay.
Changelog into wiki diffs
12/21✨ What it does
The Bot turns [CHANGELOG RANGE] into unpublished wiki diffs for pages that mention [FEATURE], without inventing behavior the changelog never states. You publish each accepted diff.
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 unpublished diffs for wiki pages that mention [FEATURE]. No invented behavior. Do not publish. Sources: [CHANGELOG RANGE], [WIKI SEARCH FOR FEATURE]. 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. Do not invent user-facing copy. Deliverable: Page, proposed diff, changelog cite. Review point: I publish accepted diffs.
Pro tip: Skip internal-only tickets. If the changelog is silent, the wiki stays silent.
Conflict between two pages
13/21✨ What it does
The Bot compares [PAGE A] and [PAGE B] on [QUESTION], lists conflicts with cites, and drafts one reconciled page. You publish the winner and archive the rest.
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 [PAGE A] and [PAGE B] on [QUESTION]. List conflicts. Draft one reconciled page only if [SOURCE FILES] settle it. Do not publish. Sources: The two pages, [SOURCE 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 delete or archive either page. Deliverable: Conflict table, cites, reconciled draft or "unsettled". Review point: I publish the winner.
Pro tip: Do not average. Show both claims. Newer is not automatically true.
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.
Structure and findability
4 promptsWiki tree, no live moves
14/21✨ What it does
The Bot proposes a wiki tree for [SPACE] from [PAGE LIST] and [TICKET SEARCH TERMS], with keep, merge, or move, and no live moves. You publish the new information architecture.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Propose an IA for [SPACE] from [PAGE LIST] and [TICKET SEARCH TERMS]. Keep / merge / move. Do not move pages. Sources: [PAGE LIST], [TICKET SEARCH TERMS], current TOC. 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 move, rename, or delete pages. Deliverable: Proposed tree, rationale, pages left alone. Review point: I publish the tree, then I move.
Pro tip: Moves break bookmarks. Propose first. You move after people agree.
Internal links that exist
15/21✨ What it does
The Bot suggests internal links for [DRAFT] only to wiki URLs it can open, and marks 404s as unknown. You publish the draft with the live 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. Do not edit live pages. Sources: The draft, [WIKI OR HELP CENTER] 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, unknown list. Review point: I add the 200s and I publish.
Pro tip: If you are not sure the URL exists, say unknown. Dead suggestions fail the next reader.
Titles people actually search
16/21✨ What it does
The Bot rewrites titles and first paragraphs for [ARTICLES] to match how [USERS] search in [HELP CENTER], without editing live pages. You publish the titles.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Rewrite titles and first paragraphs for [ARTICLES] to match [TICKET PHRASES]. Do not edit live pages. Sources: [ARTICLES], [TICKET PHRASES], [HELP CENTER SEARCH]. 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 live titles. Do not invent search volume. Deliverable: Old title, new title, first-paragraph draft, phrase it matches. Review point: I publish the titles.
Pro tip: Use phrases from tickets, not the product name we wish they typed.
Missing-page stubs from tickets
17/21✨ What it does
The Bot lists missing help pages from [TICKET THEMES] versus [CURRENT TOC], and drafts stubs from [SOURCE FILES] where evidence exists. You publish the stubs 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: List missing pages from [TICKET THEMES] versus [CURRENT TOC]. Draft stubs only from [SOURCE FILES]. Do not publish. Sources: [TICKET THEMES], [CURRENT TOC], [SOURCE 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 create live pages. Do not invent coverage. Deliverable: Gap, ticket theme, stub or "no source". Review point: I publish the stubs I want.
Pro tip: A stub with a source beats a long page of guesses. Thin evidence means no stub.
Make the docs Bot durable
4 promptsDocs Bot description
18/21✨ What it does
The Bot writes a docs Bot description named [NAME] with the wiki, voice, source-file rule, and never-publish. You create the Bot, then you publish its drafts.
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 docs Bot description named [NAME] for [WIKI OR HELP CENTER]. Source-file rule. Never publish. Sources: [WIKI], [VOICE], [SOURCE FOLDERS]. 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 delete live docs. Deliverable: Description, draft format, never-do. Review point: I create it.
Pro tip: Write the wiki and the voice doc in the description. "Be helpful" is how fiction ships.
Weekday stale-docs routine
19/21✨ What it does
The Bot writes a weekday job that flags stale pages in [SPACE] against [SOURCE FILES] and drops unpublished diffs here. You publish after you 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: Weekdays, flag stale pages in [SPACE] against [SOURCE FILES] and drop unpublished diffs here. If none, say none. Do not publish. Sources: [SPACE], [SOURCE FILES]. Fail closed if the wiki 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 edit live pages. Do not reuse yesterday as new. Deliverable: Routine card, report format. Review point: I enable, then I publish.
Pro tip: If nothing drifted, the routine says so. Do not invent a refresh.
Style card for the wiki
20/21✨ What it does
The Bot drafts a one-page style card for [WIKI] from [VOICE DOC] covering headings, screenshots, and unknown versus guess. You publish the card on the wiki.
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 a one-page style card for [WIKI] from [VOICE DOC]: headings, screenshots, unknown versus guess. Do not publish. Sources: [VOICE DOC], [THREE EXAMPLE PAGES]. 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 rewrite the whole wiki to match the card. Deliverable: One-page card plus three before/after lines. Review point: I publish the card.
Pro tip: Busy writers will not read a 20-page guide. One page, or it will not be used.
What docs Bots never do
21/21✨ What it does
The Bot writes a never-do list for docs Bots from [RULES] such as no live publish, no invented UI, and no deletes, plus the human substitute. You publish that list into every docs 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 docs Bots on this computer. Sources: My rules: [E.G. NO LIVE PUBLISH, NO INVENTED UI, NO DELETE, NO CUSTOMER DATA IN SCREENSHOTS]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not enable a skill that includes Publish. Deliverable: 12 never-do items and the human substitute. Review point: I paste it into every docs Bot.
Pro tip: Paste this before you teach Confluence or the help center. Publish is the approval.
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