inbox-unsubscribe-purge
Cut inbox volume at the source — the unsubscribe purge that classifies recurring senders into kill/digest/keep, executes safely (real unsubscribes vs. spam-report vs. never-click), and installs the filters that catch the rest. Use when asked my inbox is all newsletters, mass unsubscribe safely, cut my email volume, or set up filters for the noise. Produces the sender census, the kill/digest/keep sort, the safe-unsubscribe rules, and the filter set.
npx skills add mohitagw15856/pm-claude-skills --skill inbox-unsubscribe-purge --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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") - **Hon
- What This Skill Produces
- Required Inputs
- Framework: The Purge Rules
- Output Format
- The Census
- Execution
- The Filters
- Quality Checks
- Anti-Patterns
What does the inbox-unsubscribe-purge skill do?
Cut inbox volume at the source — the unsubscribe purge that classifies recurring senders into kill/digest/keep, executes safely (real unsubscribes vs. spam-report vs. never-click), and installs the filters that catch the rest. Use when asked my inbox is all newsletters, mass unsubscribe safely, cut my email volume, or set up filters for the noise. Produces the sender census, the kill/digest/keep sort, the safe-unsubscribe rules, and the filter set.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill inbox-unsubscribe-purge --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.