- name
SKILL.md
Die Skill-Datei bleibt im Repository des Herausgebers.
Fügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add silverstein/minutes --skill minutes-search -a cursor -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add silverstein/minutes --skill minutes-search -a claude-code -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add silverstein/minutes --skill minutes-search -a codex -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add silverstein/minutes --skill minutes-search -a grok -ySenden Sie die kopierte Nachricht in einem Grok Bot-Chat. Der Bot ruft diese SKILL.md von GitHub ab und fügt sie den Skills hinzu, die alle Ihre Bots gemeinsam nutzen.
Install this skill: https://github.com/silverstein/minutes/tree/HEAD/.agents/skills/minutes/minutes-searchVom Herausgeber
Find information across all meeting transcripts and voice memos.
# 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
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 fileHuman-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.
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"
When the user's search query is vague or too broad, push back before running it:
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).Suggest search strategies based on what the user is looking for:
minutes search "Alex"minutes search "decided" or minutes search "agreed"minutes search "idea" -t memo--since: minutes search "pricing" --since 2026-03-01"we should postpone the launch" not "launch delay meeting""Alex" or "Case""decided", "agreed", "committed to"minutes get "<exact path>" --json before loading full context"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.--limit when searching broad terms. The default limit is 10, but common words can match hundreds of files.config.toml sets engine = "qmd" but the QMD collection isn't indexed, search will fail silently. Run qmd update && qmd embed first.-t memo or -t meeting to narrow results. Voice memos live in ~/meetings/memos/, meetings in ~/meetings/.minutes list to see what's been processed.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 abou
---name: minutes-searchdescription: Search past meeting transcripts and voice memos for specific topics, people, decisions, or ideas. Use this…---# .agents/skills/minutes/minutes-search/SKILL.mdÜbersicht
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".
FAQ
Laden Sie .agents/skills/minutes/minutes-search/SKILL.md vom Herausgeber herunter oder kopieren Sie den Pfad und öffnen Sie das Repository. PlugMCP listet den Skill und hostet die Datei nicht.
Der Herausgeber pflegt es unter https://github.com/silverstein/minutes.
Claude, Cursor, Codex und Grok Build können eine SKILL.md lesen, die Sie aus dem Repository des Herausgebers hinzufügen. Grok Bot installiert sie, wenn Sie den Link zum GitHub-Ordner des Skills in einem Chat senden.