THE MEETING PREP ENGINE

Most meetings are bad because no one prepped. The 10 minutes of prep would save the 60 minutes of meeting. Nobody does the 10. This skill does the 10 in 4.

THE PROBLEM

You walk into the meeting. You haven't read the deck. You haven't looked up who the new person on the call is. You don't have a question ready. The meeting goes the meeting's way, not your way.

This isn't laziness — it's that prep is invisible work. Nobody thanks you for it. So it slips. Until the day you walk into a meeting that mattered, unprepared, and watch it cost you.

THE SKILL

You give Claude:

Meeting title + time
Attendee names + companies/roles
Agenda link or topic
What you want out of this (1 line)

Claude returns:

Attendee briefs (background on each person, recent moves, conversational hooks)
3 smart questions tailored to the meeting goal
Suggested agenda if one wasn't shared
Pre-meeting opener — your first 30 seconds, scripted
Follow-up email template — already drafted, ready to send post-meeting

4 minutes of prep. Different meeting.

3 THINGS YOU CAN'T SKIP

1. State the goal in one line. "Get aligned on Q2 budget" is a goal. "Discuss the project" is not. The skill gets sharp when the goal is sharp.

2. Read the attendee briefs out loud. You retain 5x more when you say it. The "huh, that's interesting" moment is what makes you sound prepared in the meeting.

3. Pre-write the follow-up email. Most meetings die because nobody captures the next step. The skill drafts the follow-up before the meeting — you just fill in 2 details after.

INSTALL

Standard. Highly recommended: enable web search so the skill can pull recent context on attendees.

THE FULL SKILL FILE

---
name: meeting-prep-engine
description: Pre-meeting research and structuring skill. Inputs: meeting title, attendees, agenda or topic, the user's goal. Outputs: attendee briefs (with conversational hooks), 3 tailored questions, suggested agenda if missing, opening 30-second script, and a pre-drafted follow-up email template.
when_to_use: User mentions an upcoming meeting and asks for prep, says "help me prep for X meeting," or pastes a calendar invite.
---

# The Meeting Prep Engine

You prep meetings well so they go well. Specific. Tactical. Not generic "meeting hygiene" advice.

## Inputs
1. Meeting title + time
2. Attendee names + companies/roles
3. Agenda or topic
4. User's goal in 1 line ("Get aligned on Q2 budget" — not "discuss the project")

If goal is vague, push: *"What's the one outcome that would make this meeting worth attending?"*

## Output structure

### 👥 ATTENDEE BRIEFS

For each attendee:

[Name] · [Role] · [Company]

Background: [1 sentence]
Recent: [anything from web search — recent role change, news, posts]
Conversational hook: [1 thing to mention, not generic]
Likely position on this meeting's topic: [if predictable]


If user can't share attendee details, ask for at least name + company so search can run.

### ❓ 3 SMART QUESTIONS

Tailored to the user's stated goal. Format:

[Question that surfaces hidden context]
[Question that tests an assumption you're making]
[Question that creates a decision moment]


Avoid generic ("what are your thoughts on..."). Specific to the people in the room.

### 📋 SUGGESTED AGENDA (if missing)

3–5 bullets, each with a time estimate. Total ≤ meeting length.

### 🎤 OPENER (first 30 seconds)

Script the user's opening, in their voice. Format:

"[Acknowledgment of attendees], [framing of why we're here], [the goal stated openly], [proposed agenda]."


Aim for 30 seconds spoken — about 75 words.

### ✉️ FOLLOW-UP EMAIL DRAFT

Pre-write the post-meeting summary email. Leave 2 placeholders:
- `[KEY DECISIONS — fill after meeting]`
- `[NEXT STEPS — fill after meeting]`

Subject line, greeting, body, sign-off all done. User just fills the placeholders and hits send.

## What NOT to do

- Don't recommend "review the deck" — that's obvious
- Don't suggest the user "be more confident" or other fluff
- Don't give 5 questions when 3 will do
- Don't write generic openers — script the actual sentences
- Don't fabricate attendee details. If web search returns nothing, say so. Better to say "couldn't find recent context on X" than make it up.

## Delivery
End with: *"Prep complete. Drop the follow-up email back here after the meeting and I'll fill in the rest."*

SAFETY CHECK

Same as Day 1.

WHAT'S NEXT

Day 79 of 100. Pair with Day 48 — The Meeting Notes-to-Actions (post-meeting half of the workflow) and Day 49 — The Personal CRM (track who you met with).