CtrlK
BlogDocsLog inGet started
Tessl Logo

minutes-note

Add a note to the current recording or annotate a past meeting. Use whenever the user says "note that", "remember this", "mark this as important", "add a note about", "annotate the meeting", or wants to capture a thought during or after a recording. Plain text input — no markdown needed.

75

Quality

94%

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-note 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-form skill body: entirely executable commands with concrete realistic examples, lean prose with no filler, clear separation of the two usage modes, and an explicit pre-flight validation step in the Gotchas. Nothing is padded and nothing important is missing.

DimensionReasoningScore

Conciseness

The ~40-line body is lean and efficient with zero padding: every line is an executable command example, a tip, or a gotcha. No concepts Claude already knows are explained, matching anchor 5 ('every token earns its place').

5 / 5

Actionability

Commands are fully executable and copy-paste ready — `minutes note "Alex wants monthly billing not annual billing"` and `minutes note "..." --meeting ~/meetings/2026-03-17-pricing-call.md` — with realistic examples covering both the live-recording and post-meeting cases, matching anchor 5.

5 / 5

Workflow Clarity

A simple single-purpose skill under 50 lines whose two modes (during a recording vs. after a meeting) are cleanly separated into sections, with an explicit checkpoint ('Check with `minutes status` first') for the risky live-note case. The simple-skill exception applies and the action is unambiguous; it is not destructive or batch.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external reference files (none exist in the bundle), and the content is organized into clear, well-labeled sections (During a recording / After a meeting / Tips / Gotchas), so the sub-50-line guideline yields anchor 5.

5 / 5

Total

20

/

20

Passed

Description

86%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 explicit and comprehensive trigger phrasing, clear what/when coverage, and third-person voice. The only weakness is that it names just two concrete actions, and its generic trigger phrases ('remember this') slightly raise conflict risk with memory-style skills.

DimensionReasoningScore

Specificity

"Add a note to the current recording or annotate a past meeting" names the domain and two concrete actions covering both usage modes, but only two actions are listed, matching anchor 3 ('Names domain and 1-2 concrete actions') rather than anchor 4 which expects several specific actions.

3 / 5

Completeness

It explicitly answers both what ("Add a note to the current recording or annotate a past meeting") and when ("Use whenever the user says...") with concrete quoted trigger phrases, exactly matching anchor 5.

5 / 5

Trigger Term Quality

The description includes comprehensive natural trigger phrases — "note that", "remember this", "mark this as important", "add a note about", "annotate the meeting", "capture a thought" — covering synonyms and both during/after contexts, matching anchor 5. No common variations are missing.

5 / 5

Distinctiveness Conflict Risk

The meeting/recording niche is mostly distinct, but broad phrases like "remember this" and "mark this as important" carry minor overlap risk with memory or general note-taking skills, fitting anchor 4 rather than 5.

4 / 5

Total

17

/

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.