meeting-prep-cc

Q: How do I install meeting-prep-cc?

Run npx skills add https://github.com/brianrwagner/ai-marketing-claude-code-skills --skill meeting-prep-cc in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/meeting-prep-cc/ (personal) or .claude/skills/meeting-prep-cc/ (project).

by brianrwagnerProductivity & Automation

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]."

Installs: 370
Last 24h: —
Trending rank: —
Security: Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/brianrwagner/ai-marketing-claude-code-skills --skill meeting-prep-cc

01
Install
Run the command in your project. The CLI asks which agents to install for.
02
Describe the task
Ask your agent for something this skill covers. It loads meeting-prep-cc automatically when relevant.
03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

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

FAQ

What does the meeting-prep-cc skill do?

How do I install meeting-prep-cc?

Run npx skills add https://github.com/brianrwagner/ai-marketing-claude-code-skills --skill meeting-prep-cc in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/meeting-prep-cc/ (personal) or .claude/skills/meeting-prep-cc/ (project).

Which AI agents can use meeting-prep-cc?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is meeting-prep-cc safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains meeting-prep-cc?

It is published by brianrwagner in brianrwagner/ai-marketing-claude-code-skills. It has 370 recorded installs.