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.

76

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

An efficient, actionable, well-organized skill body that gives exactly what is needed to run `minutes note` in both modes without bloat. No bundle files exist, which is appropriate given the skill's small scope.

DimensionReasoningScore

Conciseness

Lean, command-first content with no padding of concepts Claude already knows; the only discursive sentence (note weight in the summarizer) earns its place as product behavior, not filler.

3 / 3

Actionability

Provides concrete, copy-paste-ready `minutes note "..."` commands with realistic example notes and a complete `--meeting <path>` invocation for the after-meeting case.

3 / 3

Workflow Clarity

For a simple skill, the two modes (during-recording vs after-meeting) are clearly separated, each with a worked example, and the gotchas supply a validation checkpoint (check `minutes status` before a live note, fall back to `--meeting`).

3 / 3

Progressive Disclosure

A compact, single-purpose skill under 50 lines with no bundle files to offload; the body is well-organized into clear sections, which is sufficient for a score of 3 per the simple-skills guidance.

3 / 3

Total

12

/

12

Passed

Description

90%

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, natural trigger phrases and a clear what-and-when structure. The only soft spot is specificity, which names just two actions rather than a richer, comprehensive list.

Suggestions

Broaden the capability list beyond the two named actions (e.g., mention that notes are timestamped to the recording position and become searchable) to lift specificity to a comprehensive set.

DimensionReasoningScore

Specificity

Names two concrete actions ("Add a note to the current recording", "annotate a past meeting") but stops there rather than listing a broader, comprehensive set of specific actions.

2 / 3

Completeness

Explicitly states what it does and pairs it with an explicit "Use whenever the user says..." trigger clause, satisfying both the 'what' and 'when' requirements.

3 / 3

Trigger Term Quality

Quotes natural verbatim phrases a user would say ("note that", "remember this", "mark this as important", "add a note about", "annotate the meeting"), giving strong coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The niche (timestamped notes on meeting recordings) plus recording/meeting-specific triggers make it clearly distinguishable and unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

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.