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.

Quality

93%

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

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.

Excellent body for a simple, single-purpose skill: fully executable commands, explicit failure modes with their remedies, and tight prose with no over-explanation. It models the right pattern — short, command-first, gotcha-aware content that assumes Claude's competence.

Dimension	Reasoning	Score
Conciseness	The ~40-line body is lean with zero padding: two command blocks, behavior facts Claude cannot infer ("Notes feed into the LLM summarizer as high-priority context", timestamps like "[4:23]"), and dense Tips/Gotchas where every line is actionable.	5 / 5
Actionability	Commands are copy-paste ready and cover the common cases: live notes ("minutes note \"...\""), annotating a past meeting with a concrete --meeting path example, and quote escaping ("minutes note 'Alex said \"no way\"'").	5 / 5
Workflow Clarity	A simple single-task skill with two unambiguous paths (during a recording / after a meeting), and the gotchas section supplies an explicit pre-check ("Check with `minutes status` first") plus the fallback (--meeting) for the failure case; the non-destructive operation means no validation cap applies.	5 / 5
Progressive Disclosure	Under 50 lines with no bundle files present, the skill needs no external references; its well-organized sections (During a recording, After a meeting, Tips, Gotchas) satisfy the simple-skill guideline for a top score.	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 that clearly states what it does and when to use it, with excellent natural-language trigger coverage in third-person voice. Its only weakness is modest action specificity — it names two core actions but omits capabilities (auto-timestamping, notes feeding the summarizer, searchability) that would sharpen the what.

Suggestions

Extend the capability sentence with one or two more concrete actions, e.g. "Notes are auto-timestamped to the recording position and feed into the AI meeting summary."

Narrow the generic triggers ("remember this") with meeting/recording context, e.g. "remember this about the meeting", to reduce overlap with general note-taking or memory skills.

Dimension	Reasoning	Score
Specificity	Names the domain and exactly two concrete actions ("Add a note to the current recording", "annotate a past meeting") with a concrete input-format note ("Plain text input — no markdown needed"), but stops short of the comprehensive action coverage (e.g., timestamping, searchability) that would merit a 4.	3 / 5
Completeness	Explicitly answers both questions: the first sentence states what the skill does, and "Use whenever the user says..." states when with concrete trigger phrases, matching the top anchor exactly.	5 / 5
Trigger Term Quality	Six quoted natural trigger phrases ("note that", "remember this", "mark this as important", "add a note about", "annotate the meeting") plus "capture a thought during or after a recording" give comprehensive synonym coverage of how users would naturally phrase this need.	5 / 5
Distinctiveness Conflict Risk	The recording/meeting niche and phrases like "annotate the meeting" are distinct, but generic triggers such as "remember this" carry minor overlap risk with general memory or note-taking skills, so it sits between the mostly-distinct (4) and minimal-conflict (5) anchors.	4 / 5
	Total	17 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: silverstein/minutes
Path: .claude/plugins/minutes/skills/minutes-note/SKILL.md
Commit: 39bb670

Reviewed: 8 days 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.