outlook-email-subscription-cleanup

$npx mdskill add openai/plugins/outlook-email-subscription-cleanup

Safely cleans up Outlook newsletters and subscriptions by unsubscribing, categorizing, or moving emails to organize low-signal traffic.

  • Helps users unsubscribe from unwanted emails and separate newsletters from important human mail.
  • Integrates with Outlook APIs for message search, folder management, and category handling.
  • Decides actions by inspecting unsubscribe metadata and distinguishing subscriptions from transactional messages.
  • Presents results through organized folders or categories in the user's Outlook interface.

SKILL.md

.github/skills/outlook-email-subscription-cleanupView on GitHub ↗
---
name: outlook-email-subscription-cleanup
description: 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.
---

# Outlook Email Subscription Cleanup

## Overview

Use this skill for newsletter and subscription cleanup. Outlook organization is folder- and category-oriented, so prefer unsubscribe inspection first, then category or folder organization when the user wants the remaining mail tamed.

## Relevant Actions

- Use `search_messages` or `list_messages` to build the sender or newsletter shortlist.
- Use `get_unsubscribe_info` before attempting an unsubscribe action.
- Use `unsubscribe_via_mailto` only when the connector exposes a `mailto:` unsubscribe target.
- Use `list_categories`, `create_category`, and `set_message_categories` when the user wants newsletter tagging instead of moving mail.
- Use `find_mail_folder`, `create_mail_folder`, and `move_email` when the user wants recurring subscription traffic separated into folders.

## Workflow

1. Build a shortlist of recurring low-signal senders or newsletter-like messages.
2. Separate true subscriptions from transactional mail, alerts, or automated messages that may still matter operationally.
3. Inspect unsubscribe metadata before claiming a safe unsubscribe path exists.
4. If unsubscribe is not supported through the connector, fall back to category or folder organization instead of pretending the cleanup is complete.
5. Keep irreversible or high-volume mailbox changes explicit in the response. Say what you plan to unsubscribe, move, or tag before doing it.
6. Prefer a small, explainable cleanup pass over a broad noisy sweep.

## Output

- Group results by `Unsubscribe`, `Keep but Organize`, and `Needs Human Review`.
- For unsubscribe candidates, say whether the path is a supported `mailto:` action or only an informational header.
- For organization actions, say which category or folder each sender should map to.
- If the cleanup scope is heuristic, state the query or mailbox slice you used.

More from openai/plugins

SkillDescription
accessibility-and-inclusive-visualizationMake data visualizations accessible and inclusive. Use when the user needs chart or diagram accessibility guidance, text alternatives for complex visuals, color and contrast review, keyboard support, reduced-motion behavior for animation or parallax, or an accessibility QA workflow for exported figures, UML-like diagrams, and dashboards.
agent-browserBrowser automation CLI for AI agents. Use when the user needs to interact with websites, verify dev server output, test web apps, navigate pages, fill forms, click buttons, take screenshots, extract data, or automate any browser task. Also triggers when a dev server starts so you can verify it visually.
agent-browser-verifyAutomated browser verification for dev servers. Triggers when a dev server starts to run a visual gut-check with agent-browser — verifies the page loads, checks for console errors, validates key UI elements, and reports pass/fail before continuing.
agents-sdkBuild AI agents on Cloudflare Workers using the Agents SDK. Load when creating stateful agents, durable workflows, real-time WebSocket apps, scheduled tasks, MCP servers, or chat applications. Covers Agent class, state management, callable RPC, Workflows integration, and React hooks. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
ai-elementsAI Elements component library guidance — pre-built React components for AI interfaces built on shadcn/ui. Use when building chat UIs, message displays, tool call rendering, streaming responses, reasoning panels, or any AI-native interface with the AI SDK.
ai-gatewayVercel AI Gateway expert guidance. Use when configuring model routing, provider failover, cost tracking, or managing multiple AI providers through a unified API.
ai-generation-persistenceAI generation persistence patterns — unique IDs, addressable URLs, database storage, and cost tracking for every LLM generation
ai-sdkVercel AI SDK expert guidance. Use when building AI-powered features — chat interfaces, text generation, structured output, tool calling, agents, MCP integration, streaming, embeddings, reranking, image generation, or working with any LLM provider.
aiq-deploy|
aiq-research|