CtrlK
BlogDocsLog inGet started
Tessl Logo

outlook-calendar-shared-calendars

Safely write to delegated or shared Outlook calendars. Use when the user explicitly wants to create, update, respond to, cancel, delete, or add a small attachment to an event on a shared or delegated Outlook Calendar.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 tight, well-structured instruction-only skill that gives exact action-name routing, a sequenced workflow with pre-write validation checkpoints, and clear safety guardrails for high-impact shared-calendar writes. No bundle files are present or needed.

DimensionReasoningScore

Conciseness

The body is lean with no concept explanations Claude already knows; every line is routing or safety guidance and each token earns its place.

3 / 3

Actionability

Provides a concrete routing table mapping each intent to an exact action name (e.g. 'create_shared_calendar_event', 'update_shared_calendar_event'); per the instruction-only scoring note, the absence of code is not penalized because the guidance is specific and actionable.

3 / 3

Workflow Clarity

A clear 5-step sequence with explicit pre-write checkpoints — fetching event context and restating the exact target calendar/event before writes — plus error handling that forbids silent retry when the shared write is unavailable.

3 / 3

Progressive Disclosure

Under 50 lines with no external references needed and well-organized sections (Required Target, Action Routing, Workflow, Safety, Example Requests), which the rubric allows to score 3 for simple skills.

3 / 3

Total

12

/

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, specific, and complete: it names concrete write actions, includes an explicit 'Use when' trigger, and carves out a distinct shared/delegated-calendar niche. It reads naturally as something a user would say when they need this skill.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'create, update, respond to, cancel, delete, or add a small attachment' — matching the anchor for enumerating specific concrete actions rather than vague language.

3 / 3

Completeness

Answers both 'what' ('Safely write to delegated or shared Outlook calendars' plus enumerated actions) and 'when' via an explicit 'Use when the user explicitly wants to...' trigger clause.

3 / 3

Trigger Term Quality

Natural user-facing terms like 'create', 'cancel', 'shared calendar', 'delegated', 'Outlook Calendar', and 'attachment' cover the phrasings a user would actually say when requesting these writes.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche — delegated or shared Outlook calendars — and is explicitly scoped away from the signed-in user's own calendar, making conflict with the base Outlook skill unlikely.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
openai/plugins
Reviewed

Table of Contents

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.