Prompt Library

Grok Bot Slack prompts that draft, then wait

21 copy-paste prompts

Read channels, map them to priorities, draft replies. Connecting multiple workspaces is not the same as installing Grok Bot as a Slack app. Broad "every message" triggers burn usage.

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

Digests

4 prompts

Priority-mapped Slack digest

1/21

✨ What it does

The Bot reads only [CHANNELS] since yesterday and keeps the items that map to [PRIORITIES DOC]. You reply; it does not post or react.

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, only Slack items in [CHANNELS] that map to [PRIORITIES DOC]. Sources: [CHANNELS], [PRIORITIES]. 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 in Slack. Do not react to messages. Deliverable: Item, permalink, why it matters, whether I owe a reply. Review point: I reply.

💡

Pro tip: Name the channels. "All of Slack" is how you buy a second seat in usage.

Thread I missed

2/21

✨ What it does

The Bot summarizes thread [PERMALINK] into decisions, open asks, and who is waiting on you, with quotes. You reply if needed.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Summarize thread [PERMALINK]: decisions, open asks, who is waiting on me. Sources: That thread 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 reply in the thread. Deliverable: Decisions, asks, my action, quotes. Review point: I reply if needed.

💡

Pro tip: Ask for quotes. Summaries without quotes invent consensus.

#customer-escalations watch

3/21

✨ What it does

