outlook-calendar-meeting-prep

Build a practical meeting prep brief from an Outlook Calendar event and its nearby Microsoft context. Use when the user wants to prepare for an upcoming meeting, understand what to read beforehand, pull in linked notes or docs, or get a concise brief on what the meeting appears to require.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

70%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 a well-structured, lean instruction-only skill that assumes Claude's competence and gives a sequenced workflow with an explicit recheck checkpoint. Its main weakness is a duplicated Output Conventions section that wastes tokens, and several workflow steps that stay abstract despite the concrete tool and formatting guidance elsewhere.

Suggestions

Merge the two '## Output Conventions' sections into one — the second (lines 42-49) repeats the first with minor additions; consolidate to remove redundant tokens.

Tighten abstract workflow steps like 'inspect them before writing the brief' and 'Build the prep brief around what the meeting appears to be for' into more concrete, actionable instructions (e.g., specify which fields to read first and what a prep-brief skeleton looks like).

Consider adding a short concrete brief template under Output Conventions so the output structure is copy-paste ready rather than implied.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of concept-overexplaining, but the body contains two near-duplicate '## Output Conventions' sections (lines 28-33 and 42-49) that rehash the same lead/call-out/separate-confirmed/list-ending guidance, which is unnecessary token spend that could be tightened into one section.	2 / 3
Actionability	Concrete elements are present — named tools (fetch_event, fetch_events_batch, search_events), a 5-minute threshold, and specific formatting rules ('one concise agenda block', 'keep the update plain text', 'use HTML deliberately') — but several core steps ('inspect them before writing the brief', 'Build the prep brief around what the meeting appears to be for') stay abstract, so guidance is incomplete rather than copy-paste ready.	2 / 3
Workflow Clarity	The 9-step Workflow is clearly sequenced and includes an explicit checkpoint (step 7: recheck the meeting is still upcoming after 5 minutes before updating/presenting), which is a concrete feedback gate; for a non-destructive meeting-prep task this meets the 'clear sequence with explicit validation steps' anchor.	3 / 3
Progressive Disclosure	This is a self-contained, single-purpose skill under 50 lines with no bundle files and no external references; per the simple-skills note, well-organized sections (Relevant Actions, Workflow, Output Conventions, Outlook-Specific Focus) earn the top score, and there are no nested reference chains to penalize.	3 / 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.

A strong, third-person description that states concrete capabilities and provides an explicit, multi-trigger 'Use when' clause tied to a distinct Outlook/Microsoft niche. It is concise without padding and clearly answers both what the skill does and when to invoke it.

Dimension	Reasoning	Score
Specificity	Names concrete actions — 'Build a practical meeting prep brief' and 'pull in linked notes or docs' — against a specific Outlook/Microsoft context, matching the 'lists multiple specific concrete actions' anchor rather than the single-domain score-2 example.	3 / 3
Completeness	Explicitly answers both 'what' (build a prep brief from an Outlook event and nearby Microsoft context) and 'when' (an explicit 'Use when...' clause with several trigger conditions), matching the top anchor.	3 / 3
Trigger Term Quality	Covers natural phrases a user would say — 'prepare for an upcoming meeting', 'what to read beforehand', 'linked notes or docs', 'concise brief' — giving broad coverage of common variations rather than a single keyword.	3 / 3
Distinctiveness Conflict Risk	The Outlook Calendar + Microsoft context framing carves a clear niche with distinct triggers, making it unlikely to fire for unrelated skills; it is well above the 'somewhat specific but could overlap' score-2 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: openai/plugins
Path: plugins/outlook-calendar/skills/outlook-calendar-meeting-prep/SKILL.md
Commit: 11c74d6

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