minutes-verify
minutes-verify runs a diagnostic script that checks whether the Minutes recording application is properly installed and configured by validating the binary exists on PATH, a whisper model is downloaded, required directories are present, no stale process files remain, and audio input is accessible. Use this skill when users report setup problems, ask if Minutes is working correctly, or request a health check after initial installation.
git clone --depth 1 https://github.com/silverstein/minutes /tmp/minutes-verify && cp -r /tmp/minutes-verify/.opencode/skills/minutes-verify ~/.claude/skills/minutes-verifySKILL.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-verify" ``` # /minutes-verify Run a health check on the Minutes installation to confirm everything is working. ## How to verify Run the verification script included with this skill: ```bash bash "$MINUTES_SKILL_ROOT/scripts/verify-setup.sh" ``` The script checks each component and outputs a pass/fail status for each. Read the output and report results to the user. ## What gets checked | Check | What it verifies | |-------|-----------------| | Binary | `minutes` command exists on PATH | | Model | At least one whisper model downloaded in `~/.minutes/models/` or `~/.cache/whisper/` | | Meetings dir | `~/meetings/` directory exists | | Memos dir | `~/meetings/memos/` directory exists | | PID state | No stale PID file in `~/.minutes/recording.pid` | | Audio input | CLI-context audio input visibility (macOS only; desktop readiness is authoritative for the signed app) | | Config | `~/.config/minutes/config.toml` exists (optional — defaults work fine) | | Spotlight privacy | macOS `.metadata_never_index` markers exist for `~/.minutes` and `~/meetings` when those directories exist | ## After verification If any checks fail, tell the user exactly what to do: - **Binary missing** → `cargo build --release` in the minutes repo, then add to PATH - **No model** → `minutes setup --model small` (recommended) or `--model tiny` (faster, lower quality) - **No meetings dir** → `mkdir -p ~/meetings/memos` — will also be created on first recording - **Stale PID** → `rm ~/.minutes/recording.pid` — previous recording crashed without cleanup - **Audio input warning** → Treat as CLI-context-only. If the signed desktop app's Readiness Center shows Audio input/Microphone as ready, trust the desktop app identity. - **Spotlight privacy warning** → Open the desktop app or run `minutes setup` so Minutes can recreate the `.metadata_never_index` markers. ## Gotchas - **The script is macOS-specific** for the audio input check (uses `system_profiler`). On Linux, that check will be skipped. On macOS, shell-context checks can disagree with the signed desktop app; use the desktop Readiness Center for TCC-sensitive truth. - **"Model not found" is the #1 setup issue** — most people forget to run `minutes setup` after building. - **Config file is optional** — if `~/.config/minutes/config.toml` doesn't exist, that's fine. Minutes uses compiled defaults. Only flag it as "not configured" (informational), not as an error. - **Spotlight privacy uses folder markers** — Minutes verifies `.metadata_never_index`; it does not disable Spotlight indexing for the whole user volume.
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.