Skip to content
cccskills
FreePublished on GitHub

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.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

/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

CheckWhat it verifies
Binaryminutes command exists on PATH
ModelAt least one whisper model downloaded in ~/.minutes/models/ or ~/.cache/whisper/
Meetings dir~/meetings/ directory exists
Memos dir~/meetings/memos/ directory exists
PID stateNo stale PID file in ~/.minutes/recording.pid
Audio inputCLI-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 privacymacOS .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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Fast non-interactive briefing before any meeting — auto-detects your next calendar event, pulls relationship history, surfaces open commitments, and produces a one-page brief in under 30 seconds. Use this whenever the user says "brief me", "give me a quick brief", "what's coming up", "background on my next call", "who am I meeting next", "brief me on Sarah", "I have a call in 10 min", "quick rundown", or right before walking into a meeting. Different from /minutes-prep — brief is the fast hook-fireable version that doesn't ask questions and doesn't set goals. Use brief when speed matters; use prep when the user wants to think hard about goals first.

The English summary is being prepared. Showing the original description.

silverstein/minutes1.6KUpdated Oct 22, 2026

Manage old recordings — find large files, archive old meetings, delete processed originals. Use when the user says "clean up recordings", "how much space are meetings using", "delete old recordings", "archive meetings", "manage meeting storage", or asks about disk space from minutes.

The English summary is being prepared. Showing the original description.

silverstein/minutes1.6KUpdated Oct 22, 2026

Start and control Minutes Coach, the separate real-time copilot HUD, with an explicit meeting goal. Use only for explicit Coach or HUD lifecycle requests such as "start Minutes Coach", "open the Coach HUD", "pause Minutes Coach", "resume Minutes Coach", "Minutes Coach status", or "stop Minutes Coach". Do not use for requests that explicitly ask the current terminal agent to watch or strategize; those belong to minutes-live-sidekick. An ambiguous request such as "coach me live" requires one short surface clarification and must not automatically start Coach.

The English summary is being prepared. Showing the original description.

silverstein/minutes1.6KUpdated Oct 22, 2026

Post-meeting debrief — analyzes what happened, compares outcomes to your prep intentions, tracks decision evolution. Use when the user says "debrief", "what just happened in that meeting", "what did we decide", "debrief that call", "post-meeting", "what changed", or right after stopping a recording.

The English summary is being prepared. Showing the original description.

silverstein/minutes1.6KUpdated Oct 22, 2026

Policy-safe relationship rankings, commitments, aliases, person profiles, and topic research. Always use Minutes' bounded native CLI surfaces; never build or read a durable graph cache.

The English summary is being prepared. Showing the original description.

silverstein/minutes1.6KUpdated Oct 22, 2026

Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.

The English summary is being prepared. Showing the original description.

silverstein/minutes1.6KUpdated Oct 22, 2026

See all skills by silverstein

Report a problem with this skill