Agent skill · Testing & QA

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.

silversteingithub.com/silversteinGitHub ↗
claude-codeships scriptsMIT
Install
npx skills add silverstein/minutes --skill minutes-verify --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 3 KB
Bundled scripts: yes
Requires: opencode
Path: .opencode/skills/minutes-verify/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,410
Language: Rust

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

## 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 priva

What's inside
Steps it walks through
  1. Skill Path
  2. How to verify
  3. What gets checked
  4. After verification
  5. Gotchas
Ships with 1 file
  • scripts/verify-setup.sh
Commands it runs
export MINUTES_SKILLS_ROOT="$(git rev-parse --show-toplevel)/.opencode/skills"
export MINUTES_SKILL_ROOT="$MINUTES_SKILLS_ROOT/minutes-verify"
bash "$MINUTES_SKILL_ROOT/scripts/verify-setup.sh"
More from minutes
All skills →
About this skill
What does the minutes-verify skill do?

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.

How do I install it?

Run `npx skills add silverstein/minutes --skill minutes-verify --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From silverstein/minutes, a repository with 1,410 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going