Get briefed on every meeting tomorrow

Founder with 6-10 external meetings/day · Assemble in ~10 min; full batch brief for 6-10 meetings in 5-12 min once installed.

Founder opsEdit flowon X◆ new (unverified) 90

step 1ready

Pull tomorrow's calendar events

google-calendar

step 2ready

Triage: skip internal, flag externals

calendar

step 3connector

Surface recent email threads per attendee

⚡ bring your own tool

step 4ready

Generate per-meeting briefing card

meeting-prep10 alts

step 5partial

Enrich with past meeting transcripts

meeting-analyzer

step 6ready

Compile tomorrow's briefing dashboard

meeting-prep10 alts

Did this recipe work for you?

What you get

▸Per-meeting brief card for every external event on tomorrow's calendar (who, why, context, 3+ questions, one objective)
▸Chronological tomorrow briefing dashboard — one file to read tonight before bed
▸Email-sourced attendee context map (last threads per contact)
▸Transcript-grounded history flags where past commitments or open loops exist

tools: Gmail/Google Calendar MCP — free via existing harness auth; Granola/Otter/Fireflies for transcripts if used (existing subscription)

tokens: ~$0.30-1.20 per run for a 6-10 meeting day

≈ $3-10/mo at daily use (tokens only; no additional SaaS required beyond calendar + email already in use)

What stays yours

· Supply past meeting transcript files for attendees when richer history is needed — automatic transcript retrieval is not wired
· Review and personalise each brief card before high-stakes meetings; the agent works from available data and may miss context that lives only in your head
· Decide which internal meetings to include if the triage filter is too aggressive or too permissive for your team setup

The problem

When I have a dense external calendar tomorrow, I want every meeting prepared in one batch run — attendee context, relationship history, stated goals, and 3+ sharp questions per meeting — so I walk into every conversation ready and never waste anyone's time ramping up.

Cybernetic layers

Memorypartial

No persistent relationship-memory artifact in the pool. Relationship context (open commitments, past conversation tone, what you promised) lives in email threads and transcripts fetched ad-hoc each run. A CRM or local contacts file would make this richer; not yet a library artifact.

Background-schedulingbyo

The recipe runs on-demand. To fire automatically each evening for next-day prep, wire it to a Claude Code cron (scripts/gbrain-local.sh pattern) or a scheduled cloud agent. No harvested scheduler artifact covers this use case yet.

Harnessready

Claude Code is the runtime. Drop each ready skill into ~/.claude/skills/ and invoke the recipe by name. Gmail/Google Calendar MCPs must be pre-authenticated in the harness.

Click any step to see what fills it — and the ranked alternatives you can swap in.