minutes-verify

1# /minutes-verify
2 
3Run a health check on the Minutes installation to confirm everything is working.
4 
5## How to verify
6 
7Run the verification script included with this skill:
8 
9```bash
10bash "${CLAUDE_PLUGIN_ROOT}/skills/minutes-verify/scripts/verify-setup.sh"
11```
12 
13The script checks each component and outputs a pass/fail status for each. Read the output and report results to the user.
14 
15## What gets checked
16 
17| Check | What it verifies |
18|-------|-----------------|
19| Binary | `minutes` command exists on PATH |
20| Model | At least one whisper model downloaded in `~/.minutes/models/` or `~/.cache/whisper/` |
21| Meetings dir | `~/meetings/` directory exists |
22| Memos dir | `~/meetings/memos/` directory exists |
23| PID state | No stale PID file in `~/.minutes/recording.pid` |
24| Audio input | CLI-context audio input visibility (macOS only; desktop readiness is authoritative for the signed app) |
25| Config | `~/.config/minutes/config.toml` exists (optional — defaults work fine) |
26| Spotlight privacy | macOS `.metadata_never_index` markers exist for `~/.minutes` and `~/meetings` when those directories exist |
27 
28## After verification
29 
30If any checks fail, tell the user exactly what to do:
31 
32- **Binary missing** → `cargo build --release` in the minutes repo, then add to PATH
33- **No model** → `minutes setup --model small` (recommended) or `--model tiny` (faster, lower quality)
34- **No meetings dir** → `mkdir -p ~/meetings/memos` — will also be created on first recording
35…