meeting-prep-cc
Scannednpx machina-cli add skill BrianRWagner/ai-marketing-claude-code-skills/meeting-prep --openclawMeeting Prep (Claude Code Edition)
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.
How to Use
Open Claude Code in your vault directory and say:
Run the Meeting Prep skill. Meeting with [name] from [company]. Type: [sales/WRS/strategy/partnership/interview]. Time: [date/time].
INTAKE
Check that the user has provided:
- Participant name(s) and company
- Meeting type (WRS / 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?
WRS client / Sales / Strategy / Partnership / Interview / Other
ANALYZE
Run these steps in order. Capture all output before formatting the brief.
Step 1 — Vault Search
VAULT="${VAULT_PATH:-/root/obsidian-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
VAULT="${VAULT_PATH:-/root/obsidian-vault}"
find "$VAULT/bambf/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
VAULT="${VAULT_PATH:-/root/obsidian-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 bambf/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 formatreferences/meeting-types.md— agenda by meeting typereferences/question-banks.md— question sets by context
Requirements
- Claude Code with bash tool access
- Vault with bambf/ structure
- No external APIs required
Source
git clone https://github.com/BrianRWagner/ai-marketing-claude-code-skills/blob/main/meeting-prep/SKILL.mdView on GitHub Overview
Generates a crisp pre-meeting brief from your Obsidian vault. It researches participants, surfaces vault history, builds a prioritized agenda, and surfaces sharp questions. You run it to get a polished brief that includes intake validation, vault-derived context, and a clear action path.
How This Skill Works
The skill runs in three steps: 1) Vault Search to pull context on participants and company, 2) Prior Meeting Notes to surface relevant history, 3) Open Commitments Check to surface TODOs and follow-ups. It formats output per the standard brief template and saves the result to bambf/meeting-prep, ready for review and action.
When to Use It
- Before a client or partner meeting to align on priorities and questions
- When you have a call with a named person from a company and need context
- For a meeting scheduled tomorrow that requires a tight agenda
- During sales, strategy, partnership, or interview prep to surface open items
- When you want a structured, vault-backed prep brief with a clear next step
Quick Start
- Step 1: Provide participant name(s), company, meeting type, and time/date
- Step 2: Run the Meeting Prep skill in Claude Code to harvest vault context and create the brief
- Step 3: Save the brief to bambf/meeting-prep/YYYY-MM-DD-[lastname]-prep.md and review the 3-line summary
Best Practices
- Provide participant name(s) and company to improve vault search accuracy
- Specify meeting type (WRS / Sales / Strategy / Partnership / Interview / Other) for tailored output
- Review prior notes and commitments in the vault before running the skill
- Limit output to 3 top priorities and up to 5 sharp questions for focus
- Save and re-use the generated brief; follow up with the proposed next step
Example Use Cases
- Sales call with Acme Corp to discuss renewal and upsell opportunities
- Strategy meeting with BetaTech on the Q3 product roadmap
- Partnership discussion with Gamma LLC around co-marketing initiatives
- Interview prep with Jane Doe from Omega Corp for a leadership interview
- WRS client briefing for a quarterly review with a long-standing client