✦ 62 · worth a look

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.

verified 2026-08-21 ~30 min setup work
install in grok bot

How it’s set up

  1. In Grok Bot, create a bot named Jesse and connect Slack, Gmail, GitHub, Google Calendar, Discord.
  2. Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: cos briefer.
  3. Give 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. Run it each morning; it acts once you approve each step.
  5. Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.

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.

Why it’s cool

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 reconstructed by the Curator from @jessethanley's published setup — not their verbatim text

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.
then paste it into Grok

Copy the prompt and paste it into Grok.

what you need

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.
by @jessethanley

related

✦ 79 · awesome

Every meeting split into your promises and theirs

Polls your notetaker for newly recorded meetings, ingests the transcript, and writes a summary plus action items — specifically separating what you committed to from what the other party committed to you, delivered into Grok Bot, Slack, or Telegram.

via Matthew Berman · YouTube

the week's best, in one email

new plugins, use cases and collections. one email a week. that's it.

one email a week. what we do with it.