CtrlK
BlogDocsLog inGet started
Tessl Logo

minutes-prep

Interactive meeting preparation — builds a relationship brief and talking points before a call. Use when the user says "prep me for my call with", "I'm meeting with X", "prepare me for", "what should I bring up with", "meeting prep", "get ready for my call", or wants to review history with someone before a meeting.

68

Quality

82%

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

75%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 well-sequenced, highly actionable multi-phase workflow with concrete commands and templates. Its main weakness is conciseness, as the calendar fallback and gotchas sections run long and partly restate earlier guidance.

Suggestions

Move the multi-source calendar auto-detect fallbacks (Google MCP, gog, osascript, m365) into a separate reference file and keep only the selection order plus the silent-fallback rule in SKILL.md to improve conciseness and progressive disclosure.

Tighten the Gotchas section by removing points that restate phase instructions (e.g., push-back-on-vague, first-name slug, zero-past-meetings already covered in phases), keeping only net-new edge cases.

Add an explicit validation checkpoint in Phase 4 (e.g., verify the prep file exists and is 0600, and confirm the date/slug so /minutes-debrief will pick it up) to raise workflow clarity.

DimensionReasoningScore

Conciseness

Mostly efficient but includes sections that could be tightened, notably the dense Phase 0 calendar fallbacks (Google MCP, gog, osascript, m365) and gotchas that restate phase content; it is not a 4 because the over-explanation is more than minor, and not a 2 because most content earns its place rather than being heavily padded.

3 / 5

Actionability

Fully executable guidance throughout: concrete bash commands (minutes search, m365 outlook event list, chmod 600), an MCP call signature, exact file paths, and a copy-paste prep-file template covering the common cases.

5 / 5

Workflow Clarity

Clear Phase 0-5 sequence with most checkpoints present (require exit status 0, never reopen search paths with Read, m365 login feedback loop); it is not a 5 because Phase 4 lacks an explicit verify step after writing the prep file and some validation is implicit.

4 / 5

Progressive Disclosure

Single-file skill with well-organized section headers and no bundled references present; good structure, but the lengthy calendar auto-detect section could plausibly be split into a separate reference, keeping it just below a 5.

4 / 5

Total

16

/

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.

The description is strong: it states a clear purpose, includes many natural trigger phrases, and explicitly pairs a 'what' with a 'when'. The only mild weakness is specificity, which lists just two concrete actions rather than a fuller enumeration.

DimensionReasoningScore

Specificity

Names the meeting-prep domain with two concrete actions ("builds a relationship brief and talking points"), matching the 1-2 concrete actions anchor; it is not a 4 because only two actions are listed rather than several.

3 / 5

Completeness

Explicitly answers both what (builds a relationship brief and talking points before a call) and when ("Use when the user says ...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive set of natural phrases users would actually say ("prep me for my call with", "I'm meeting with X", "prepare me for", "what should I bring up with", "meeting prep", "get ready for my call"), covering synonyms and variations.

5 / 5

Distinctiveness Conflict Risk

Clear niche (pre-call relationship brief from meeting history) with distinct triggers that are unlikely to fire for unrelated skills, minimizing conflict risk.

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.

Validation16 / 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.