CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is minutes-search in silverstein/minutes

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a lean, command-driven reference for a single CLI tool: every section gives executable guidance, includes an explicit result-reauthorization requirement with exit-status validation, and documents real failure modes with concrete remediation commands. The main gaps are mild padding in the coaching section and an end-to-end workflow that must be assembled from multiple sections rather than read as one sequence.

Suggestions

Condense the 'Search coaching' section: keep the category-to-strategy mapping but drop the verbatim quoted replies, reducing it to one line per vague-query pattern.

Add a short ordered 'Workflow' section near the top (1. narrow vague queries, 2. `minutes search` with `--limit`, 3. reauthorize with `minutes get "<path>" --json` requiring exit 0) so the full sequence is readable in one place instead of being spread across Usage, Output, and Gotchas.

Consider moving the search-strategy tips and QMD setup details into a reference file (e.g., references/strategies.md) to keep SKILL.md focused on the core search-and-retrieve loop.

DimensionReasoningScore

Conciseness

Efficient throughout — usage block, flags table, output schema, and gotchas are all command-first with no explanations of concepts Claude already knows. Not 5: the "Search coaching" section's verbatim suggested replies (e.g., the full quoted responses for broad queries) are somewhat padded and could be condensed to the coaching rule itself.

4 / 5

Actionability

Copy-paste-ready commands everywhere: `minutes search "pricing strategy"`, `-t memo`, `--since 2026-03-01`, `minutes get "<exact path>" --json`, plus exact remediation commands (`qmd update && qmd embed`, `date -v-7d +%Y-%m-%d`). Common cases are covered with concrete examples; nothing is pseudocode.

5 / 5

Workflow Clarity

The flow is clear with an explicit validation checkpoint ("require exit status 0") and error-recovery paths (empty results → `minutes list`; unindexed QMD → `qmd update && qmd embed`), and vague-query coaching acts as a pre-flight check. Not 5: the end-to-end sequence (search → coach → reauthorize via `minutes get`) is distributed across Usage, Output, and Gotchas rather than presented as one ordered workflow.

4 / 5

Progressive Disclosure

No bundle files exist and the ~85-line body is well-organized into clearly labeled sections (Usage, Flags, Output, Gotchas) with nothing buried. Not 5: the skill exceeds the under-50-lines simple-skill threshold, and the Search coaching / Tips sections are arguably extractable reference material kept fully inline.

4 / 5

Total

17

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is a strong example: it states a concrete capability, defines the content domain (transcripts and voice memos), and provides an unusually rich set of natural trigger phrases covering questions, lookups, and decision recall. It uses third-person/neutral voice with no fluff or over-claims.

DimensionReasoningScore

Specificity

Names the domain ("meeting transcripts and voice memos") and enumerates concrete search targets ("specific topics, people, decisions, or ideas"), giving concrete coverage beyond the 1-2-action anchor. It stays at 4 rather than 5 because it relies on a single verb ("search") rather than listing multiple distinct actions.

4 / 5

Completeness

Explicitly answers both: what ("Search past meeting transcripts and voice memos for specific topics, people, decisions, or ideas") and when ("Use this whenever the user asks…" with concrete trigger phrases). Matches the top anchor verbatim in structure.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrasings with variations — "what did we discuss about X", "what did Alex say", "did we decide on", "do I have any notes about", "check my meetings for" — exactly the phrasings a user would naturally say. Not 4: essentially no common variation is missing.

5 / 5

Distinctiveness Conflict Risk

Clear niche (personal meeting-history search) with meeting-specific triggers ("find that meeting where we talked about Y", "check my meetings for"), giving minimal conflict risk. The only slight overlap is "do I have any notes about" with generic notes skills, which is not enough to drop to 4.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

silverstein/minutes

Path

.opencode/skills/minutes-search/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.