Grok Bot chief of staff prompts that map to your priorities
Official CoS use case: only items that map to a priorities doc. Source, why it matters, next step, whether you owe a decision. No messages sent, no meetings changed.
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.
The daily digest
4 promptsPriority-mapped morning digest
1/21✨ What it does
The Bot reviews activity since yesterday across [SLACK], [INBOX], [CALENDAR], and [MEETING NOTES], and returns only items that map to [PRIORITIES DOC]. You act on the digest; 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: Review activity since yesterday across approved channels. Return only items that map to [PRIORITIES DOC]. Sources: [SLACK], [INBOX], [CALENDAR], [MEETING NOTES], [PRIORITIES 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 send messages or change meetings. Deliverable: For each item: source, why it matters, proposed next step, whether I owe a decision. Review point: Digest here. I act.
Pro tip: Tune it by marking what was useful. Then schedule the digest for a time you actually read it.
What I owe by 5pm
2/21✨ What it does
The Bot lists commitments you made in the last [7] days that are still open and due by [DATE], quoting the original promise and linking the source. You decide what is actually a promise; the Bot does not chase anyone.
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 commitments I made in the last [7] days that are still open and due by [DATE]. Sources: [EMAIL SENT], [SLACK], [MEETING NOTES], [TASK 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 mark tasks done. Do not chase anyone. Deliverable: Promise (quoted), source link, due if stated, suggested next step. Review point: I decide what is actually a promise.
Pro tip: Ask it to quote the promise. Paraphrased "you should probably" lists are not commitments.
Noise vs signal calibration
3/21✨ What it does
The Bot takes yesterday's digest with your useful / noise marks and rewrites its filter rules, then replays yesterday under the new rules against [PRIORITIES DOC]. You approve the rules before any schedule changes.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Here is yesterday's digest with my marks: useful / noise. Rewrite your filter rules. Sources: The marked digest I paste, plus [PRIORITIES 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 change the routine schedule until I approve the new rules. Deliverable: New include / exclude rules, and a replay of yesterday under the new rules. Review point: I approve the rules, then you may update the skill.
Pro tip: Official docs: tune the Bot by marking what was useful and what was noise.
Week-ahead calendar brief
4/21✨ What it does
The Bot briefs next week from [CALENDAR] and only keeps events that need prep or a decision, noting prep you still lack. You block the time; the Bot does not create, move, or decline events.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Brief next week from [CALENDAR]. Only events that need prep or a decision. Sources: [CALENDAR], [PRIORITIES], [DECK FOLDER], [OPEN THREADS]. 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, move, or decline events. Deliverable: Event, why it matters, prep I still lack, decision at risk. Review point: I block prep time.
Pro tip: Ask "what needs prep" not "list my meetings". You already have a calendar app.
Prompts get you started. Tutorials level you up.
A growing library of 300+ hands-on AI tutorials. New tutorials added every week.
Follow-ups and meetings
4 promptsDraft follow-ups I still send
5/21✨ What it does
The Bot drafts a follow-up for [MEETING] to [PEOPLE] from [NOTES OR TRANSCRIPT] and your style examples, including anything you promised. 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: Draft a follow-up for [MEETING] to [PEOPLE]. I will send it. Sources: [NOTES OR TRANSCRIPT], [DECK], style examples attached. 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 add calendar holds. Deliverable: Subject, body, open questions, and anything I promised. Review point: I send.
Pro tip: Attach two emails you have sent. CoS Bots otherwise write chief-of-staff fanfiction.
Prep a 1:1 in 10 minutes
6/21✨ What it does
The Bot preps your 1:1 with [NAME] on [DATE] from [LAST 1:1 NOTES], [SLACK DM], and [EMAIL], with open loops and a five-item agenda. You run the 1:1; the Bot does not message 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: Prep my 1:1 with [NAME] on [DATE]. Sources: [LAST 1:1 NOTES], [SLACK DM], [EMAIL], [THEIR GOALS 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 message them. Deliverable: Open loops, suggested agenda (5 items), landmines, links. Review point: I run the 1:1.
Pro tip: Point at the person's last three threads, not "everything about Jane".
Staff meeting packet
7/21✨ What it does
The Bot assembles a packet for [STAFF MEETING] from [NAMED DOCS], [METRICS SHEET], and last week's notes, and flags what is stale or missing. You share it; the Bot does not email it or create a meeting.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Assemble a packet for [STAFF MEETING] from [NAMED DOCS]. Sources: [DOC LIST], [METRICS SHEET], [LAST WEEK NOTES]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not email the packet or create a meeting. Deliverable: Packet file, what is stale, what is missing. Review point: I share it.
Pro tip: Name the exact files. "Find the latest strategy doc" will pick a 2024 draft.
Sit in when I cannot
8/21✨ What it does
The Bot joins [LINK] at [TIME TZ] as [BOT NAME], announces it is a note-taking Bot, and returns decisions, owners, and what you owe. You send follow-ups; the Bot does not speak for you or accept action 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: Join [LINK] at [TIME TZ] as [BOT NAME]. Announce you are a note-taking Bot. Do not speak for me. Sources: [AGENDA], [PRIOR NOTES]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not accept action items for me. Do not share notes outside this conversation. Deliverable: Decisions, owners, timestamps, what I owe. Review point: I send follow-ups.
Pro tip: Field case from SpaceXAI staff: the Bot joins, announces itself, takes notes.
People, travel, and ops
4 promptsTravel options, last click is mine
9/21✨ What it does
The Bot finds flights for [ROUTE] on [DATES] under [BUDGET] given [CONSTRAINTS], with times, price, stops, and a screenshot of the fare. You buy; the Bot does not enter payment.
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 flights for [ROUTE] on [DATES] under [BUDGET], [CONSTRAINTS]. Do not book. Sources: [AIRLINE OR OTA SITES] on the cloud browser, my calendar for conflicts. 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 purchase. Do not enter payment. Hand me the computer at checkout. Deliverable: Options table: times, price, stops, refund rules, screenshot of the fare. Review point: I buy.
Pro tip: Honest field note: near-miss is normal. The last click needs you. Put a price cap in the brief.
Vendor or contractor quote pack
10/21✨ What it does
The Bot collects quotes for [JOB] from [VENDORS OR INBOX], compares them to your must-haves and [BUDGET], and drafts a yes and a no note. You send the yes; the Bot does not accept a quote or pay a deposit.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Collect quotes for [JOB] from [VENDORS OR INBOX]. Compare. Recommend one. Sources: [INBOX], [ATTACHED RFPS], [BUDGET]. 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 accept a quote or pay a deposit. Deliverable: Vendor, price, gaps vs must-haves, risk, draft "yes" and "no" notes. Review point: I send the yes.
Pro tip: Tell it the must-haves. Otherwise it picks the pretty PDF.
Subscription and tool audit
11/21✨ What it does
The Bot lists paid tools from [INBOX + BILLING] for the last [90] days and flags ones that look unused, with a keep / review / cancel note. You cancel; the Bot does not chat with a vendor.
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 paid tools and subs from [INBOX + BILLING] for the last [90] days. Flag unused. Sources: [INBOX], [CARD STATEMENTS IF ATTACHED], [SSO APP 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 cancel, downgrade, or chat with a vendor. Deliverable: Tool, last used if known, monthly cost, keep / review / cancel recommendation. Review point: I cancel.
Pro tip: Cancellations are irreversible enough to always need you.
Visitor or guest logistics
12/21✨ What it does
The Bot plans [GUEST] visit on [DATES] in [CITY] given [CONSTRAINTS], with itinerary options and a draft guest email. You book and you send; the Bot does not reserve hotels or email the guest.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Plan [GUEST] visit on [DATES] in [CITY] given [CONSTRAINTS]. Sources: [CALENDAR], [DIETARY NOTES], [VENUE LIST], maps 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 book hotels or restaurants. Do not email the guest. Deliverable: Itinerary options, holds I need to make, draft guest email. Review point: I book and I send.
Pro tip: Same rule as flights. Research is free. Reservations wait.
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.
Writing in your voice
3 promptsInvestor or board update draft
13/21✨ What it does
The Bot drafts the [MONTHLY] update from [METRICS SOURCE] and [HIGHLIGHTS I PASTE], in the prior format, and writes TBD where a number is missing. You send it; the Bot does not email investors.
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 the [MONTHLY] update from [METRICS SOURCE] and [HIGHLIGHTS I PASTE]. Sources: [DASHBOARD], [FINANCE SHEET], [PRIOR UPDATE]. 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 investors. Do not invent metrics. If a number is missing, write TBD. Deliverable: Update in the prior format, plus a TBD list. Review point: I send.
Pro tip: Lock the metric sources. CoS Bots love a confident number from a random screenshot.
Decision memo from a messy thread
14/21✨ What it does
The Bot writes a one-page memo for [DECISION] from [SLACK THREAD], [EMAIL], and [DOC], with options, a recommendation, and risks. You decide; the Bot does not announce it or @ people.
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 decision memo for [DECISION] from the thread I point you at. Sources: [SLACK THREAD], [EMAIL], [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 announce a decision. Do not @ people. Deliverable: Context, options, recommendation, risks, open questions, sources. Review point: I decide.
Pro tip: Ask for options, recommendation, and what would change it. Not a recap.
Say no, kindly, in my voice
15/21✨ What it does
The Bot drafts a short, kind no to [REQUEST] that stays true to [PRIORITIES], in three tones of 80 words or less, using two "no" emails you have sent. You send one.
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 no to [REQUEST] that is kind, short, and true to [PRIORITIES]. Sources: The request, [PRIORITIES DOC], two "no" emails I have sent. 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. Deliverable: Three tone variants, 80 words or less. Review point: I send one.
Pro tip: This is how a CoS Bot earns its keep: protecting time, not summarizing Slack.
Make the CoS durable
6 promptsCoS Bot description I can paste
16/21✨ What it does
The Bot writes a chief of staff profile named [NAME], covering [PRIORITIES], [TOOLS], a daily output format, and a never-send line for your [REVIEW WINDOW, E.G. 8AM]. You paste it into Create your 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: Write a Bot description for a chief of staff named [NAME]. Sources: [PRIORITIES], [TOOLS], [REVIEW WINDOW, E.G. 8AM]. 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 send, never change meetings, never spend. Deliverable: Name, job, sources, daily output format, never-do, tuning instructions. Review point: I paste it into Create your own.
Pro tip: Put the priorities doc and the approval line in the description, not only in chat.
Turn the digest into a skill
17/21✨ What it does
The Bot saves this digest process as a skill called "Daily CoS digest", including inputs, format, approvals, and what to do when a source is empty. You test it on a second morning before scheduling.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Save this digest process as a skill called "Daily CoS digest". Sources: This conversation and [PRIORITIES 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. - External messages always need approval. Deliverable: Skill: when, inputs, steps, format, approvals, failure behavior. Review point: I test on a second morning before scheduling.
Pro tip: Include the no-data policy: report failure, do not reuse yesterday.
When I am away, pause rules
18/21✨ What it does
The Bot writes away-mode rules: if you do not reply for [N] days, which routines pause and which [MUST-KEEP JOBS] stay, plus the message it will post. You confirm before anything is paused.
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 away-mode rules: if I do not reply for [N] days, pause these routines and keep these. Sources: Current routine list, [MUST-KEEP JOBS]. 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 anything until I confirm. Deliverable: Keep / pause table and the message you will post when you enter away mode. Review point: I confirm, then you may store it as a skill.
Pro tip: Official: Grok Bot may pause routines after a long time away. Write your preference explicitly.
Debbie-style first CoS prompt
19/21✨ What it does
The Bot writes a standing one-page digest format—decisions needed, people waiting, calendar collisions, money moving—from [CALENDAR], [INBOX], [SLACK], and [TASKS], plus a sample from today. You adopt the format; the Bot does not reply to anyone or move 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: Write my standing CoS digest format: decisions needed, people waiting, calendar collisions, money moving. Cap at one page. Sources: [CALENDAR], [INBOX], [SLACK], [TASKS]. 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 anyone. Do not move meetings. Deliverable: The format plus a sample from today. Review point: I adopt the format.
Pro tip: If the digest is longer than a page, you will not read it. Cap it.
Reorganize the roster
20/21✨ What it does
The Bot looks at the Bots you paste in [PASTE LIST] and proposes a cleaner roster of [N] names with one job each, based on [NOTES] about what actually got used. You change the roster; the Bot does not create, rename, or delete Bots.
You are a Grok Bot on my shared cloud computer (browser, files, terminal). This is a standing job, not a grok.com chat. Outcome: Look at my current Bots [PASTE LIST] and propose a cleaner roster of [N] names with one job each. Sources: The list I paste, what actually got used this week: [NOTES]. Constraints: - Do not send messages, enroll anyone, make payments, delete records, or change production settings. - If a login, 2FA, passkey, or CAPTCHA appears, ask me to take over the computer. Never ask me to paste a password or API key into chat. - If a source is missing or stale, say so. Do not invent numbers or contacts. - Do not create, rename, or delete Bots. Deliverable: Keep / merge / kill, plus new names. Review point: I change the roster.
Pro tip: Focused Bots beat one catch-all. Official docs: one primary job.
Away-mode pack
21/21✨ What it does
The Bot writes, for [DATES AWAY], what it may collect, what must wait, and what pages you at [CHANNEL], using [CALENDAR], [ON-CALL RULES], and [CUSTOMERS IN FLIGHT]. You turn away-mode on; the Bot does not message customers unless the rule matches.
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 [DATES AWAY], write what the CoS Bot may collect vs what must wait vs what pages me at [CHANNEL]. Sources: [CALENDAR], [ON-CALL RULES], [CUSTOMERS IN FLIGHT]. 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 message customers. Do not page me unless the rule matches. Deliverable: Three buckets and the page-me sentence. Review point: I turn away-mode on.
Pro tip: Write the "page me" rule or everything becomes urgent.
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