From outlook-email
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/outlook-email:outlook-email-subscription-cleanupThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
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.
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.
search_messages or list_messages to build the sender or newsletter shortlist.get_unsubscribe_info before attempting an unsubscribe action.unsubscribe_via_mailto only when the connector exposes a mailto: unsubscribe target.list_categories, create_category, and set_message_categories when the user wants newsletter tagging instead of moving mail.find_mail_folder, create_mail_folder, and move_email when the user wants recurring subscription traffic separated into folders.Unsubscribe, Keep but Organize, and Needs Human Review.mailto: action or only an informational header.npx claudepluginhub robinebers/converted-plugins --plugin outlook-emailGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.