Agent skill · Workflow & Productivity

meeting-prep-cc

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

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill meeting-prep --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/analysis/meeting-prep/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 ```bash 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

What's inside
Steps it walks through
  1. How to Use
  2. INTAKE
  3. ANALYZE
  4. Step 1 — Vault Search
  5. Step 2 — Prior Meeting Notes
  6. Step 3 — Open Commitments Check
  7. OUTPUT
  8. Reference Files
  9. Requirements
Ships with 1 file
  • metadata.json
Commands it runs
echo "=== VAULT CONTEXT ==="
grep -rl "$NAME\|$COMPANY" "$VAULT" \
echo "--- ${f##$VAULT/} ---"
grep -n "$NAME\|$COMPANY" "$f" | head -5
done
find "$VAULT/bambf/meeting-prep" -name "*.md" 2>/dev/null \
echo "--- Prior brief: ${f##$VAULT/} ---"
head -30 "$f"
grep -rn "TODO\|action item\|follow up\|promised" "$VAULT" \
grep -n "TODO\|action item\|follow up\|promised" "$f" | grep -i "$NAME\|$COMPANY" | head -5
More from claude-skill-registry
All skills →
About this skill
What does the meeting-prep-cc skill do?

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

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill meeting-prep --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going