Minutes Search
Search past meeting transcripts and voice memos for specific topics, people, decisions...
Install
npx skills add silverstein/minutes --skill minutes-search -g -a claude-code -y- Repository
- silverstein/minutes1.6k
- Category
- Writing
- Updated
- 3d ago
- License
- MIT
- Context cost
- Lightabout 1,086 tokens
- Runs scripts
- No, instructions only
What it does
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
# 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 titledate, When it was recordedcontent_type, "meeting" or "memo"snippet, The line containing the matchpath, Full path to the markdown file
Human-readable output goes to stderr. A result path is only a hint. To read the
full transcript, run minutes get "<exact path>" --json, require exit status 0,
and use only that response. Never pass the path to cat or the host Read tool.
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:
[search]
engine = "qmd"
qmd_collection = "meetings"
Search coaching
When the user's search query is vague or too broad, push back before running it:
