CtrlK
BlogDocsLog inGet started
Tessl Logo

outlook-email-shared-mailboxes

Work with delegated or shared Outlook Email mailboxes. Use when the user explicitly wants to read another mailbox, send from or on behalf of a shared mailbox, mark shared mail read or unread, move shared mail, or browse folders in a shared mailbox.

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

Low

Low-risk findings worth noting

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.

A tight, well-structured routing skill that distinguishes shared-mailbox actions from signed-in-user actions, names exact tools and parameters, and bakes safety and error-handling into the workflow. It is concise and actionable with no wasted tokens.

DimensionReasoningScore

Conciseness

Lean, sectioned routing guidance with no explaining of concepts Claude already knows — e.g. "Require the exact delegated/shared mailbox owner email address or UPN" and "Treat send_email_on_behalf as high impact"; every line earns its place. Not a 2 because there is no padding to tighten.

3 / 3

Actionability

Concrete, executable references throughout — named actions (list_shared_messages, fetch_shared_message, send_email_on_behalf, mark_shared_email_read_state, move_shared_email) and the exact parameter mailbox_user_principal_name; per the instruction-skill scoring note, absence of code is not penalized when guidance is this specific. Not a 2 because the action and parameter names are copy-paste concrete, not pseudocode.

3 / 3

Workflow Clarity

A clear 5-step sequence with a pre-write checkpoint ("say which mailbox is being used before performing the write") and explicit error recovery ("If a write fails because shared/delegated scopes are unavailable, say the shared-mailbox action or scope is the blocker"). Not a 2 because the confirmation checkpoint and feedback loop satisfy the validation requirement for these high-impact sends.

3 / 3

Progressive Disclosure

Under 50 lines with no external references needed (no references/scripts/assets bundle exists) and clean sections (Required Target, Action Routing, Workflow, Safety, Example Requests), matching the under-50-lines allowance for scoring 3 on organization alone.

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.

A strong, well-scoped description that names concrete actions, supplies an explicit 'Use when' trigger, and carves out a distinct niche from the base Outlook Email skill. No vague fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "read another mailbox, send from or on behalf of a shared mailbox, mark shared mail read or unread, move shared mail, or browse folders" — matching the 'lists multiple specific concrete actions' anchor; not a 2 because coverage is comprehensive rather than partial.

3 / 3

Completeness

States what ("Work with delegated or shared Outlook Email mailboxes") and when via an explicit "Use when the user explicitly wants to..." clause; not a 2 because the trigger guidance is explicit, not merely implied.

3 / 3

Trigger Term Quality

Natural phrases a user would say — "read another mailbox", "send from... a shared mailbox", "mark shared mail read or unread", "move shared mail", "browse folders" — give good coverage; not a 2 because common variations are present rather than missing.

3 / 3

Distinctiveness Conflict Risk

A clear niche (delegated/shared mailboxes) with distinct triggers that separate it from the signed-in-user Outlook skill; not a 2 because the shared/delegated framing makes overlap 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.