BrianRWagner/ai-marketing-claude-code-skills / meeting-prep
meeting-prep
VerifiedGenerate a pre-meeting prep brief in Claude Code. Researches participants, pulls vault context, builds agenda, surfaces sharp questions. Use when user says "prep for this meeting," "I have a call with," "meeting tomorrow with," or "prep brief for [name/company]."
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.4 KB |
| references/brief-template.md | markdown | 1.0 KB |
| references/meeting-types.md | markdown | 2.3 KB |
| references/question-banks.md | markdown | 2.7 KB |
SKILL.md
View on GitHub---
name: meeting-prep
description: Generate a pre-meeting prep brief in Claude Code. Researches participants, pulls vault context, builds agenda, surfaces sharp questions. Use when user says "prep for this meeting," "I have a call with," "meeting tomorrow with," or "prep brief for [name/company]."
---
# Meeting Prep
Generate a meeting prep brief from your Obsidian vault. Researches participants, surfaces vault history, builds a prioritized agenda, and generates sharp questions. No autonomy — you run it, you get your brief.
---
## Mode
Detect from context or ask: *"Quick refresher, full prep brief, or deep prep for a high-stakes meeting?"*
| Mode | What you get | Best for |
|------|-------------|----------|
| `quick` | Who they are, last touchpoint, open commitments, 3 questions. Skips the full agenda. | A call in 10 minutes |
| `standard` | Full brief: vault search, prior notes, open commitments, agenda, questions | Most client, sales and partner meetings |
| `deep` | Full brief plus web research on each participant and company, likely objections with responses, and a one-line desired outcome with a fallback ask | Pitches, renewals, negotiations, first meetings with senior people |
**Default: `standard`.** Use `quick` if the meeting is soon or routine. Use `deep` when money, a decision or a first impression is on the line.
---
## How to Use
Open Claude Code in your vault directory and say:
```
Run the Meeting Prep skill. Meeting with [name] from [company]. Type: [sales/client/strategy/partnership/interview]. Time: [date/time].
```
---
## INTAKE
Check that the user has provided:
- Participant name(s) and company
- Meeting type (Client / Sales / Strategy / Partnership / Interview / Other)
- Meeting time/date
- Optional: prior notes, last meeting summary
If meeting type is missing, ask:
```
What type of meeting is this?
Client / Sales / Strategy / Partnership / Interview / Other
```
---
## ANALYZE
Run these steps in order. Capture all output before formatting the brief.
### Step 1 — Vault Search
```bash
VAULT="${VAULT_PATH:-$HOME/vault}"
NAME="[PARTICIPANT_NAME]"
COMPANY="[COMPANY_NAME]"
echo "=== VAULT CONTEXT ==="
grep -rl "$NAME\|$COMPANY" "$VAULT" \
--include="*.md" \
-not -path "*/.git/*" \
-not -path "*/.obsidian/*" \
| head -10 | while read f; do
echo "--- ${f##$VAULT/} ---"
grep -n "$NAME\|$COMPANY" "$f" | head -5
done
```
### Step 2 — Prior Meeting Notes
```bash
VAULT="${VAULT_PATH:-$HOME/vault}"
find "$VAULT/meeting-prep" -name "*.md" 2>/dev/null \
| xargs grep -l "$NAME\|$COMPANY" 2>/dev/null \
| sort -r | head -3 | while read f; do
echo "--- Prior brief: ${f##$VAULT/} ---"
head -30 "$f"
done
```
### Step 3 — Open Commitments Check
```bash
VAULT="${VAULT_PATH:-$HOME/vault}"
grep -rn "TODO\|action item\|follow up\|promised" "$VAULT" \
--include="*.md" \
-l 2>/dev/null \
| xargs grep -l "$NAME\|$COMPANY" 2>/dev/null \
| head -5 | while read f; do
echo "--- ${f##$VAULT/} ---"
grep -n "TODO\|action item\|follow up\|promised" "$f" | grep -i "$NAME\|$COMPANY" | head -5
done
```
---
## OUTPUT
Format the brief using this structure (see `references/brief-template.md`):
```
# Meeting Prep: [Name] | [Date] [Time]
Meeting type: [type]
Their role: [role at company]
Relationship stage: [new / existing / lapsed]
---
WHY THIS MEETING MATTERS
[1-2 sentences on stakes, objective, desired outcome]
3 PRIORITIES FOR THIS CALL
1. [Priority 1]
2. [Priority 2]
3. [Priority 3]
CONTEXT FROM VAULT
[Pulled notes, open items, prior commitments — or "No prior history found"]
QUESTIONS TO ASK
1. [Question referencing research]
2. [Question]
3. [Question]
4. [Question]
5. [Question]
WATCH FOR
[Known objections, sensitivities, open loops]
DESIRED OUTCOME
[What does success look like in one sentence?]
NEXT STEP TO PROPOSE
[Specific: "schedule X," "send Y," "agree on Z"]
```
**Then:** Save brief to `meeting-prep/YYYY-MM-DD-[lastname]-prep.md`
**Then:** Print 3-line summary:
```
WHO: [Name], [role] at [company]
WHY IT MATTERS: [1 sentence]
TOP QUESTION: [The single sharpest question to ask]
```
---
## Reference Files
- `references/brief-template.md` — full brief format
- `references/meeting-types.md` — agenda by meeting type
- `references/question-banks.md` — question sets by context
---
## Requirements
- Claude Code with bash tool access
- Vault with a meeting-prep/ folder
- No external APIs required
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |