CtrlK
BlogDocsLog inGet started
Tessl Logo

minutes-list

List recent meetings and voice memos. Use when the user asks "what meetings did I have", "show my recent recordings", "any meetings today", "list my voice memos", or wants an overview of their meeting history. Also use when they need to find a specific meeting by browsing rather than searching.

76

Quality

96%

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-list in silverstein/minutes

SKILL.md
Quality
Evals
Security

Quality

Content

100%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.

An exemplary short skill: fully executable commands covering common variations, a precise output contract with a sensible safety rule for consuming returned paths, and four specific, non-obvious gotchas. Nothing is padded and nothing is missing for the task it covers.

DimensionReasoningScore

Conciseness

Every section earns its place: four one-line executable commands, a compact output schema, a non-obvious path-reauthorization rule, and four genuinely surprising gotchas. Nothing explains concepts Claude already knows, matching the 'lean and efficient' anchor rather than 4's 'minor instances of over-explanation'.

5 / 5

Actionability

Commands are copy-paste ready and cover the common cases: `minutes list`, `--limit 20`, `-t memo`, `-t meeting`, plus the follow-up read path `minutes get "<exact path>" --json` and `minutes status` for in-progress checks. Matches anchor 5's 'fully executable, specific examples cover the common cases'; anchor 4 would imply gaps in coverage of common cases.

5 / 5

Workflow Clarity

This is a simple single-purpose skill whose primary action (list) is unambiguous with concrete variants, which scores 5 under the simple-skill exception. The secondary read workflow is even sequenced with an explicit checkpoint ('require exit status 0', 'Never reopen a result path with the host Read tool'); no destructive or batch operation triggers the validation cap.

5 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external references (none exist in the bundle), and is cleanly organized into Usage, Output, and Gotchas sections. This meets the short-skill exception for a top score; there is no inline content that belongs in a separate file.

5 / 5

Total

20

/

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 an explicit 'Use when' clause and highly natural quoted trigger phrases that comprehensively cover how users would ask for this capability. The only weakness is that the 'what' states a single action (listing) without mentioning capabilities like type filtering, limit control, or JSON output, which slightly caps specificity.

Suggestions

Mention one or two more concrete capabilities in the 'what' clause, e.g. 'List recent meetings and voice memos, filter by type, and return them newest-first as JSON' — this would raise specificity from anchor 3 to 4.

Optionally note the output shape (entries with title, date, content_type, path) so the description also signals what the caller gets back, distinguishing it further from sibling minutes skills.

DimensionReasoningScore

Specificity

Names the domain ("meetings and voice memos") and one concrete action ("List recent"), but does not list several specific actions such as filtering by type, adjusting limits, or output format. It fits anchor 3 (1-2 concrete actions, not comprehensive) better than 4, which requires several specific actions with only minor gaps.

3 / 5

Completeness

Explicitly answers what ("List recent meetings and voice memos") and when ("Use when the user asks ... " with concrete quoted trigger phrases, plus a secondary browse-vs-search use case). This matches the anchor-5 example's structure; anchor 4 would require the 'when' to be less explicit than these verbatim triggers.

5 / 5

Trigger Term Quality

Quotes comprehensive natural user phrases — "what meetings did I have", "show my recent recordings", "any meetings today", "list my voice memos" — covering synonyms (meetings/recordings/voice memos) and recency variants (recent/today). Not 4: no common natural phrasing for this need is obviously missing.

5 / 5

Distinctiveness Conflict Risk

Clear niche (listing meeting/voice-memo recordings) with distinct quoted triggers, and "find a specific meeting by browsing rather than searching" explicitly separates it from sibling search/get skills. Not 4: the triggers are specific enough that overlap risk is minimal.

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.

Validation — 16 / 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.