CtrlK
BlogDocsLog inGet started
Tessl Logo

outlook-email-subscription-cleanup

Clean up Outlook newsletters and recurring subscription email safely. Use when the user wants to unsubscribe, separate newsletters from human mail, move recurring senders into folders, or organize low-signal subscription traffic without losing important messages.

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.

A tight, well-structured instruction skill that names specific Outlook connector tools, sequences the cleanup workflow with explicit pre-action verification and fallback steps, and organizes content cleanly within a single file. It avoids concept re-explanation and verbosity while remaining highly actionable.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it does not explain what Outlook, newsletters, or folders are; every line is actionable guidance, matching the level-3 'lean and efficient' anchor rather than padded level-2 or verbose level-1.

3 / 3

Actionability

Names exact connector tools with gating conditions — 'get_unsubscribe_info', 'unsubscribe_via_mailto only when the connector exposes a mailto: target', 'set_message_categories', 'move_email' — giving concrete actionable guidance; per the instruction-only scoring note, the absence of code is not penalized since guidance is specific and actionable.

3 / 3

Workflow Clarity

A clear 6-step sequence with explicit verification gates for destructive/batch operations — step 3 'Inspect unsubscribe metadata before claiming a safe unsubscribe path exists' and step 5 'Say what you plan to unsubscribe, move, or tag before doing it' — plus an explicit fallback (step 4), so the missing-validation cap at level-2 does not apply.

3 / 3

Progressive Disclosure

At 33 lines with no bundle files and well-organized sections (Overview, Relevant Actions, Workflow, Output), it meets the simple-skill note that progressive disclosure can score 3 with just well-organized sections and no external references.

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, concise description that names concrete actions, provides natural user-facing trigger terms, and explicitly states both what it does and when to use it within a distinctive Outlook-subscription niche. No vague fluff or over-claims are present.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'unsubscribe', 'separate newsletters from human mail', 'move recurring senders into folders', 'organize low-signal subscription traffic' — matching the level-3 anchor that lists several specific concrete actions; it is not the level-2 'some actions' case nor vague level-1.

3 / 3

Completeness

Explicitly answers both what ('Clean up Outlook newsletters and recurring subscription email safely') and when via an explicit 'Use when the user wants to...' trigger clause, matching the level-3 anchor; the 'Use when' presence avoids the level-2 cap.

3 / 3

Trigger Term Quality

Includes natural terms users would actually say — 'unsubscribe', 'newsletters', 'recurring subscription email', 'move recurring senders into folders' — giving good coverage rather than jargon (level-1) or partial keywords (level-2).

3 / 3

Distinctiveness Conflict Risk

Targets a clear Outlook newsletter/subscription-cleanup niche with distinct triggers, making overlap with other skills unlikely; not the generic level-1 or broadly-overlapping level-2 cases.

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.