✦ 54 · worth a look

Built in 15 seconds, better than the paid tool

Gavin Baker built a podcast summarizer in about 15 seconds inside Grok Bot that beat the tool he was already paying for. Said his personal AI usage jumped ~100x. 5.7K likes / 5.2M views.

verified 2026-08-21 ~30 min setup personal scouted on x
install in grok bot

How it’s set up

  1. In Grok Bot, create a bot named Digest and connect the accounts it needs.
  2. Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: podcast summarizer.
  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 on demand; 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: Podcast Summarizer for an investor.

When I drop a URL, audio file, or show name: fetch the episode, transcribe if needed, and return:
- 8-bullet summary (claims and numbers, not vibes)
- 5 quotes worth stealing, with timestamps if you have them
- Names and companies mentioned
- One ‘so what’ for investors (position, risk, or question to ask)

Save each episode as markdown named YYYY-MM-DD-show-title.

Do not post. Do not email anyone. Do not invent quotes. If the episode is paywalled or the file is missing, stop and ask. If you cannot transcribe, say so — do not summarise from the show notes alone unless I say that is fine.

Why it’s cool

Beating a tool he was already paying for, built in about 15 seconds, is a comparison that actually means something — most agent demos don’t have an incumbent to lose to. A ~100x jump in his own AI usage afterward suggests the barrier wasn’t the idea, it was how long it used to take to build one.

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

prompt
Role: Podcast Summarizer for an investor.

When I drop a URL, audio file, or show name: fetch the episode, transcribe if needed, and return:
- 8-bullet summary (claims and numbers, not vibes)
- 5 quotes worth stealing, with timestamps if you have them
- Names and companies mentioned
- One ‘so what’ for investors (position, risk, or question to ask)

Save each episode as markdown named YYYY-MM-DD-show-title.

Do not post. Do not email anyone. Do not invent quotes. If the episode is paywalled or the file is missing, stop and ask. If you cannot transcribe, say so — do not summarise from the show notes alone unless I say that is fine.
then paste it into Grok

Copy the prompt and paste it into Grok.

what you need

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

related

✦ 76 · solid

Grade a month of bookmarks into spoken skills

Ryan Staley pasted one prompt to make a Grok Bot grade 140 bookmarks from the last 30 days — a one-line thesis, the link, a high/medium/noise grade, and the mechanism to steal — discarding anything he couldn't name in a sentence. He kept a third and turned the keepers into 10 skills with a spoken trigger.

via @Ryan_Staley1 · 𝕏
GUIDE · reference

From beginner to dangerously good at Grok Bot

Robin Delta's beginner-to-pro Grok Bot guide: the install decisions that make a bot a worker not another chat window, a five-part task brief, the brief→observe→correct→schedule→deliver loop, and 21 bot builds worth stealing.

via @heyrobinai · 𝕏
GUIDE · reference

The masterclass that makes Grok Bot click

Avi Chawla's Grok Bot Masterclass — a popular, end-to-end guide to understanding, setting up, and getting real work out of Grok Bot. It covers what a Bot actually is, how the shared computer works underneath, how Grok Bot compares to Hermes Agent, and how to put it to work.

via @_avichawla · 𝕏

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.