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.

72

Quality

90%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a tight, executable, well-structured skill for a single-purpose task, with concrete commands and a useful gotchas section. The only minor gap is the absence of an explicit retry/feedback loop on the live-note validation step.

DimensionReasoningScore

Conciseness

Lean and efficient: every section earns its place with executable commands and targeted gotchas, no padding or explanation of concepts Claude already knows. Re-reading the 4-anchor ('minor instances of over-explanation that could be trimmed') it fits better at 5 since there is nothing to trim.

5 / 5

Actionability

Fully executable, copy-paste-ready commands cover both common cases ('minutes note "..."' for live and '--meeting <path>' for past meetings), with concrete real example strings and exact escaping guidance.

5 / 5

Workflow Clarity

The two paths (live vs. past meeting) are clearly separated, and the live path includes an explicit validation checkpoint ('Check with minutes status first') plus a fallback ('use --meeting <path>'). Held at 4 rather than 5 because there is no explicit retry/feedback loop, though the append-only past-meeting path is non-destructive so the destructive cap does not apply.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references; content is well-organized into clear sections (During a recording, After a meeting, Tips, Gotchas) satisfying the simple-skill exception for a 5.

5 / 5

Total

19

/

20

Passed

Description

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

The description is strong across all dimensions: concrete actions, comprehensive natural trigger phrases, and explicit what/when guidance with minimal conflict risk. It is written in third person and avoids fluff.

DimensionReasoningScore

Specificity

Names concrete actions ('Add a note to the current recording', 'annotate a past meeting', 'capture a thought') plus a constraint ('Plain text input — no markdown needed'), giving several specific actions with only minor coverage gaps; not a full 5 because it lists ~2-3 actions rather than a comprehensive multi-action set.

4 / 5

Completeness

Clearly answers both 'what' ('Add a note to the current recording or annotate a past meeting') and 'when' with an explicit 'Use whenever...' clause listing concrete trigger phrases.

5 / 5

Trigger Term Quality

Provides comprehensive natural trigger phrases users would actually say — 'note that', 'remember this', 'mark this as important', 'add a note about', 'annotate the meeting' — covering synonyms and variations.

5 / 5

Distinctiveness Conflict Risk

Targets a clear niche (meeting recording annotation) with distinct, specific triggers that are unlikely to fire for unrelated skills.

5 / 5

Total

19

/

20

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.