
Meeting Prep Cc
- 118 installs
- 390 repo stars
- Updated March 19, 2026
- brianrwagner/ai-marketing-skills
meeting-prep-cc is a Claude Code skill that generates a pre-meeting prep brief by searching an Obsidian vault for participant context, prior notes, and open commitments.
About
meeting-prep-cc generates a pre-meeting prep brief inside Claude Code by searching an Obsidian vault. It greps the vault for participant and company context, pulls prior meeting notes, and checks for open commitments, then formats a brief with priorities, questions, and a desired outcome. A developer uses it before a sales, strategy, or partnership call to walk in prepared without external APIs.
- Generates a pre-meeting prep brief from an Obsidian vault using Claude Code and bash
- Runs three grep/find vault searches: participant context, prior meeting notes, open commitments
- Outputs a structured brief (priorities, questions, watch-fors) and saves it to the vault
Meeting Prep Cc by the numbers
- 118 all-time installs (skills.sh)
- Ranked #1,296 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
meeting-prep-cc capabilities & compatibility
Free; runs locally with bash over a vault, no API keys.
- Capabilities
- meeting prep · note search · agenda generation
- Works with
- obsidian
- Use cases
- research · project management
- Pricing
- Free
What meeting-prep-cc says it does
Generate a meeting prep brief from your Obsidian vault. Researches participants, surfaces vault history, builds a prioritized agenda, and generates sharp questions.
No external APIs required
Save brief to `bambf/meeting-prep/YYYY-MM-DD-[lastname]-prep.md`
npx skills add https://github.com/brianrwagner/ai-marketing-skills --skill meeting-prep-ccAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 118 |
|---|---|
| repo stars | ★ 390 |
| Last updated | March 19, 2026 |
| Repository | brianrwagner/ai-marketing-skills ↗ |
What it does
Prepare a meeting brief from an Obsidian vault before a sales, strategy, partnership, or interview call.
Who is it for?
Developers or founders who keep meeting notes in an Obsidian vault and want a structured brief before a call.
Skip if: Users without an Obsidian vault or who need live participant research from external APIs.
When should I use this skill?
The user says 'prep for this meeting', 'I have a call with', 'meeting tomorrow with', or 'prep brief for [name/company]'.
What you get
A saved, structured meeting brief with priorities, vault context, questions, and a proposed next step.
- A structured meeting prep brief saved to the vault
- A 3-line who/why/top-question summary
By the numbers
- 3 vault-search steps
- 5 questions in the output brief
Files
Meeting 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
doneStep 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"
doneStep 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
Meeting Prep: [Name] | [Date] [Time]
Meeting type: [WRS / Sales / Strategy / Partnership / Interview] Duration: [time] Their role: [role at company] Relationship stage: [new / existing / lapsed]
---
Why This Meeting Matters
[1-2 sentences on stakes, objective, and 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"]
What They Care About Right Now
[Recent signals: posts, news, company context, anything fresh]
Questions to Ask
1. [Question — should reference specific research] 2. [Question] 3. [Question] 4. [Question] 5. [Question] 6. [Optional question] 7. [Optional question]
Watch For / Potential Friction
[Known objections, sensitivities, open loops, or landmines]
Desired Outcome
[What does a successful meeting look like in one sentence?]
Next Step to Propose
[Specific and concrete: "schedule X," "send Y," "agree on Z"]
Meeting Types + Agenda Templates
---
WRS Client Meeting
Objective: Relationship health + project status + next sprint alignment
Agenda: 1. Quick wins since last meeting (2 min) 2. Current project status (5 min) 3. Blockers / what they need from us (5 min) 4. Next sprint priorities (5 min) 5. Any scope or budget changes (3 min)
Watch for: Scope creep, satisfaction signals, renewal indicators, unspoken concerns Key question: "What's one thing that would make your life easier right now?"
---
Sales / Discovery Meeting
Objective: Understand their pain, qualify fit, move to next step
Agenda: 1. Context setting — why they reached out (2 min) 2. Current situation + pain (10 min) 3. What they've tried (5 min) 4. What good looks like (5 min) 5. Our fit / next step (5 min)
Watch for: Urgency signals, budget authority, timeline, who else is involved Key question: "What made you want to have this conversation now vs. 6 months ago?"
---
Strategy Session
Objective: Make a decision or align on direction
Agenda: 1. Situation brief (3 min) 2. Options on the table (10 min) 3. Tradeoffs + risks (5 min) 4. Decision / alignment (5 min) 5. Owners + timeline (2 min)
Watch for: Misaligned assumptions, hidden blockers, decisions being deferred Key question: "What assumptions are we making that could be wrong?"
---
Partnership / Intro Meeting
Objective: Establish mutual value, determine fit for collaboration
Agenda: 1. Their world — what they're building (5 min) 2. Our world — what we're building (5 min) 3. Overlap and potential (5 min) 4. Specific collaboration idea (5 min) 5. Next step if fit exists (5 min)
Watch for: Complementary audiences, clear non-compete, genuine energy vs. polite interest Key question: "Where do you see your audience overlapping with ours?"
---
Interview / Evaluation Meeting
Objective: Assess fit — culture, competence, motivation
Agenda: 1. Their background in their own words (5 min) 2. Deep dive on relevant experience (10 min) 3. How they handle X situation (10 min) 4. Their questions (5 min) 5. Next step (2 min)
Watch for: Ownership language, specificity, red flags (vague answers, blame, inconsistencies) Key question: "Walk me through a time you had to [relevant challenge]."
Question Banks by Category
Use at least 2 questions that reference specific participant context (their role, recent news, vault history).
---
Discovery Questions (Sales / New Relationship)
- What made you want to have this conversation now vs. 6 months ago?
- What have you already tried? What worked, what didn't?
- Walk me through how this problem shows up in a typical week.
- Who else is affected by this? Who would notice if it was fixed?
- What would "solved" look like for you?
- What's the cost of doing nothing?
- Who else is involved in making this decision?
---
Relationship / WRS Questions
- What's working well that we should double down on?
- What's one thing that would make your life easier right now?
- If you had to prioritize one thing for next quarter, what would it be?
- How are you feeling about the direction we're headed?
- Is there anything you've been hesitant to bring up?
- What does success look like for you 90 days from now?
---
Strategy Questions
- What assumptions are we making that could be wrong?
- What's the reversible vs. irreversible version of this decision?
- Who would disagree with this direction and why?
- What would we regret not doing in 12 months?
- What's the cheapest way to test this before we commit?
- What's changed since we last talked about this?
---
Partnership Questions
- What's working in your current partnerships?
- Where do you see your audience overlapping with ours?
- What would a successful collaboration look like 6 months from now?
- What's the one thing you'd need to feel confident about moving forward?
- What do your current partners get wrong that we could get right?
---
Interview / Evaluation Questions
- Walk me through your background in your own words.
- Tell me about a time you [relevant situation] — what did you do?
- What's the hardest thing you've had to figure out in a role?
- What do you need from the people you work with to do your best work?
- What are you looking for in your next opportunity that you don't have now?
- What questions do you have for me?
---
Closing / Next Step Questions
- Based on what we discussed, does this feel like a fit?
- What would you need to see to move forward?
- What's the right next step from your side?
- Is there anything that would get in the way of us working together?
- When should we follow up, and what should that look like?
---
Context-Specific Starters (Fill in with research)
- "I noticed you recently [posted about / published / announced] — what's driving that focus right now?"
- "Last time we spoke, you mentioned [open item]. Where does that stand?"
- "Your company just [news item]. How is that affecting [relevant area]?"
- "You've been in [role] for [tenure]. What's shifted in how you approach [topic] over that time?"
Platform: OpenClaw (token-optimized)
Required Inputs
- 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 missing, ask before proceeding.
Workflow
Step 1 — Vault search:
VAULT="${VAULT_PATH:-/root/obsidian-vault}"
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
doneStep 2 — Prior meeting notes:
find "$VAULT/bambf/meeting-prep" -name "*.md" 2>/dev/null \
| xargs grep -l "$NAME\|$COMPANY" 2>/dev/null | sort -r | head -3Step 3 — Open commitments check:
grep -rn "TODO\|action item\|follow up\|promised" "$VAULT" --include="*.md" -l \
| xargs grep -l "$NAME\|$COMPANY" 2>/dev/null | head -5Output Format
# 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 + 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. [Research-referencing question]
2–5. [Additional questions]
WATCH FOR
[Known objections, sensitivities, open loops]
DESIRED OUTCOME
[What success looks like in one sentence]
NEXT STEP TO PROPOSE
[Specific: "schedule X," "send Y," "agree on Z"]Then: Save 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: [Sharpest question to ask]Reference Files
references/brief-template.md— full formatreferences/meeting-types.md— agenda by typereferences/question-banks.md— question sets
--- Skill by Brian Wagner | AI Marketing Architect
Related skills
FAQ
Does this skill need external APIs?
No. The SKILL.md states 'No external APIs required'; it runs bash searches over a local Obsidian vault.
Where is the brief saved?
It saves the brief to bambf/meeting-prep/YYYY-MM-DD-[lastname]-prep.md inside the vault.