minutes-list
The minutes-list skill displays recent meetings and voice memos from the ~/meetings/ directory in reverse chronological order, with options to filter by type or adjust the result limit. Use it when users ask for an overview of their meeting history, request recent recordings, or need to browse meetings rather than search for a specific one by name.
git clone --depth 1 https://github.com/silverstein/minutes /tmp/minutes-list && cp -r /tmp/minutes-list/tooling/skills/goldens/claude/minutes-list ~/.claude/skills/minutes-listSKILL.md
# /minutes-list Show recent meetings and voice memos, sorted newest-first. ## Usage ```bash # List last 10 recordings (default) minutes list # Show more minutes list --limit 20 # Only voice memos minutes list -t memo # Only meetings minutes list -t meeting ``` ## Output Human-readable list to stderr, JSON array to stdout. Each entry has: - `title`, `date`, `content_type`, `path` Treat each returned `path` as a hint, not a retained capability. To read a specific meeting, reauthorize it through `minutes get "<exact path>" --json`, require exit status 0, and use only that result. Never reopen a result path with the host `Read` tool. ## Gotchas - **Returns nothing on first use** — If `~/meetings/` doesn't exist yet or has no `.md` files, list returns an empty array. This is normal before the first recording. - **JSON goes to stdout, human-readable to stderr** — If you pipe the output (e.g., `minutes list | jq`), you get JSON only. The human-readable table goes to stderr. - **In-progress recordings don't appear** — List only shows completed, processed recordings. Use `minutes status` to check if something is currently recording. - **Sorted by date in frontmatter, not file modification time** — If you manually edit a meeting file, it won't change its position in the list.
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.
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.
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.
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.
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.
Extract facts from meetings and update your knowledge base — person profiles, chronological log, and index. Use when the user asks "ingest my meetings", "update my knowledge base", "extract facts from meetings", "sync meetings to wiki", "backfill knowledge", or wants their PARA/Obsidian/wiki profiles updated from conversation data.
Health-check your meeting knowledge for contradictions, stale commitments, and decision conflicts. Use when the user asks "any conflicts in my meetings", "check for stale action items", "lint my meetings", "consistency check", "are there contradictions", or wants to audit their decision history.
Self-coaching analysis of your own behavior across meetings — talk-time ratio, filler words, hedging language, monologue length, energy patterns, and (when meetings are tagged via /minutes-tag) what your behavior in winning meetings looks like vs losing ones. Use this whenever the user says "how did I do", "review my last meeting", "mirror", "self-review", "show my patterns", "coach me", "where am I weak", "talk time", "am I improving", "what do I do in meetings I win", "feedback on me", or asks for any kind of personal feedback on their own meeting behavior. This is the rare skill that gives the user a mirror to their own habits — surface it whenever they show curiosity about their own performance, even if they don't use the word "mirror".