---
name: partner-meeting-prep
version: 1.0.0
description: "One-page brief before any sponsor or stakeholder meeting. Pull recent emails, last meeting's notes, and the partner's recent press into a single document with the three asks worth making. Triggers: 'prep me for [meeting]', 'meeting brief', 'partner prep', 'I'm meeting [name] tomorrow'."
tools: ["composio:GMAIL_FETCH_EMAILS", "composio:GOOGLEDRIVE_SEARCH", "composio:LINKEDIN_SEARCH_PEOPLE", "composio:GOOGLECALENDAR_LIST_EVENTS"]
scripts: ["scripts/meeting_prep.py"]
---

# Partner Meeting Prep

## Purpose

The difference between a meeting that earns the next meeting and one that drifts into pleasantries is preparation. Most sports business pros run too hot to do real prep, so they walk in with stale context and lose the room. This skill builds a one-page briefing in under 90 seconds: who you are meeting, what their world looks like this week, what you last discussed, and the three asks that move the relationship forward. Bring this on your phone or print it. Either way, you walk in ready.

## When to Use

- Sponsor pitch or renewal meeting
- Quarterly business review with an existing partner
- First meeting with a prospective athlete representative or agent
- Board-prep meeting with a sponsor stakeholder
- Any meeting where the relationship matters more than the agenda

## When NOT to Use

- Internal staff one-on-ones (overkill)
- Standing meetings with the same agenda each week
- Cold prospecting calls. Use the outreach skill instead

## Inputs

| Input | Required | Default | Notes |
|---|---|---|---|
| `--with` | yes | | Person and company, like "Sara Kim, Acme Brands" |
| `--meeting-time` | no | next match | When the meeting is, for calendar pull |
| `--lookback-days` | no | 90 | Email and notes lookback window |
| `--include-press` | no | true | Pull recent press mentions |
| `--include-linkedin` | no | true | Pull recent LinkedIn activity |
| `--output` | no | `prep-{name}-{date}.md` | Output path |
| `--dry-run` | no | false | Run on fixture data |

## Quick Reference

**The one-page structure:**

| Section | What goes here | Source |
|---|---|---|
| Who | Name, title, company, where they came from | LinkedIn, internal CRM |
| Their week | One sentence each on company news, recent press, LinkedIn posts | Press, LinkedIn, Google News |
| Our history | Last meeting date, what was agreed, what shipped, what slipped | Calendar, internal notes |
| Open threads | Any email threads still pending a reply, with last status | Gmail |
| Three asks | The specific moves you want from this meeting | You, drafted by the skill |
| What they will likely ask | Best guesses based on email and press patterns | Pattern matching |
| Their constraints | What you know about budget, timing, internal politics | CRM notes |

**Three-asks framework:**

The brief always proposes exactly three asks, in this order:

1. **The relationship ask.** Something small that signals you take them seriously (a 30-second update, a specific intro)
2. **The progression ask.** The next concrete step in the partnership (proposal, pilot, expanded scope)
3. **The strategic ask.** A bigger question that you want them thinking about even if not deciding today (multi-year, category exclusivity, executive sponsor change)

If you cannot draft three asks before the meeting, it is not a meeting worth taking yet.

## Workflow by Task

### Task 1: Standard partner-meeting prep

```bash
python skills/partner-meeting-prep/scripts/meeting_prep.py \
  --with "Sara Kim, Acme Brands"
```

Or ask Claude: `"Prep me for tomorrow's meeting with Sara Kim at Acme Brands."`

### Task 2: First-time meeting (no history)

```bash
python skills/partner-meeting-prep/scripts/meeting_prep.py \
  --with "Marcus Holloway, NextWave Media" --lookback-days 0
```

The skill auto-detects no prior history and adds an "outreach hypothesis" section instead of "our history."

### Task 3: Renewal-meeting prep

```bash
python skills/partner-meeting-prep/scripts/meeting_prep.py \
  --with "Sara Kim, Acme Brands" --include-press true
```

For renewal prep, the skill weights the three-asks heavier on multi-year and category exclusivity.

## Output Format

Markdown, designed to print on a single sheet. Print-friendly even on a phone. Every section is one to three lines.

## Principles

- **One page or it does not work.** Anything longer is a research dump and will not be read in the elevator.
- **Three asks, exactly.** Two is incomplete. Four is unfocused. Force the discipline.
- **Recent over deep.** What happened this week beats what happened last year, every time.
- **The brief is for you, not for them.** It can be opinionated, it can speculate. It is your prep, not a public document.
- **Update, do not regenerate.** Keep the same brief and add to it through the relationship. The pattern over time is itself signal.

## What to Avoid

- **A two-page brief.** Consequence: you skim the wrong half before the meeting and miss the actual ask
- **Stale press from 2024.** Consequence: you reference something they already moved on from and look out of touch
- **No three-asks discipline.** Consequence: you walk in hoping a good vibe leads somewhere. It rarely does
- **Rebuilding from scratch every meeting.** Consequence: you lose the longitudinal pattern. The brief is a living document
- **Sending the brief to the partner.** This is your prep. Never share it. Especially never share the "what they will likely ask" section

## Tool Integration

| Action | Safety Tier | Used For |
|---|---|---|
| `GMAIL_FETCH_EMAILS` | T1 Read | Pull last 90 days of email with this person |
| `GOOGLEDRIVE_SEARCH` | T1 Read | Find last meeting's notes |
| `LINKEDIN_SEARCH_PEOPLE` | T1 Read | Recent LinkedIn activity |
| `GOOGLECALENDAR_LIST_EVENTS` | T1 Read | Confirm meeting time and prior meeting dates |

The skill never sends, drafts, or modifies anything. Read-only by design.

## Resources

- Sample meeting prep: `examples/sample-prep.md`
- CRM notes template: `templates/partner-notes.md`