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

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

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.

A well-structured, actionable skill body with concrete commands, a real validation checkpoint for result handling, and useful coaching for vague queries. Slightly verbose in the coaching/tips overlap and could benefit from an explicit feedback loop for the QMD indexing failure case.

Suggestions

Consolidate the overlapping 'Search coaching' and 'Tips for good searches' sections to remove restated guidance and tighten conciseness.

Add an explicit validate→fix→retry loop for the QMD engine case (e.g., if `engine = "qmd"` search returns nothing, run `qmd update && qmd embed`, then re-run) rather than a one-line remediation hint.

Trim restated constraints in 'Gotchas' that already appear under 'Output' or 'Flags' to reduce token cost.

Dimension	Reasoning	Score
Conciseness	Mostly lean and assumes Claude's competence (e.g., the Gotchas deliver dense, useful constraints); a few sections restate guidance found elsewhere (coaching vs. tips) that could be tightened.	4 / 5
Actionability	Fully executable, copy-paste-ready commands covering common cases — `minutes search` with flags, an exact config.toml snippet, `date -v-7d +%Y-%m-%d` for relative dates, and `minutes get "<exact path>" --json` with an exit-status requirement.	5 / 5
Workflow Clarity	Clear sequencing with an explicit validation checkpoint ("require exit status 0, and use only that response") before trusting a result and a guard against `cat`/Read; minor gap is the absent validate→fix→retry loop for the QMD-not-indexed failure beyond a one-line remediation hint.	4 / 5
Progressive Disclosure	Well-organized into clearly labeled sections (Usage, Flags, Output, How search works, Coaching, Tips, Gotchas) with no bundle files present; sits just above the under-50-line simple-skill exception, so structure is good but not the maximal single-section case.	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.

A strong, trigger-rich description that clearly states the capability and gives extensive natural-language triggers a user would actually say. Uses third-person/infinitive voice with no first- or second-person phrasing. Minor specificity gap only in not describing the output form.

Dimension	Reasoning	Score
Specificity	Names the domain and enumerates several concrete search targets — "specific topics, people, decisions, or ideas" across "meeting transcripts and voice memos" — with only minor gaps in coverage (no mention of output or result handling).	4 / 5
Completeness	Explicitly answers both what (search transcripts/memos for topics/people/decisions/ideas) and when ("Use this whenever the user asks..." with concrete trigger phrases).	5 / 5
Trigger Term Quality	Comprehensive verbatim natural trigger phrases are quoted — "what did we discuss about X", "what did Alex say", "did we decide on", "do I have any notes about", "check my meetings for" — covering synonyms and user-said variations.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (personal meeting transcripts and voice memos) with distinct, user-specific triggers, giving minimal conflict risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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: .agents/skills/minutes/minutes-search/SKILL.md
Commit: a9a4a8b

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.