Verify that Minutes is properly set up and working — model downloaded, mic accessible, directories exist, no stale state. Use when the user says "is minutes working", "check my setup", "verify minutes", "test recording setup", "why isn't minutes working", "minutes health check", or after running setup for the first time.
Run a health check on the Minutes installation to confirm everything is working.
Run the verification script included with this skill:
bash "${CLAUDE_PLUGIN_ROOT}/skills/minutes-verify/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.
| 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 | At least one audio input device available (macOS only) |
| Config | ~/.config/minutes/config.toml exists (optional — defaults work fine) |
If any checks fail, tell the user exactly what to do:
cargo build --release in the minutes repo, then add to PATHminutes setup --model small (recommended) or --model tiny (faster, lower quality)mkdir -p ~/meetings/memos — will also be created on first recordingrm ~/.minutes/recording.pid — previous recording crashed without cleanupsystem_profiler). On Linux, that check will be skipped.minutes setup after building.~/.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.