Skill

minutes-verify

Runs health check on Minutes setup: binary, Whisper model, directories, stale PID, mic access (macOS), config. Outputs pass/fail with fixes.

Bash

Rust

developer-tools

automation

npx claudepluginhub silverstein/minutes --plugin minutes

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Run a health check on the Minutes installation to confirm everything is working.

SKILL.md

Similar Skills

minutes-setup

906

Guides first-time Minutes setup: verifies state, builds Rust binary, downloads Whisper model, creates directories, configures macOS audio with BlackHole, tests recording.

minutes

speak-prod-checklist

1.9k

Provides production readiness checklist for Speak language learning API integrations: auth, audio pipeline with ffmpeg, rate limiting, monitoring, compliance. For prod setups and troubleshooting.

1 file6 tools

speak-pack

twinmind-incident-runbook

1.9k

Guides incident response for TwinMind failures: transcription startup, audio capture, sync issues, calendar disconnects. Includes API verification, setup, and error handling for meeting AI operations.

1 file6 tools

twinmind-pack

Stats

Parent Repo Stars906

Parent Repo Forks90

Last CommitMar 20, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

/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

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.

/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	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.