Agent skill · Workflow & Productivity

minutes-search

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".

silversteingithub.com/silversteinGitHub ↗
claude-codeMIT
Install
npx skills add silverstein/minutes --skill minutes-search --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Requires: opencode
Path: .opencode/skills/minutes-search/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,410
Language: Rust

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# /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. 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

What's inside
Steps it walks through
  1. Usage
  2. Flags
  3. Output
  4. How search works
  5. Search coaching
  6. Tips for good searches
  7. Gotchas
Commands it runs
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
More from minutes
All skills →
About this skill
What does the minutes-search skill do?

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".

How do I install it?

Run `npx skills add silverstein/minutes --skill minutes-search --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From silverstein/minutes, a repository with 1,410 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going