minutes-cleanup
The minutes-cleanup skill helps users manage disk space consumed by meeting recordings and transcripts. Use it when the user requests storage cleanup, wants to know how much space meetings occupy, needs to delete old or processed audio files, or asks about archiving past meetings. The skill previews cleanup actions before applying them, archives old meeting markdown files, removes temporary audio files post-transcription, and cleans stale state files while protecting transcript markdown from accidental deletion.
git clone --depth 1 https://github.com/silverstein/minutes /tmp/minutes-cleanup && cp -r /tmp/minutes-cleanup/tooling/skills/sources/minutes-cleanup ~/.claude/skills/minutes-cleanupskill.md
# /minutes-cleanup
Help the user manage disk space and organize old recordings. Minutes is
transcript-first: markdown notes and structured memory are durable, while raw
audio is a temporary recovery/reprocessing layer unless pinned.
## Check current usage
```bash
minutes storage
minutes storage --json
```
Present this to the user before taking any action.
## Common cleanup tasks
### Preview raw-audio cleanup
After transcription, the original audio files are no longer needed for search or
recap. They only matter if you want to re-transcribe with a better model or
debug recovery. Cleanup is preview-only unless `--apply` is passed.
```bash
# Use the configured retention policy
minutes cleanup
# Try a shorter successful-audio window
minutes cleanup --older-than 14d
# Machine-readable preview for agents
minutes cleanup --json
```
### Delete raw audio candidates
Only apply cleanup after showing the preview and getting explicit confirmation.
```bash
minutes cleanup --apply
minutes cleanup --older-than 14d --apply
```
### Archive old meetings
Move meetings older than N days to an archive folder:
```bash
mkdir -p ~/meetings/archive
# Find meetings older than 90 days
find ~/meetings -maxdepth 1 -name "*.md" -mtime +90
# Move them (confirm with user first)
find ~/meetings -maxdepth 1 -name "*.md" -mtime +90 -exec mv {} ~/meetings/archive/ \;
```
Archived meetings won't appear in `minutes list` or `minutes search` (which only scans `~/meetings/`), but they're still on disk if needed.
### Clean up processed voice memos
The watcher moves originals to `~/meetings/memos/processed/` after transcription:
```bash
du -sh ~/meetings/memos/processed/ 2>/dev/null
```
### Clean up stale state
```bash
# Remove stale PID file
rm -f ~/.minutes/recording.pid
# Clean old logs (keep last 7 days)
find ~/.minutes/logs -name "*.log" -mtime +7 -delete 2>/dev/null
# Remove last-result.json (transient)
rm -f ~/.minutes/last-result.json
```
## Gotchas
- **Never delete `.md` files without asking** — These are the transcripts. They're small and contain the actual value. WAV files are the space hogs.
- **Prefer `minutes cleanup` over raw `find -delete`** — The CLI understands pinned audio and sidecar stems.
- **Archived meetings are invisible to search** — `minutes search` only walks `~/meetings/` and `~/meetings/memos/`. If you need archived meetings searchable, configure QMD to index `~/meetings/archive/` too.
- **Audio deletion is irreversible** — If the user might want to re-transcribe with a better model later, suggest pinning important recordings and only deleting old unpinned candidates.
- **Pin exceptions in frontmatter** — Add `audio_retention: pinned` to a meeting to keep its raw audio out of cleanup candidates.
- **Audio is ~10 MB/minute, transcripts are ~1 KB/minute** — Deleting audio saves 99%+ of space while keeping all searchable content.
- **iCloud sync caveat** — If `~/meetings/` is in an iCloud-synced folder, deleted files go to "Recently Deleted" and still count against storage for 30 days.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.
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.
Cross-meeting entity graph — query who/what/when across all your meetings as structured data, with co-occurrence and cross-entity queries that text search can't answer. Use whenever the user says "show me everyone who mentioned X", "all mentions of Y across meetings", "who knows about Z", "graph", "across all meetings", "entity search", "first time we talked about", "trend for X over time", "who's been mentioned alongside", or wants to query meetings as an index rather than full-text search. Builds a JSON entity index on first run (one-time slow), then answers queries instantly. Surface this skill for relationship intelligence, due diligence, or any "across all my history" question that text search alone can't answer.
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.
List recent meetings and voice memos. Use when the user asks "what meetings did I have", "show my recent recordings", "any meetings today", "list my voice memos", or wants an overview of their meeting history. Also use when they need to find a specific meeting by browsing rather than searching.
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".