minutes-verify

Featured

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.

AI & Automation 1,609 stars 187 forks Updated today MIT

Install

View on GitHub

Quality Score: 93/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

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

Details

Author
silverstein
Repository
silverstein/minutes
Created
8 months ago
Last Updated
today
Language
Rust
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

verify-skill-builder

Use only when the user asks to create, audit, or refresh a project-local verify skill that drives the real app - "make a verify skill for this repo", "script how to prove this app works", "audit the verify skill", "the feature map is stale". Runs only when the user asks. Not for a one-off check (use superpowers:verification-before-completion). (formerly test-kitchen)

4 Updated today
escoffier-labs
Code & Development Listed

verifier-setup

Set a repo up to prove engineering-task work actually works before it ships. Investigates the repo, ensures a one-command dev stack (`dev-local`) exists, asks whether verification runs locally or in a sandbox (crabbox), confirms/installs the driver (the `playwright-cli` skill for web by default). Outputs three artifacts: a committed `/verify` skill (per-task verification SOP — spawn a verifier sub-agent → drive the app → screenshot/video proof → open a PR with the proof embedded), the `/dev-local` skill + script, and the installed driver skill. Use when someone says "set up verification", "make this repo verifiable", "scaffold a verify skill", "set up the verifier".

1,312 Updated 2 months ago
AI-Builder-Club
Code & Development Listed

verify

Use after editing, before commit or PR, to verify an issue-delivery packet. Uses Moon's affected graph when present and documented repository-native commands otherwise; returns hash-bound evidence and loops back on failure.

1 Updated 5 days ago
g-bastianelli