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.
Best use case
outlook-email-subscription-cleanup is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using outlook-email-subscription-cleanup should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/outlook-email-subscription-cleanup/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How outlook-email-subscription-cleanup Compares
| Feature / Agent | outlook-email-subscription-cleanup | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# 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.
Related Skills
Email sending integration guidance — Resend (native Vercel Marketplace) with React Email templates. Covers API setup, transactional emails, domain verification, and template patterns. Use when sending emails from a Vercel-deployed application.
outlook-email
Triage Outlook mail, extract tasks, clean up subscriptions, and draft responses. Use when the user asks to inspect an Outlook inbox or thread, summarize open actions and deadlines, clean up newsletters, draft replies or forwards, or organize mailbox follow-up work before any send or cleanup action.
outlook-email-task-extraction
Extract action items, deadlines, commitments, and owners from Outlook email threads and mailbox searches. Use when the user wants a task list from one thread, several related messages, or a mailbox slice, including who owes what and when.
outlook-email-reply-drafting
Draft Outlook email replies safely from connected mailbox context. Use when the user wants to reply to a thread, decide whether to reply-all, prepare a draft before sending, or turn the latest Outlook message into a polished response.
outlook-email-inbox-triage
Triage an Outlook inbox into actionable buckets such as urgent, needs reply soon, waiting, and FYI using connected Outlook data. Use when the user asks to triage the inbox, rank what needs attention, find what still needs a reply, or separate important mail from noise.
outlook-calendar
Handle Outlook Calendar workflows. 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, or cancel changes with timezone-aware event times and attendee validation.
outlook-calendar-meeting-prep
Build a practical meeting prep brief from an Outlook Calendar event and its nearby Microsoft context. Use when the user wants to prepare for an upcoming meeting, understand what to read beforehand, pull in linked notes or docs, or get a concise brief on what the meeting appears to require.
outlook-calendar-group-scheduler
Find and rank good meeting times for several people using Outlook Calendar data. Use when the user wants to schedule a meeting, compare candidate slots across attendees, find the best compromise time, or add a room/resource check after narrowing the attendee-compatible options.
outlook-calendar-free-up-time
Find ways to open up meaningful free time in Outlook Calendar. Use when the user wants to clear part of their schedule, make room for focus time, create a longer uninterrupted block, or see the smallest set of calendar changes that would give time back.
outlook-calendar-daily-brief
Build polished one-day Outlook Calendar briefs. Use when the user asks for today, tomorrow, or a specific date summary with an agenda, conflict flags, free windows, remaining-meeting readouts, or a calendar brief, and Outlook Calendar is available.
workflow
Vercel Workflow DevKit (WDK) expert guidance. Use when building durable workflows, long-running tasks, API routes or agents that need pause/resume, retries, step-based execution, or crash-safe orchestration with Vercel Workflow.
verification
Full-story verification — infers what the user is building, then verifies the complete flow end-to-end: browser → API → data → response. Triggers on dev server start and 'why isn't this working' signals.