Inbox Unsubscribe Purge Skill

Triage manages the flow; the purge shrinks it. Most inbox volume is recurring senders — newsletters, notifications, marketing — and each one is a decision made once that pays forever. The purge runs a census of who actually sends the volume, sorts senders into kill/digest/keep, and executes with the safety rules most people don't know: legitimate senders' unsubscribe links are safe and legally binding-ish; spam senders' unsubscribe links are confirmation beacons — those get reported, never clicked.

What This Skill Produces

• The sender census — the top recurring senders by volume, from the actual inbox
• The sort — kill (unsubscribe) / digest (batch to a daily-read label) / keep (whitelist to inbox)
• The safety rules — which unsubscribe links to click, which to never touch, what gets spam-reported
• The filter set — the rules that auto-route what survives, and the notification-settings homework that beats filtering

Required Inputs

Ask for these if not provided:

• The census data — search counts per suspected sender, or a description of the noise ("LinkedIn, three newsletters, shop marketing, GitHub notifications")
• Honest reading behavior — which newsletters actually get read (the calendar answer; "I mean to" is a kill vote)
• The platform — Gmail/Outlook/other; filter syntax differs, and the skill writes the real rules

Framework: The Purge Rules