minutes-ideas
minutes-ideas retrieves voice memos and ideas recorded on the user's devices within the last 14 days by querying the minutes CLI or scanning the local memos directory. Use this skill when users ask to recall recent voice recordings, captured thoughts, or ideas they recorded while away from their desk, such as "what ideas did I have?" or "what did I record while walking?"
git clone --depth 1 https://github.com/silverstein/minutes /tmp/minutes-ideas && cp -r /tmp/minutes-ideas/tooling/skills/sources/minutes-ideas ~/.claude/skills/minutes-ideasskill.md
# /minutes-ideas — Recent Voice Memos & Ideas Surface voice memos and ideas captured from any device in the last 14 days. This is the recall layer for the cross-device ghost context pipeline. ## How to run 1. Search for recent voice memos using the `minutes` CLI: ```bash minutes list --type memo --limit 20 --json 2>/dev/null ``` 2. If no results or CLI unavailable, scan `~/meetings/memos/` directly: ```bash ls -t ~/meetings/memos/*.md 2>/dev/null | head -20 ``` 3. For each memo found, read the frontmatter to get title, date, duration, and device: ```bash head -20 "<path>" ``` 4. Present the memos as a clean list: - Date, title, duration, device (if from iPhone) - Ask: "Want to dig into any of these?" 5. If the user picks one, read the full file and present the transcript/summary. ## Ghost Context These memos were captured on the user's phone (or Mac) and automatically transcribed by the Minutes watcher. They may contain ideas, thoughts, observations, or reminders that the user recorded while away from their desk. When the user asks "what was that idea I had while walking?" — search these memos first, then broaden to full meeting search if needed.
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.
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.
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".