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.

Quality

82%

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

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.

A highly actionable, well-sequenced interactive workflow with concrete commands and validation checkpoints throughout. Its main weakness is conciseness: the Gotchas section duplicates guidance already present in the phases, and the m365 timezone handling is explained twice.

Suggestions

Consolidate the Gotchas section so it only captures guidance not already stated inline in the phases (e.g. drop the duplicated all-day/solo-event, first-name-slug, and zero-meetings notes that already appear in Phase 0/2/4).

Explain the m365 over-fetch + local-filter timezone rationale once (in Phase 0) and have the Gotchas entry point back to it instead of restating the full reasoning.

Spell out the error-recovery loop for failed reauthorization in Phase 2 (e.g. what to do when 'minutes get' exits non-zero) to reach a full feedback-loop checkpoint.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and assumes Claude's competence (no basic-concept padding), but the Gotchas section restates several decisions already embedded in the phases and the m365 timezone handling is explained in detail both in Phase 0 and again in Gotchas, which could be tightened.	3 / 5
Actionability	Fully executable, copy-paste-ready commands with real flags and parameters (e.g. 'minutes search "<name>" --limit 50', 'm365 outlook event list --userId "@meId" ...'), plus concrete JSON field paths, AskUserQuestion prompts, and a concrete prep-file template.	5 / 5
Workflow Clarity	Clear Phase 0-5 sequence with explicit skip/branch conditions and validation checkpoints (require exit status 0 for m365 and 'minutes get'), but error-recovery loops are only partially spelled out (what to do on non-zero 'minutes get' is not fully specified), so it falls short of the 5 anchor's explicit fix-and-retry feedback.	4 / 5
Progressive Disclosure	Well-organized into numbered phases with clear headers and conditional logic, and inlining is defensible for an interactive flow; no bundle files exist so there are no references to signal, and the dense m365 sub-procedure plus duplicated Gotchas are minor organization gaps rather than misplacement.	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.

A strong, third-person description that cleanly states what the skill does and when to invoke it via a rich set of natural trigger phrases. The only soft spot is specificity, which lists just two somewhat abstract actions rather than a comprehensive set.

Dimension	Reasoning	Score
Specificity	Names the domain ('Interactive meeting preparation') and two concrete actions ('builds a relationship brief and talking points'), matching the 1-2 concrete actions anchor; it does not list several specific actions so it stays below 4.	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 coverage of natural phrases users would say, including synonyms ('prep', 'prepare', 'get ready') and variations like 'I'm meeting with X' and 'what should I bring up with'.	5 / 5
Distinctiveness Conflict Risk	Clear pre-meeting niche with distinct triggers ('prep me for my call with', 'meeting prep') that are unlikely to fire for unrelated or post-meeting skills.	5 / 5
	Total	18 / 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-prep/SKILL.md
Commit: a9a4a8b

Reviewed: 1 day 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.