minutes-setup
The minutes-setup skill guides users through initial Minutes configuration by verifying existing setup state, building the Rust binary if needed, downloading a Whisper speech recognition model at their chosen quality level, creating required directories, configuring audio input for call recording via BlackHole, and testing the installation. Use this skill when users request setup help, installation guidance, or first-time configuration for the Minutes meeting transcription tool.
git clone --depth 1 https://github.com/silverstein/minutes /tmp/minutes-setup && cp -r /tmp/minutes-setup/.opencode/skills/minutes-setup ~/.claude/skills/minutes-setupSKILL.md
## Skill Path Before running helper scripts or opening bundled references, set: ```bash export MINUTES_SKILLS_ROOT="$(git rev-parse --show-toplevel)/.opencode/skills" export MINUTES_SKILL_ROOT="$MINUTES_SKILLS_ROOT/minutes-setup" ``` # /minutes-setup Walk the user through first-time Minutes setup, step by step. ## Setup steps ### 1. Check current state first Run the verify skill's script to see what's already done: ```bash bash "$MINUTES_SKILLS_ROOT/minutes-verify/scripts/verify-setup.sh" ``` Skip any steps that already pass. ### 2. Build the binary (if needed) ```bash cd ~/Sites/minutes export CXXFLAGS="-I$(xcrun --show-sdk-path)/usr/include/c++/v1" cargo build --release ``` The binary lands at `target/release/minutes`. The user should add it to their PATH or create a symlink. ### 3. Download a whisper model Ask the user which quality level they want using AskUserQuestion: | Model | Size | Speed | Quality | Best for | |-------|------|-------|---------|----------| | `tiny` | 75 MB | ~10x real-time | Low | Quick tests, short memos | | `small` | 466 MB | ~4x real-time | Good | Daily meetings (recommended) | | `medium` | 1.5 GB | ~2x real-time | Great | Important meetings, accents | | `large-v3` | 3.1 GB | ~1x real-time | Best | Legal, medical, foreign language | Then run: ```bash minutes setup --model <chosen-model> ``` ### 4. Create directories ```bash mkdir -p ~/meetings/memos ``` ### 5. Audio input (if recording calls) For in-person conversations, the built-in mic works fine. For Zoom/Meet/Teams: 1. Install BlackHole: `brew install blackhole-2ch` 2. Open Audio MIDI Setup (Spotlight → "Audio MIDI Setup") 3. Create a Multi-Output Device combining speakers + BlackHole 4. Set the Multi-Output Device as system output 5. Set BlackHole as Minutes' input (or system default input) See `minutes-record/references/audio-devices.md` for the full guide. ### 6. Verify Run verify again to confirm everything passes: ```bash bash "$MINUTES_SKILLS_ROOT/minutes-verify/scripts/verify-setup.sh" ``` ### 7. Test recording ```bash minutes record --title "Test recording" # Speak for 10-15 seconds minutes stop ``` Check the output file exists in `~/meetings/` and has a transcript. ## Gotchas - **macOS 26 (Tahoe) requires CXXFLAGS** — The whisper.cpp build needs the C++ include path set explicitly. This is a known Apple SDK issue. - **First model download can be slow** — The `small` model is 466 MB. On slow connections, `tiny` is a good starting point (75 MB). - **BlackHole setup is the hardest part** — Most users struggle with the Audio MIDI Setup step. Offer to walk through it if they get stuck.
Fast non-interactive briefing before any meeting — auto-detects your next calendar event, pulls relationship history, surfaces open commitments, and produces a one-page brief in under 30 seconds. Use this whenever the user says "brief me", "give me a quick brief", "what's coming up", "background on my next call", "who am I meeting next", "brief me on Sarah", "I have a call in 10 min", "quick rundown", or right before walking into a meeting. Different from /minutes-prep — brief is the fast hook-fireable version that doesn't ask questions and doesn't set goals. Use brief when speed matters; use prep when the user wants to think hard about goals first.
Manage old recordings — find large files, archive old meetings, delete processed originals. Use when the user says "clean up recordings", "how much space are meetings using", "delete old recordings", "archive meetings", "manage meeting storage", or asks about disk space from minutes.
Post-meeting debrief — analyzes what happened, compares outcomes to your prep intentions, tracks decision evolution. Use when the user says "debrief", "what just happened in that meeting", "what did we decide", "debrief that call", "post-meeting", "what changed", or right after stopping a recording.
Cross-meeting entity graph — query who/what/when across all your meetings as structured data, with co-occurrence and cross-entity queries that text search can't answer. Use whenever the user says "show me everyone who mentioned X", "all mentions of Y across meetings", "who knows about Z", "graph", "across all meetings", "entity search", "first time we talked about", "trend for X over time", "who's been mentioned alongside", or wants to query meetings as an index rather than full-text search. Builds a JSON entity index on first run (one-time slow), then answers queries instantly. Surface this skill for relationship intelligence, due diligence, or any "across all my history" question that text search alone can't answer.
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
Extract facts from meetings and update your knowledge base — person profiles, chronological log, and index. Use when the user asks "ingest my meetings", "update my knowledge base", "extract facts from meetings", "sync meetings to wiki", "backfill knowledge", or wants their PARA/Obsidian/wiki profiles updated from conversation data.
Health-check your meeting knowledge for contradictions, stale commitments, and decision conflicts. Use when the user asks "any conflicts in my meetings", "check for stale action items", "lint my meetings", "consistency check", "are there contradictions", or wants to audit their decision history.
List recent meetings and voice memos. Use when the user asks "what meetings did I have", "show my recent recordings", "any meetings today", "list my voice memos", or wants an overview of their meeting history. Also use when they need to find a specific meeting by browsing rather than searching.