silverstein/minutes/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 "${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.

What gets checked

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.