minutes-search

$npx mdskill add silverstein/minutes/minutes-search

Search past meeting transcripts and voice memos for topics, people, or decisions.

  • Answers questions about past discussions, decisions, or ideas from meetings.
  • Relies on a local filesystem of markdown transcripts and voice memo files.
  • Uses keyword search with optional filters for content type and date range.
  • Returns JSON with matching titles, dates, snippets, and file paths.

SKILL.md

.github/skills/minutes-searchView on GitHub ↗
---
name: minutes-search
description: Search past meeting transcripts and voice memos for specific topics, people, decisions, or ideas. Use this whenever the user asks "what did we discuss about X", "find that meeting where we talked about Y", "what did Alex say", "did we decide on", "what was that idea about", or any question that could be answered by searching their meeting history. Also use for "do I have any notes about" or "check my meetings for".
---

# /minutes-search

Find information across all meeting transcripts and voice memos.

## Usage

```bash
# Basic search
minutes search "pricing strategy"

# Filter to just voice memos
minutes search "onboarding idea" -t memo

# Filter to just meetings
minutes search "sprint planning" -t meeting

# Date filter + limit
minutes search "API redesign" --since 2026-03-01 --limit 5
```

## Flags

| Flag | Description |
|------|-------------|
| `-t, --content-type <meeting\|memo>` | Filter by type |
| `--since <date>` | Only results after this date (ISO format, e.g., `2026-03-01`) |
| `-l, --limit <n>` | Maximum results (default: 10) |

## Output

Returns JSON to stdout with an array of matches. Each result includes:
- `title` — Meeting or memo title
- `date` — When it was recorded
- `content_type` — "meeting" or "memo"
- `snippet` — The line containing the match
- `path` — Full path to the markdown file

Human-readable output goes to stderr. To read the full transcript of a match, use `cat <path>` on any result's path.

## How search works

Search is case-insensitive and matches against both the transcript body and the YAML frontmatter title. It walks all `.md` files in `~/meetings/` (including the `memos/` subfolder).

For richer semantic search, users can configure QMD as the search engine in `~/.config/minutes/config.toml`:
```toml
[search]
engine = "qmd"
qmd_collection = "meetings"
```

## Search coaching

When the user's search query is vague or too broad, push back before running it:

- **"who said X"** or **"what did Alex say"** → If the meeting has `speaker_map` in frontmatter, use it to identify who said what. `speaker_map` maps SPEAKER_X labels to real names. High confidence = reliable, Medium = "likely" (suggest `minutes confirm` to lock it in).
- **"everything"** or **"all meetings"** → "That'll return hundreds of results. What specifically are you looking for? A person, a topic, or a decision?"
- **Single common word** like "meeting" or "project" → "That's too broad. Can you narrow it — a person's name, a specific topic, or a date range?"
- **"that meeting"** or **"the one where"** → "Help me narrow it down. Do you remember who was in the meeting, roughly when it was, or a specific thing that was said?"

Suggest search strategies based on what the user is looking for:
- **Finding a person's input** → Search their name: `minutes search "Alex"`
- **Finding a decision** → Search decision keywords: `minutes search "decided"` or `minutes search "agreed"`
- **Finding an idea** → Search voice memos: `minutes search "idea" -t memo`
- **Finding something from a time range** → Use `--since`: `minutes search "pricing" --since 2026-03-01`

## Tips for good searches

- Search for **what people said**, not document titles: `"we should postpone the launch"` not `"launch delay meeting"`
- Search for **names** to find everything someone discussed: `"Alex"` or `"Case"`
- Search for **decisions**: `"decided"`, `"agreed"`, `"committed to"`
- Combine with `Read` to load the full context after finding a match

## Gotchas

- **Search is substring, not fuzzy** — `"price"` matches `"pricing"` and `"price"`, but `"prcing"` (typo) matches nothing. Try multiple terms if you're not sure of the exact wording.
- **`--since` requires ISO date format** — Use `2026-03-01`, not `"last week"` or `"March 1st"`. For relative dates, compute the ISO date first: `date -v-7d +%Y-%m-%d`.
- **Large result sets flood stdout** — Always use `--limit` when searching broad terms. The default limit is 10, but common words can match hundreds of files.
- **QMD semantic search requires separate setup** — If `config.toml` sets `engine = "qmd"` but the QMD collection isn't indexed, search will fail silently. Run `qmd update && qmd embed` first.
- **Voice memos vs meetings** — Both are searched by default. Use `-t memo` or `-t meeting` to narrow results. Voice memos live in `~/meetings/memos/`, meetings in `~/meetings/`.
- **Empty results don't mean it wasn't discussed** — If the meeting wasn't transcribed (e.g., recording was stopped before processing), it won't appear in search. Check `minutes list` to see what's been processed.

More from silverstein/minutes

SkillDescription
minutes-briefFast 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.
minutes-cleanupManage 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.
minutes-copilotStart and control Minutes Coach, the separate real-time copilot HUD, with an explicit meeting goal. Use only for explicit Coach or HUD lifecycle requests such as "start Minutes Coach", "open the Coach HUD", "pause Minutes Coach", "resume Minutes Coach", "Minutes Coach status", or "stop Minutes Coach". Do not use for requests that explicitly ask the current terminal agent to watch or strategize; those belong to minutes-live-sidekick. An ambiguous request such as "coach me live" requires one short surface clarification and must not automatically start Coach.
minutes-debriefPost-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.
minutes-graphCross-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.
minutes-ideasSurface 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.
minutes-ingestExtract 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.
minutes-lintHealth-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.
minutes-listList 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.
minutes-live-sidekickAct as the user's live meeting sidekick inside the current terminal agent session. Use when the user explicitly asks you, the terminal agent, to watch a meeting, follow the live transcript, answer during the call, offer strategist thoughts, silently watch for risks, or track decisions. Do not use this skill to start or control the separate Minutes Coach HUD; explicit Coach or HUD lifecycle requests belong to minutes-copilot, and an ambiguous request such as "coach me live" requires one short surface clarification.