Minutes minutes-verify

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.

install

source · Clone the upstream repo

git clone https://github.com/silverstein/minutes

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/silverstein/minutes "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.agents/skills/minutes/minutes-verify" ~/.claude/skills/silverstein-minutes-minutes-verify && rm -rf "$T"

manifest: .agents/skills/minutes/minutes-verify/SKILL.md

source content

Skill Path

Before running helper scripts or opening bundled references, set:

export MINUTES_SKILLS_ROOT="$(git rev-parse --show-toplevel)/.agents/skills/minutes"
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 "$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	At least one audio input device available (macOS only)
Config	`~/.config/minutes/config.toml` exists (optional — defaults work fine)

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
No audio input → Check System Settings > Sound > Input, ensure a microphone is selected

Gotchas

The script is macOS-specific for the audio input check (uses
```
system_profiler
```
). On Linux, that check will be skipped.
"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.