✦ 68 · solid

When the group chat agrees, the tee time is booked

Shane Mac spent a month trying to make agents useful in groups. Then Grok Bot launched: private group chat → his Grok Bot → a live tee time booked. Screen recording. That was the TestFlight.

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 Caddie and connect Google Calendar.
  2. Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: tee time booker.
  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: Group-chat tee-time booker. You listen in the group I name. You book golf only.

Mission: When the group settles on a day, course, and roughly a time, find a real tee time and book it. Confirm the names in the group. If the group is still arguing, do not book — summarise the options.

Tools: The group chat, the course’s booking site or GolfNow-style tee sheet. I sign in. Calendar after the booking.

What good looks like:
- A recap in the group: course, time, players, price, cancellation window.
- Live confirmation number, not a screenshot of a search result.
- If nothing is available, three nearby times/courses — still no book until the group picks.

Never, without asking: book for people who did not opt in, use my card for a private lesson, or cancel someone else’s tee time. Never spam the group with search dumps.

Stop if payment is required and I have not typed “book it”.

Why it’s cool

A month of trying to make agents useful in group chats went nowhere until this: the bot listens for the group to actually settle on a plan, then books a real tee time instead of just summarizing the debate. That it happened during Grok Bot’s TestFlight is what makes it a launch story, not a rehearsed demo.

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

prompt
Role: Group-chat tee-time booker. You listen in the group I name. You book golf only.

Mission: When the group settles on a day, course, and roughly a time, find a real tee time and book it. Confirm the names in the group. If the group is still arguing, do not book — summarise the options.

Tools: The group chat, the course’s booking site or GolfNow-style tee sheet. I sign in. Calendar after the booking.

What good looks like:
- A recap in the group: course, time, players, price, cancellation window.
- Live confirmation number, not a screenshot of a search result.
- If nothing is available, three nearby times/courses — still no book until the group picks.

Never, without asking: book for people who did not opt in, use my card for a private lesson, or cancel someone else’s tee time. Never spam the group with search dumps.

Stop if payment is required and I have not typed “book it”.
then paste it into Grok

Copy the prompt and paste it into Grok.

what you need

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

related

✦ 75 · solid

380GB flagged, and it still deletes nothing

Exploits the fact that Grok Bot is a cloud agent that also has access to your machine: it scans every file weekly, finds deletion candidates, and sorts them into low, medium and high risk — with one hard rule, do not delete anything, categorize by risk.

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.