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

88%

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

77%

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

The body is highly actionable with a clear, well-validated multi-phase workflow, but it carries redundancy and is a long single-file monolith with no progressive disclosure. Tightening repeated guidance and offloading the calendar-source fallback detail to a reference file would lift the weaker dimensions.

Suggestions

De-duplicate guidance that appears in both a phase and the Gotchas section (e.g. the first-name slug rule) — state it once and reference it.

Move the lengthy multi-source calendar auto-detect fallback (Google MCP, gog, osascript, m365) into a references/ file (e.g. CALENDAR_AUTODETECT.md) and keep SKILL.md as a concise overview that links to it.

Trim verbose explanatory prose around the m365 login flow and timezone handling to the essential decision logic.

Dimension	Reasoning	Score
Conciseness	Mostly actionable and free of explanations Claude already knows, but it repeats itself across phases and Gotchas (e.g. the first-name slug rule appears in Phase 4 and again in Gotchas) and the m365/calendar fallback prose could be tightened.	2 / 3
Actionability	Provides fully executable, copy-paste-ready commands (minutes search, minutes-learn-cli invocations, mkdir/chmod, gcal_list_events with parameters, m365 and osascript snippets) plus a complete prep-file template.	3 / 3
Workflow Clarity	Phases 0–5 are clearly sequenced with explicit validation checkpoints (m365 exit-code-0 and non-empty-array checks, skip rules, over-fetch+local-filter), branching error-recovery paths, and push-back guidance for vague inputs.	3 / 3
Progressive Disclosure	Well-organized into clear sections, but it is a ~220-line monolith with no bundle files or external references, and the detailed multi-source calendar fallback logic is inline content that could plausibly live in a reference file.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 concise, third-person, and clearly states both what the skill does and when to invoke it with a strong set of natural trigger phrases. It is a model example of a well-formed skill description.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — "builds a relationship brief and talking points before a call" — matching the anchor that lists several specific actions rather than a single vague verb.	3 / 3
Completeness	Explicitly answers both "what" (interactive meeting preparation building a relationship brief and talking points) and "when" via an explicit "Use when the user says..." clause with concrete triggers.	3 / 3
Trigger Term Quality	Includes a rich set of natural phrases a user would actually say ("prep me for my call with", "I'm meeting with X", "meeting prep", "get ready for my call", "what should I bring up with"), giving broad coverage of natural trigger terms.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (pre-call meeting preparation) with distinctive triggers unlikely to fire for unrelated skills, so conflict risk is low.	3 / 3
	Total	12 / 12 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: .opencode/skills/minutes-prep/SKILL.md
Commit: 7a61dd5

Reviewed: about 18 hours 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.