voc-source-noteslisted

# /voc-source-notes — Mine Meeting Notes Your call recorder captures scheduled video calls on a work account. It misses the conference hallway conversation, the in-person QBR, the dial-in from a phone, and the meeting someone forgot to admit the bot to. Meeting-notes apps catch a different slice, and the two sets overlap less than people assume. Notes are lower fidelity than transcripts — summarized, not verbatim. Treat them accordingly and the pipeline will weight them correctly. ## Requires | What | Value | |---|---| | Notes MCP server or export | Granola, Fathom, Otter, Fireflies, or a Notion database of meeting docs | | Config | `context/product-context.md` → `notes_source`, `internal_meeting_patterns` | | Cost | Free on most plans. | ### Wiring the tools **Tool names are not hardcoded here on purpose.** Run `/mcp` to see what your notes server exposes, then add those names to `allowed-tools`. A skill that declares a tool from a different product entirely will fail silently at its first call, which is exactly the class of bug this repo is trying not to ship. No MCP server for your notes app? Most export to markdown. Point `notes_source` at the export directory and this skill reads the files directly with Glob and Read. --- ## Execution ### Step 1 — Find customer-facing meetings Pull meetings in the window, then **exclude internal ones**. Default exclusion patterns — extend them in your context file: `standup` · `1:1` · `1-1` · `retro` · `planning` · `all hands