Meeting OS

8:52 a.m. Your 9:00 is a supplier negotiation. You type one line — "Prep: 9am renewal meeting with our logistics supplier, attendees pasted below" — and by 8:54 you're holding the room read: who's attending and what each of them wants, the real agenda underneath the stated one, the two outcomes to push for, the objection you'll most likely hit and your counter, and an opening line. At 10:05 you paste your notes with one word — "Debrief" — and get back the decisions, the actions with owners and dates, and a follow-up email drafted in your voice, ready to send before your next meeting starts. That's this install: two workflows, each triggered with one line, wrapped around every meeting you take.

Prerequisites

• Install 1 done: your voice skill — the debrief drafts the follow-up with it.
• On a personal account: the Anonymizer skill from Install 0.5, for scrubbing what you paste.
• A real meeting on tomorrow's calendar to test on.
• Fifteen minutes.

Build steps

1. Run the prep pack once, on a real meeting. Pick tomorrow's trickiest meeting. Open a chat and paste, filling the brackets:

   Prep me for this meeting.
   
   Meeting: [title, time, length]
   Attendees: [names and roles — or paste the invite]
   Context: [one or two lines — history, what happened last time, anything in play]
   My goal: [what I want out of it — or write "not sure" and propose one]
   
   Give me back, in under 250 words:
   
   1. **The room** — each attendee and what they're likely to want, one line each.
   2. **The real agenda** — what this meeting is actually deciding, beneath the stated agenda.
   3. **Push for** — the one or two outcomes I should drive to, phrased as sentences I could say out loud.
   4. **Watch for** — the most likely derail or objection, and my counter.
   5. **Open with** — a first line that sets the frame.
   

   Read the output against what you know. If it misses the politics, add one more line of context and rerun — the quality of the prep tracks the quality of the two context lines.

2. Save it as the Prep skill. Download the prep workflow file below and upload it in Claude under Settings → Capabilities → Skills, named "Meeting Prep". From now on the trigger is genuinely one line: Prep: [meeting] — [attendees] — [goal].

3. Run the debrief after your next meeting. Within an hour of walking out — while the notes still mean something — paste:

   Debrief this meeting. My notes are below.
   
   Give me:
   
   1. **Decisions made** — one bullet each.
   2. **Actions** — owner, action, deadline. Flag any action that left the room without an owner.
   3. **Open items** — what was raised and not resolved, and who is sitting on it.
   4. **Follow-up email** — drafted in my voice (use my voice skill), addressed to all attendees: one line of thanks at most, then decisions, actions with owners and dates, and the next step. Ready to send.
   
   Notes:
   [PASTE YOUR NOTES]
   

   Rough notes are fine — fragments, half-sentences, names and arrows. The debrief's job is to turn them into a record.

4. Save it as the Debrief skill. Second download below; upload it the same way, named "Meeting Debrief". Trigger: Debrief: plus pasted notes.

5. Close the loop on one real meeting, end to end. Prep line before, debrief line after, follow-up sent within the hour. Run that full cycle once and the habit sets — you'll notice the meetings where you didn't run it.

The Two-Lane note

Lane A (personal account). Everything reaches Claude by paste, and everything work-related goes through the Firewall skill first: attendee names become roles ("their commercial director"), figures become ranges, the client becomes "a client". The prep pack and follow-up come back with those placeholders — you restore the real names in your mail client before sending. Two extra minutes per meeting, fully safe, and the workflows still do the heavy lifting.

Lane B (company Team or Enterprise account). Claude pulls the attendee list from your calendar and the history from the email thread itself — the trigger really is just "Prep my 2pm." The debrief drafts the follow-up with real names and real context, and can reference what was promised in previous threads. This is the gap Lane A makes you feel — and the argument Install 9 turns into a rollout.

Component shipped

Two one-line workflows: Meeting Prep and Meeting Debrief, with the follow-up written in your voice from Install 1. Tomorrow: type "Prep:" two minutes before your first meeting, paste notes with "Debrief" after it — and send the follow-up while everyone else is still promising to.