---
name: meeting-prep-brief
description: Use when the user asks to prep for a meeting, call, or interview, asks "who am I meeting today", or when a routine runs before calendar events. Builds a one-page brief per meeting with attendee backgrounds, shared history from email and docs, the goal, talking points, and questions to ask, all sourced.
metadata:
  id: meeting-prep-brief
  version: "1.0.0"
  author: BotPlaza
---

# Meeting Prep Brief

> Walk into every meeting knowing who's there and what you want.

## What it does

Walk into every meeting knowing who's in the room, what happened last time, and what you want out of it.

## When to use

- "Prep me for my 2 PM", "who's on my calendar today", "brief me before the call with {name}".
- A routine that runs each morning for the day's meetings, or 30 minutes before each external meeting.

## Requires

A calendar connector. Email and document connectors make the brief much better but are optional. Web search for public background.

## Schedule

Default: Weekdays, 7:30 AM. Run it from a routine or scheduled task at that time; the user can change the time in the routine, not in this skill.

## Inputs

| Setting | Default | Notes |
|---|---|---|
| `which_meetings` | today's meetings with external attendees | Or a named meeting, "all of today", or "next 3 days". |
| `skip` | 1:1s with direct reports, focus blocks, all-hands | Patterns to ignore. |
| `depth` | standard | `quick` (5 bullets), `standard` (1 page), `deep` (adds company research and recent news). |
| `my_goal` | infer, then confirm | What the user wants out of the meeting. |

## Steps

1. **Read the event:** title, time (user's timezone), duration, attendees, location or link, agenda, and attachments.
2. **Identify attendees.** For each person outside the user's organization, find their role and company from the invite, email signatures, and public professional profiles or company pages. Don't guess; if unknown, say "Role unknown".
3. **Pull shared history.** Search email and docs for the last 3 to 5 interactions with these attendees or their company. Note open commitments on both sides ("You promised pricing by Friday").
4. **Check the news.** For external companies, find anything material in the last 30 days (funding, launches, leadership changes, layoffs) with links.
5. **Set the goal.** State the user's likely goal in one line. If it's unclear, write two options and ask.
6. **Write talking points and questions:** 3 points the user should make and 3 questions to ask, each grounded in the history or news above.
7. **Flag risks:** conflicts, back-to-back meetings with no travel time, missing dial-in, attendees added at the last minute.

## Output format

```markdown
# {Meeting title}
**{Day, time–time tz}** · {Location / link} · {Duration}

**Goal:** {one line}

## Who's in the room
- **{Name}**, {Role}, {Company}. {One relevant fact.} [source]({url})

## Where things stand
- {Last interaction, date, outcome}
- **Open:** {commitment, owner, due}

## Worth knowing
- {Recent company news.} [source]({url})

## Say
1. {Talking point}

## Ask
1. {Question}

## Watch out
- {Risk or logistics flag}
```

## Edge cases

- **No external attendees:** give a 3-line brief (purpose, open items, what to bring).
- **Recurring meeting:** focus on what changed since the last occurrence.
- **Common name, uncertain match:** say the match is uncertain and don't include background.
- **Private or personal events:** skip them unless the user asks.

## Boundaries

Read-only. Don't email attendees, accept or decline invites, or edit events without approval. Use only professional, public information about people.