// 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.
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.
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.
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.
Start or stop recording a meeting, call, or voice memo. Use this whenever the user says "record", "start recording", "capture this meeting", "stop recording", "I'm in a meeting", "take notes on this call", or wants to transcribe live audio. Also use when they ask about recording status or want to know if something is being recorded.
Start or stop recording a meeting, call, or voice memo. Use this whenever the user says "record", "start recording", "capture this meeting", "stop recording", "I'm in a meeting", "take notes on this call", or wants to transcribe live audio. Also use when they ask about recording status or want to know if something is being recorded.
Start or stop recording a meeting, call, or voice memo. Use this whenever the user says "record", "start recording", "capture this meeting", "stop recording", "I'm in a meeting", "take notes on this call", or wants to transcribe live audio. Also use when they ask about recording status or want to know if something is being recorded.
| name | minutes-verify |
| description | 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. |
| compatibility | opencode |
Before running helper scripts or opening bundled references, set:
export MINUTES_SKILLS_ROOT="$(git rev-parse --show-toplevel)/.opencode/skills"
export MINUTES_SKILL_ROOT="$MINUTES_SKILLS_ROOT/minutes-verify"
Run a health check on the Minutes installation to confirm everything is working.
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.
| 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 |
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 cleanupminutes setup so Minutes can recreate the .metadata_never_index markers.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.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..metadata_never_index; it does not disable Spotlight indexing for the whole user volume.