meeting-prep-cc

GitHub

该技能用于生成会议准备简报,通过检索Obsidian笔记库中的参与者信息、历史记录和待办事项,构建议程并生成尖锐问题,帮助用户高效准备销售或战略会议。

Trigger Scenarios

用户说“prep for this meeting” 用户提及“I have a call with” 用户提及“meeting tomorrow with” 用户要求“prep brief for [name/company]”

Install

npx skills add BrianRWagner/ai-marketing-claude-code-skills --skill meeting-prep-cc -g -y
More Options

Non-standard path

npx skills add https://github.com/BrianRWagner/ai-marketing-claude-code-skills/tree/main/meeting-prep -g -y

Use without installing

npx skills use BrianRWagner/ai-marketing-claude-code-skills@meeting-prep-cc

指定 Agent (Claude Code)

npx skills add BrianRWagner/ai-marketing-claude-code-skills --skill meeting-prep-cc -a claude-code -g -y

安装 repo 全部 skill

npx skills add BrianRWagner/ai-marketing-claude-code-skills --all -g -y

预览 repo 内 skill

npx skills add BrianRWagner/ai-marketing-claude-code-skills --list

SKILL.md

Frontmatter
{
    "name": "meeting-prep-cc",
    "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 (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

Version History

  • f36b34f Current 2026-08-20 09:22

Same Skill Collection

ai-discoverability-audit/SKILL.md
case-study-builder/SKILL.md
cold-outreach-sequence/SKILL.md
content-idea-generator/SKILL.md
daily-briefing-builder/SKILL.md
de-ai-ify/SKILL.md
go-mode/SKILL.md
homepage-audit/SKILL.md
last30days/SKILL.md
linkedin-authority-builder/SKILL.md
linkedin-profile-optimizer/SKILL.md
marketing-principles/SKILL.md
newsletter-creation-curation/SKILL.md
plan-my-day/SKILL.md
positioning-basics/SKILL.md
social-card-gen/SKILL.md
testimonial-collector/SKILL.md
tweet-draft-reviewer/SKILL.md
vault-cleanup-auditor/SKILL.md
voice-extractor/SKILL.md
youtube-summarizer/SKILL.md
reddit-insights/SKILL.md

Metadata

Files
0
Version
f36b34f
Hash
bf4ab06b
Indexed
2026-08-20 09:22

Accueil - Wiki
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-08-30 07:26
浙ICP备14020137号-1 $Carte des visiteurs$