meeting-summarizer

Meeting Summarizer

Reads a meeting transcript (VTT, TXT, SRT) and optional agenda/prep notes, then generates a structured "## Notes by Claude" summary and injects it into the corresponding Obsidian meeting file.

Also supports extracting Plaud AI summaries and transcripts directly from Plaud share URLs or the official Plaud CLI and injecting them as "## Notes by Plaud".

When to Use

Invoke /meeting-summarizer when you want to:

• Summarize a recorded meeting from a transcript file
• Add or refresh AI-generated notes in an existing meeting Obsidian file
• Replace a ## Notes by Gemini section with ## Notes by Claude
• Extract a Plaud AI summary from a share URL and inject it as ## Notes by Plaud
• Save a Plaud transcript to the vault's TRANSCRIPTS/ folder

Workflow

Step 1 — Discover Vault Root

Read Obsidian configuration to find the active vault:

cat ~/Library/Application\ Support/obsidian/obsidian.json

Parse the JSON to find the vault with "open": true. Extract vault_root.

Step 2 — Identify the Meeting File

If invoked with an argument (e.g., /meeting-summarizer 2026-04-09), use it to locate the meeting file:

find "<vault_root>/MEETINGS" -name "<arg>*.md" | head -5

If multiple matches or no argument: use AskUserQuestion to let the user select or provide the meeting file path. Show the matched file and confirm before proceeding.

Step 2.5 — Detect Plaud Source

After identifying the meeting file, check if a Plaud source is available:

1. Read the meeting frontmatter — check for a plaud: field containing a share URL.
2. Ask the user: "Do you have a Plaud share URL, recording ID, or webarchive file to import?"
   • If yes → go to Step 3a (Plaud extraction) before Step 3
   • If no → continue to Step 3 (standard transcript workflow)

Step 3a — Extract from Plaud (if Plaud source provided)

Three methods, in priority order:

Method A — Official Plaud CLI (preferred when authenticated)

Check if the CLI is available and authenticated: