How do I install the Minutes Verify skill?

Run npx skillmds@latest add silverstein/minutes-verify in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Minutes Verify safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Minutes Verify?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Minutes Verify free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Minutes Verify?

silverstein (@silverstein) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Minutes Verify by silverstein — Agent Skill

Name: Minutes Verify
Rating: 4.2 (5 reviews)
Author: silverstein

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.

silverstein Updated Sep 9, 2026

File contents

Skill Path

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"

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

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.

---name: minutes-verifydescription: 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.--- ## Skill Path Before running helper scripts or opening bundled references, set: ```bash export MINUTES_SKILLS_ROOT="$(git rev-parse --show-toplevel)/.opencode/skills" 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 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 | 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 | ## 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.

Frequently asked questions