USE CASEWorkModerate

It noticed who I was ignoring and booked the call

Jesse’s Chief of Staff reads Gmail, Calendar, Slack/Discord, and sends a 5am summary with fires. Unlike his old script, he can ask it to do something after: it noticed he was ignoring Nate Berkopec, opened SavvyCal, and found a time in both timezones.

Grok·0.0·0 saves·10 uses·via @jessethanley

How it runs

5 steps. Do them in order.

  1. 01In Grok Bot, create a bot named **Jesse** and connect Slack, Gmail, GitHub, Google Calendar, Discord.
  2. 02Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: cos briefer.
  3. 03Give it the context it needs — the accounts, files, and rules specific to your setup — so it can hold the job the way the original build did.
  4. 04Run it each morning; it acts once you approve each step.
  5. 05Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.

What you get

The 5am summary is table stakes; what makes this one different from a script is that Jesse can tell it to act on what it found. Noticing he'd been ignoring a specific person, it opened the scheduling link itself and found a slot that worked in both timezones — one concrete follow-through, not a wall of suggestions.

Prompt

Copy it. Change the names. Keep the job.

Prompt
Role: Chief of Staff briefing. 5am summary, then do the follow-through I ask.

Mission: Every morning at 5am: calendar, inbox, Slack/Discord. Flag fires. After I read it, I may tell you to book, draft, or nudge. You do that one thing and stop.

Tools: Gmail, Google Calendar, Slack or Discord, browser for scheduling links (SavvyCal, Calendly).

What good looks like:
- One page: fires, today’s map, people I am ignoring, a single suggested next action.
- If I say “book him”, open the scheduling link, find an overlap in both timezones, and wait for me to confirm before you lock it.
- No novel. I should read this before coffee.

Never, without asking: send email, accept a meeting, or book a slot. Never summarise private DMs as team decisions.

Stop if a “fire” is legal/money and you do not have the thread — link it, do not paraphrase.
Use withGrok

via @jessethanley

Tips

  • ·Reconstructed from @jessethanley's published Grok Bot build. Adapt the connected accounts and context to your own stack — the prompt is a Curator reconstruction, not the author's original text.
  • ·daily
  • ·acts-with-approval

Related setups

Same category. Different job.

More in Work

Tomorrow’s meetings, one phone-readable page each

Krista’s daily meeting-prep routine pulls Salesforce, Gmail, Slack, Granola, and Gong into a short, skimmable brief she can read on her phone. New meetings get light research; existing ones get last-touch and the ask.

Work·Advanced·0 saves
Setup

Dump a messy ask, get plain-language results back

Kun Chen’s Firstmate setup is a single Grok Bot you talk to for everything. It creates, delegates, and juggles the other bots, and for bigger work it spins Cursor cloud agents, then brings the result back in plain language so you never have to chat the specialists.

Work·Moderate·0 saves
Setup