meeting-prep

Prepare a comprehensive brief for an upcoming meeting. Gathers participant context, related emails, past meeting notes, and vault references into a structured prep document. Triggers: EN: "prepare for meeting", "meeting prep", "brief me for the meeting", "get ready for the call". IT: "prepara la riunione", "brief per il meeting", "preparami per la call". FR: "préparer la réunion", "brief pour le meeting". ES: "preparar la reunión", "brief para la reunión". DE: "Meeting vorbereiten", "Besprechung vorbereiten". PT: "preparar a reunião", "brief para o 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%Weight 40%Scale 1-3

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 concrete commands, templates, and a clearly sequenced procedure backed by validation checkpoints. Its main weakness is conciseness and progressive disclosure: no bundle files exist, so two full templates and a coordination protocol are kept inline in a monolithic ~275-line file.

Suggestions

Move the two full templates (Meeting Prep and Calendar Import) and the Inter-Agent Coordination protocol into reference files under references/ and link to them from SKILL.md to reduce inline length and enable progressive disclosure.

Tighten the body by summarizing repeated details across the Procedure, Error Handling, and Security sections, which restate command constraints (e.g., the allowed Bash commands) in several places.

Add a short Quick-start or summary block at the top of the body so the core single-pass workflow is scannable before the detailed procedure and templates.

Dimension	Reasoning	Score
Conciseness	The ~275-line body is mostly lean and instruction-oriented with no concept-padding, but it embeds two full templates and a coordination protocol inline that could be tightened or offloaded, matching the score-2 anchor of 'mostly efficient but could be tightened'.	2 / 3
Actionability	Provides concrete executable commands ('gws calendar events get', 'hey box imbox --json', 'hey threads <id> --json', specific MCP tool names) plus copy-paste-ready templates and exact naming conventions with examples, matching the score-3 anchor.	3 / 3
Workflow Clarity	A clear numbered six-step procedure is backed by explicit validation/fallback checkpoints (missing vault-map.md, missing role, ambiguous meeting) and a mandatory agent-state read/write protocol, matching the score-3 anchor for clear sequencing with checkpoints.	3 / 3
Progressive Disclosure	No bundle files exist (references/scripts/assets absent), so two full inline templates and the inter-agent coordination protocol that could live in separate references make this match the score-2 anchor of 'content that should be separate is inline'; sections are well-organized and references are one level deep, so not score 1, but the absence of any bundle prevents a score-3 split.	2 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 yet specific, listing four concrete actions and providing explicit natural-language triggers across six languages. It clearly answers both 'what does this do' and 'when should Claude use it' with minimal risk of conflicting with adjacent skills.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete actions — 'Gathers participant context, related emails, past meeting notes, and vault references into a structured prep document' — matching the score-3 anchor for listing several specific actions.	3 / 3
Completeness	Explicitly answers both what (prepare a comprehensive brief gathering context, emails, notes, vault references) and when (an explicit 'Triggers:' clause with concrete trigger phrases), satisfying the score-3 anchor's requirement for explicit triggers.	3 / 3
Trigger Term Quality	Natural phrases users would actually say ('prepare for meeting', 'meeting prep', 'brief me for the meeting', 'get ready for the call') plus equivalents in six languages, giving strong coverage matching the score-3 anchor.	3 / 3
Distinctiveness Conflict Risk	Clear niche of meeting preparation with calendar/email/vault integration and distinct triggers, making it unlikely to fire for the wrong skill — matches the score-3 anchor.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: gnekt/My-Brain-Is-Full-Crew
Path: skills/meeting-prep/SKILL.md
Commit: 238ae8c

Reviewed: 23 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.