outlook-calendar

Handle Outlook Calendar workflows, including delegated/shared calendar writes. Use when the user asks for schedule understanding, availability checks, meeting scheduling, intelligent rescheduling, meeting prep, reminder updates, RSVP responses, recurring maintenance, travel coordination, deadline planning, or safe create, update, reschedule, respond, attach, delete, or cancel changes with timezone-aware event times and attendee validation.

Quality

88%

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

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 content is highly actionable and well-sequenced with strong confirmation/validation checkpoints for risky calendar writes. Its main weaknesses are repetition that inflates the token budget and references to `resources/*.md` files that are not present in the bundle.

Suggestions

Consolidate the repeated shared-calendar free/busy guidance into a single section; it currently restates the same nuance in Overview, Outlook-Specific Checks, Write Safety, and Output Conventions.

Create the referenced `resources/recurring-meetings.md`, `resources/travel-coordination.md`, `resources/reminder-planning.md`, and `resources/availability-response.md` files, or remove the references if the content is meant to stay inline.

Tighten the Output Conventions list, which overlaps with Preferred Deliverables, to reduce token cost while keeping the concrete format examples.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient operational guidance assuming Claude's competence, but at ~180 lines it repeats itself across sections (e.g. shared-calendar free/busy nuance appears in Overview, Outlook-Specific Checks, Write Safety, and Output Conventions), which is more token spend than a lean skill needs.	2 / 3
Actionability	It gives concrete, executable guidance: named tools (`list_events`, `search_events`, `fetch_event`), explicit parameters (`start_datetime`/`end_datetime`), named SharePoint tools (`get_site`, `search(query=...)`, `fetch`), and precise output formats (title, attendees, start, end, timezone, location/Teams link).	3 / 3
Workflow Clarity	The Workflow section sequences grounding → scheduling reasoning → confirmation/writes with numbered steps and explicit validation checkpoints (e.g. step 8 'stop and confirm before editing', step 18 'restate the final interpreted weekday, date, local clock time, and timezone', step 15 verify attendee availability or say it cannot be verified).	3 / 3
Progressive Disclosure	The body references four `resources/*.md` files and five sibling specialized skills, which is good one-level navigation in principle, but none of the referenced `resources/` files actually exist on disk (only `assets/` SVGs are present), so the signaling points to missing material.	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 specific, trigger-rich, and complete, with both a clear capability statement and an explicit 'Use when' clause covering many natural user phrasings. It is on the long side but every phrase earns its place and third-person voice is maintained throughout.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions — 'schedule understanding, availability checks, meeting scheduling, intelligent rescheduling, meeting prep, reminder updates, RSVP responses, recurring maintenance, travel coordination, deadline planning' and 'create, update, reschedule, respond, attach, delete, or cancel changes' — matching the score-3 anchor that lists multiple specific concrete actions.	3 / 3
Completeness	It clearly answers 'what' (handle Outlook Calendar workflows including delegated/shared calendar writes) and 'when' via an explicit 'Use when the user asks for...' clause, satisfying the score-3 anchor requiring both with explicit triggers.	3 / 3
Trigger Term Quality	The 'Use when...' clause surfaces natural user phrasings such as 'availability checks', 'meeting scheduling', 'reschedule', 'RSVP responses', 'meeting prep', and 'travel coordination' that a user would actually say, giving good coverage of natural terms.	3 / 3
Distinctiveness Conflict Risk	The Outlook Calendar scope plus explicit delegation/shared-calendar distinction and the enumerated trigger list carve a clear niche unlikely to fire for unrelated skills.	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
relative_links	Relative link issues: 6 suspicious	Warning

	Total	15 / 16 Passed

Repository: openai/plugins
Path: plugins/outlook-calendar/skills/outlook-calendar/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.