The Bot watches [#customer-escalations] for a ticket link plus "needs repro" and builds a pack in this chat. You enable the trigger; it never posts back to Slack on its own.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: When [#customer-escalations] has a ticket link and "needs repro", build a pack here. Never post back without approval. Sources: That channel, [TICKET 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. - Never post back to Slack without approval. Deliverable: Match rule and pack format. Review point: I enable the trigger.

💡

Pro tip: Official event example uses a phrase and a ticket link on purpose.

Quiet-channel audit

4/21

✨ What it does

The Bot lists Slack channels you are in that did not produce a priority item in [14] days. You leave or mute; it 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: List Slack channels I am in that did not produce a priority item in [14] days. Sources: My channel list, [PRIORITIES]. 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 leave channels. Do not mute. Deliverable: Leave / mute / keep, with a reason. Review point: I leave.

💡

Pro tip: Leaving is a human click. The Bot only recommends.

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

Drafts

4 prompts

Draft in my voice, stay in this chat

5/21

✨ What it does

The Bot drafts a Slack reply to [PERMALINK] in your voice and leaves it here. You post it.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Draft a Slack reply to [PERMALINK] in my voice. Do not post. Sources: The thread, style examples. 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 @ extra people. Deliverable: Draft, suggested @, what you assumed. Review point: I post.

💡

Pro tip: Attach two Slack messages you wrote. Otherwise it writes corporate.

Standup I still type

6/21

✨ What it does

The Bot drafts your standup from [TRACKER + CALENDAR + YESTERDAY NOTES] in [STANDUP FORMAT]. You post it to the channel.

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 my standup from [TRACKER + CALENDAR + YESTERDAY NOTES]. Do not post. Sources: [TOOLS], [STANDUP FORMAT]. 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 #standup. Deliverable: Yesterday / today / blocked. Review point: I post.

💡

Pro tip: If the Bot posts as me, people will treat it as me. Keep the last click.

Incident channel clerk

7/21

✨ What it does

The Bot builds a timeline from [#incidents] for [WINDOW], with permalinks, and will not mention anyone. You update the channel.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Build a timeline from [#incidents] for [WINDOW]. Do not @ anyone. Sources: That channel, [STATUS]. 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 @here or @channel. Deliverable: Timeline with permalinks. Review point: I update the channel.

💡

Pro tip: Do not let it @here. That is a page.

Decision capture

8/21

✨ What it does

The Bot extracts decisions from [PERMALINK] and says "no decision" if nobody decided. You write the log.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Extract decisions from [PERMALINK]. If none, say no decision. Sources: The thread, [DECISION LOG 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 post a summary to the thread unless I ask later. Deliverable: Decision or no-decision, owners, dissent quotes. Review point: I write the log.

💡

Pro tip: If no one decided, the output is "no decision" not a fake one.

Connect the right Slack

4 prompts

Plugin vs event vs Slack app

9/21

✨ What it does

The Bot picks a path for [JOB]: Slack plugin to read and draft, a phrase trigger, or neither, and will not install a Slack app into [WORKSPACE] without you. You install the one you chose.

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 [JOB], pick: Slack plugin (read/draft), event trigger (phrase), or neither. Do not install a Slack app into [WORKSPACE] without me. Sources: Settings, my workspaces [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 install into a workspace I did not name. Deliverable: Path, workspace, approval line. Review point: I install.

💡

Pro tip: UseCarly-style note: Slack event wake-up is not installing Grok Bot as a Slack App.

Second workspace

10/21

✨ What it does

The Bot adds [WORKSPACE B] for a read-only digest and keeps it separate from [WORKSPACE A]. You finish the sign-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: Add [WORKSPACE B] for read-only digest. Do not post there. Keep it separate from [WORKSPACE A]. Sources: Settings, both workspaces. 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 in either workspace. Deliverable: Connected (yes/no), what you can read, what you must not write. Review point: I complete OAuth.

💡

Pro tip: Assume one install does not cover the customer Slack and the internal Slack.

Guest or shared-channel caution

11/21

✨ What it does

The Bot lists channels that are shared or external and excludes them from automatic digests unless you name them. You set the include list.

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 channels that are shared/external. Exclude them from automatic digests unless I name them. Sources: Channel 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 join channels. Do not download shared-channel history to /workspace. Deliverable: Internal / shared / unknown, digest include/exclude. Review point: I set the include list.

💡

Pro tip: A digest that includes a shared channel can pull customer Slack into your computer.

Discord or Telegram is not Slack

12/21

✨ What it does

The Bot reminds you there is no official Slack-shaped install for Discord or Telegram, and lists the risk of a community bridge for [PASTE]. You decide whether a browser fallback is enough.

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 I mention Discord or Telegram, remind me there is no official Slack-shaped install and list the risk of a community bridge. Sources: My ask: [PASTE]. 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 install a community bridge without me reading the repo. Deliverable: Official path (none) vs community risk, and a browser fallback. Review point: I decide.

💡

Pro tip: If you need Discord, treat the bridge as untrusted code on this computer.

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

Triggers

3 prompts

Phrase + link only

13/21

✨ What it does

The Bot rewrites [TRIGGER] so it fires only on [PHRASE] plus a [TICKET OR URL] pattern. You save the tighter rule.

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 [TRIGGER] so it fires only on [PHRASE] plus a [TICKET OR URL] pattern. Sources: Current trigger, junk examples. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not keep a broad fallback. Deliverable: New rule, ignored examples. Review point: I save.

💡

Pro tip: Official: avoid every new message.

Never post back automatically

14/21

✨ What it does

The Bot updates the routine so all Slack-triggered work lands in this chat only. You save that 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: All Slack-triggered work posts here only. Add that line to the routine. Sources: The routine. 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 as a test. Deliverable: Updated routine text. Review point: I save.

💡

Pro tip: Auto-post is how a half-repro becomes customer-visible.

Usage cap on Slack jobs

15/21

✨ What it does

The Bot caps Slack-triggered runs at [N] per day and posts "cap hit" here after that. You set N.

You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Cap Slack-triggered runs at [N] per day. After that, post "cap hit" here and stop. Sources: The trigger. 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 raise the cap yourself. Deliverable: Cap and the stop message. Review point: I set N.

💡

Pro tip: A 50-message night is a weekly-meter event.

Make the Slack Bot durable

6 prompts

Slack Bot description

16/21

✨ What it does

The Bot writes a Slack-reader description named [NAME] for [CHANNELS] mapped to [PRIORITIES], with never-post rules. You create that 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 Slack-reader Bot description named [NAME]. Sources: [CHANNELS], [PRIORITIES], [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 react, never @here. Deliverable: Description and daily format. Review point: I create it.

💡

Pro tip: Put the include-list of channels in the description.

Morning Slack routine

17/21

✨ What it does

The Bot writes a weekday routine at [08:15] [TZ] that digests [CHANNELS] mapped to [PRIORITIES], and stops if Slack is down. You enable 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: Weekdays at [08:15] [TZ], Slack digest for [CHANNELS] mapped to [PRIORITIES]. Sources: Those channels. If Slack is down, 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 post to Slack. Deliverable: Routine card. Review point: I enable.

💡

Pro tip: Confirm timezone on the routine card.

What Slack Bots never do

18/21

✨ What it does

The Bot writes a never-do list for Slack Bots: no @here, no DMs as you, no joining new workspaces, no shared-channel dumps. You paste those twelve items.

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 Slack 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 even if the Bot is "just a digest".

Multi-workspace wake-up vs Slack App

19/21

✨ What it does

The Bot lists how to watch [WORKSPACES] without posting, preferring a read-only digest over installing Grok Bot as a Slack app. You connect the workspaces you actually 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 how to watch [WORKSPACES] without posting. Prefer read-only digest. Do not install anything. Sources: [WORKSPACE NAMES], [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. - Do not post. Do not install a Slack App as me. Do not join new workspaces. Deliverable: Per-workspace plan: digest vs ignore. Review point: I connect the ones I want.

💡

Pro tip: Say which workspaces matter. A Bot that reads every workspace will drown you.

Decision extraction, not a novel

20/21

✨ What it does

The Bot lists decisions, owners, and dates from [CHANNEL] since [TIME], and writes "no decision" if nobody decided. You nag the humans.

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 [CHANNEL] since [TIME], list decisions, owners, dates. No decision if none. Sources: That channel. If Slack is down, 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 @ people. Do not add reminders. Deliverable: Table: decision, who, when, link. Review point: I nag humans.

💡

Pro tip: If nobody said a decision, write "no decision". Do not upgrade a maybe.

Shared-channel dump warning

21/21

✨ What it does

The Bot checks whether [CHANNEL] is shared with another company and, if it is, refuses to download the history. You decide whether a short digest is even allowed.

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 whether [CHANNEL] is shared-external. If yes, do not download history. If no, digest only. Sources: Slack channel info. 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 download shared-channel history. Do not post. Deliverable: Shared or not, then digest or stop. Review point: I decide.

💡

Pro tip: If the channel is shared, say so and skip the dump.

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.

Use Settings → Plugins for a Slack connector when you want the Bot to read or draft. Use a Cursor account event integration when you want a message to wake a routine. Those are different flows. Connecting several workspaces is also its own flow. None of that is the same as installing Grok Bot as a Slack app.

If the plugin allows it, it can. These prompts still forbid posting without approval. Auto-replies in customer or incident channels are how you ship a half-finished pack to humans who did not ask.

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 business

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