Minutes Verify

A diagnostic skill that runs through the entire Minutes setup checklist: binary on PATH, whisper model downloaded, directories created, no stale PIDs, and audio input accessible. Use it when users ask "is minutes working" or right after initial setup to catch the most common gotcha (forgetting to download a model). The script is macOS-aware for audio checks but gracefully degrades on Linux. One thing to know: if the audio input check fails in the shell but the desktop app's Readiness Center shows green, trust the desktop app. The config file check is informational only since Minutes ships with sensible defaults.

GitHub stars: 1.3K
last updated: Jun 11, 2026

View on GitHub

Install

$ npx -y skills add silverstein/minutes --skill minutes-verify --agent claude-code

Installs into .claude/skills of the current project.

Files

/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

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