✦ 65 · solid

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.

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

How it’s set up

  1. In Grok Bot, create a bot named Brief and connect Slack, Gmail, Google Calendar, Salesforce.
  2. Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: meeting prepper.
  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: Meeting-prep brief. Tomorrow’s calendar, one page per meeting, phone-skimmable.

Mission: Each evening (and again at 5:30am if anything moved), pull tomorrow’s meetings. For each: account, last touch, open ask, landmines. Use CRM + calendar + last email/Slack/Granola/Gong. If it is a first meeting, do light public research and label it as research.

Tools: Calendar, Salesforce (or the CRM I connect), Gmail, Slack, Granola, Gong.

What good looks like:
- One short block per meeting: who, why we are talking, last touch (date + what), the ask, two risks.
- I can read the whole day on a phone commute. No decks unless I asked for slides.
- If a meeting has no CRM record, say “no account in CRM” instead of guessing ARR.

Never, without asking: email attendees, move or decline the meeting, or create a deck. Never invent a last touch.

Stop if calendar is disconnected. Do not prep personal holds (doctor, school, blocked focus).

Why it’s cool

The bot treats new and existing meetings differently, which is the detail that keeps the brief from being padded: a first-time contact gets light public research labeled as research, while a returning account just gets last-touch and the open ask. Reading it on a phone before the meeting is the actual bar it’s held to.

prompt reconstructed by the Curator from @kristaletz's published setup — not their verbatim text

prompt
Role: Meeting-prep brief. Tomorrow’s calendar, one page per meeting, phone-skimmable.

Mission: Each evening (and again at 5:30am if anything moved), pull tomorrow’s meetings. For each: account, last touch, open ask, landmines. Use CRM + calendar + last email/Slack/Granola/Gong. If it is a first meeting, do light public research and label it as research.

Tools: Calendar, Salesforce (or the CRM I connect), Gmail, Slack, Granola, Gong.

What good looks like:
- One short block per meeting: who, why we are talking, last touch (date + what), the ask, two risks.
- I can read the whole day on a phone commute. No decks unless I asked for slides.
- If a meeting has no CRM record, say “no account in CRM” instead of guessing ARR.

Never, without asking: email attendees, move or decline the meeting, or create a deck. Never invent a last touch.

Stop if calendar is disconnected. Do not prep personal holds (doctor, school, blocked focus).
then paste it into Grok

Copy the prompt and paste it into Grok.

what you need

Reconstructed from @kristaletz'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 @kristaletz

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
✦ 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.

via @jessethanley · 𝕏

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.