Meeting Prep Researcher

---
name: meeting-prep
description: Build a one-page brief before an external meeting. Use when the user mentions an upcoming call, meeting, or interview.
---

# Meeting Prep Researcher

When the user has an upcoming external meeting, build a brief from the context they provide (emails, CRM notes, past meeting notes, attendee info).

## Brief format (one page max)

**The meeting** — who, when, their role(s), and the meeting's stated purpose vs. its likely real purpose if different.

**History** — bullet timeline of relevant past interactions from the provided context. Flag open threads ("they asked about pricing on May 3 — never answered").

**What they likely want** — 2-3 bullets inferred from role + history, each labeled (stated) or (inferred).

**Our goals, ranked** — the ONE must-achieve outcome, plus nice-to-haves. Ask the user if the primary goal isn't clear from context.

**Likely friction** — 2-3 objections or hard questions to expect, each with a one-line suggested response drawn from the context.

**Questions to ask** — 3 questions that advance our goal and can't be answered by looking at their website.

**Logistics** — anything actionable: materials to bring, people to loop in, follow-ups still owed to them.

## Rules

- Everything inferred is labeled (inferred) — never present guesses as facts
- Use only provided context; if history is thin, say "no prior context on X" instead of inventing rapport
- If the user hasn't stated their goal for the meeting, ASK — a brief without a goal is trivia

How to use

1. 1Save as .claude/skills/meeting-prep/SKILL.md.
2. 2Paste whatever you have — email threads, CRM exports, past notes. More context, better brief.
3. 3Answer the goal question when asked; it's the difference between a brief and a fact sheet.
4. 4Read the 'open threads' flags carefully — unanswered items from past interactions are meeting gold.

Examples

Pro tips

• Run it 24h before the meeting, not 5 minutes — the 'follow-ups still owed' section often requires action.