One-page briefing before a call or meeting with person context, open items, and talking points. Use when user says \"prep me for my call with [person]\", \"meeting prep\", \"brief me before my meeting\", \"get ready for my call\", or mentions an upcoming meeting where context would help. See also: `capture-meeting` for processing notes after the call; `follow-up-draft` for thank-yous.
Scanned 9/6/2026
Install to Claude Code
npx -y skills add kbanc85/claudia --skill meeting-prep --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Meeting Prep?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/kbanc85-meeting-prep-claudia)More formats (shields.io, HTML) on the badges page.
---
name: meeting-prep
description: "One-page briefing before a call or meeting with person context, open items, and talking points. Use when user says \"prep me for my call with [person]\", \"meeting prep\", \"brief me before my meeting\", \"get ready for my call\", or mentions an upcoming meeting where context would help. See also: `capture-meeting` for processing notes after the call; `follow-up-draft` for thank-yous."
argument-hint: [person or meeting name]
effort-level: medium
---
# Meeting Prep
One-page briefing before a call or meeting.
## Usage
`/meeting-prep [person or meeting name]`
Or naturally:
- "Prep me for my call with Sarah"
- "Meeting prep for the Acme quarterly"
- "What should I know before talking to Jim?"
## What to Gather
### Primary: Deep Context (one call)
Call the `memory_deep_context` MCP tool with the person's name. This returns everything in one round trip: entity info, all memories, connected entities, temporal items (commitments, observations), and episode history. Use this data for all sections below.
If deep_context is unavailable, fall back to sequential calls: `memory_about` for the entity, then `memory_recall` for broader context.
### 1. Person Context
From `memory_deep_context` result (or `people/[person].md` as fallback):
- Role and organization
- Relationship history
- Last contact and topics
- Communication style
- What matters to them
### 2. Open Items
From the temporal section of deep_context results:
- Commitments to them
- Commitments from them
- Waiting items
### 3. Recent Context
From the episodes section of deep_context results, plus linked documents.
Also check:
- Last meeting notes (if any)
- Recent email threads (if available)
- Any project/client context
### 4. Strategic Context
- What's the purpose of this meeting?
- What outcome would be good?
- Any concerns to be aware of?
## Output Format
```
## Meeting Prep: [Person/Meeting Name]
### [Day, Date] at [Time]
---
**Who:** [Name, Role, Organization]
**Last Contact:** [Date] — [Context]
**Relationship:** [Current state/health]
---
### Context
[Brief summary of relationship and recent history]
### Open Items
**You Owe Them:**
- [Item] — due [date]
**They Owe You:**
- [Item] — expected [date]
### Key Points from Last Interaction
- [Point 1]
- [Point 2]
### What Matters to Them
- [Priority 1]
- [Priority 2]
### Suggested Topics
1. [Topic based on context]
2. [Topic based on open items]
3. [Topic based on their priorities]
### Watch For
- [Concern or sensitivity]
- [Opportunity]
### Outcome to Aim For
[What would make this meeting successful?]
---
*Anything else to prepare?*
```
## Tone
- Concise — one page max
- Actionable — clear talking points
- Contextual — relevant history surfaced
- Strategic — not just facts but suggested approach
## Without Prior Context
If no file exists for this person:
"I don't have context on [Person] yet. Would you like to:
1. Tell me about them now (quick capture)
2. Create a full person file
3. Proceed with what you know"
## Group Meetings
For meetings with multiple people:
- Brief context on key attendees
- Focus on meeting purpose
- Common threads across attendees
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!