CtrlK
BlogDocsLog inGet started
Tessl Logo

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

72

Quality

89%

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

88%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 and an explicit validation checkpoint. It is efficient rather than fully lean, and at ~90 lines it is slightly past the simple-skill threshold where structure alone would justify a top progressive-disclosure score.

Suggestions

Tighten the 'Search coaching' section by collapsing the four vague-query bullets into a single short decision rule to improve conciseness.

Consider moving the 'Gotchas' list into a separate references file to bring SKILL.md closer to a lean overview and lift progressive_disclosure.

DimensionReasoningScore

Conciseness

Efficient and assumes Claude's competence (no concept explanations), with copy-paste commands and a tight flags table; the 'Search coaching' and 'Tips' sections are somewhat verbose but actionable, so it sits between efficient and lean.

4 / 5

Actionability

Fully executable guidance throughout — concrete `minutes search` examples, a flags table, exact `minutes get "<path>" --json` reauthorization, a config.toml snippet, and helper commands like `date -v-7d +%Y-%m-%d` and `qmd update && qmd embed`.

5 / 5

Workflow Clarity

Single-purpose skill with an unambiguous action and an explicit validation checkpoint ('require exit status 0, and use only that response') for the reauthorize step; the simple-skill exception applies and there are no destructive/batch operations triggering the cap.

5 / 5

Progressive Disclosure

Well-organized into clear sections (Usage, Flags, Output, How search works, Search coaching, Tips, Gotchas) with no nested references, but at ~90 lines it exceeds the under-50-line simple-skill threshold and the coaching/gotchas content could plausibly live in a separate reference.

4 / 5

Total

18

/

20

Passed

Description

90%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 description with excellent trigger-term coverage and a clear, explicit what/when structure. The only soft spot is specificity, since the skill is described as a single action (search) applied to several target categories rather than multiple distinct operations.

Suggestions

Consider naming one or two additional concrete actions beyond 'Search' (e.g., 'Search and retrieve past meeting transcripts...') to lift specificity above a single-verb description.

DimensionReasoningScore

Specificity

Names the domain (meeting transcripts/voice memos) and several specific search targets (topics, people, decisions, ideas), but the action is singular ('Search') rather than multiple distinct actions, matching the 'names domain and 1-2 concrete actions' anchor.

3 / 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, matching the top anchor.

5 / 5

Trigger Term Quality

Comprehensive coverage of natural user phrasings ('what did we discuss about X', 'find that meeting where we talked about Y', 'what did Alex say', 'do I have any notes about', 'check my meetings for') with synonym variation, matching the top anchor.

5 / 5

Distinctiveness Conflict Risk

Clear niche (meeting history search) with distinct triggers unlikely to overlap with general file or document skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.

5 / 5

Total

18

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
silverstein/minutes
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.