Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
brianrwagner avatar

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)
At a glance

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
From the docs

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.
SKILL.md
No external APIs required
SKILL.md
Save brief to `bambf/meeting-prep/YYYY-MM-DD-[lastname]-prep.md`
SKILL.md
npx skills add https://github.com/brianrwagner/ai-marketing-skills --skill meeting-prep-cc

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs118
repo stars390
Last updatedMarch 19, 2026
Repositorybrianrwagner/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

SKILL.mdMarkdownGitHub ↗

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
  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 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 bambf/ structure
  • No external APIs required

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.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.