Agent skill

Inbox Unsubscribe Purge

by mohitagw15856 in mohitagw15856/pm-claude-skills

Cut inbox volume at the source — the unsubscribe purge that classifies recurring senders into kill/digest/keep, executes safely (real unsubscribes vs.

MITAuto-check passedProductivity & Automation

Install Inbox Unsubscribe Purge

skills CLI
$ npx skills add mohitagw15856/pm-claude-skills --skill inbox-unsubscribe-purge -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mohitagw15856/pm-claude-skills inbox-unsubscribe-purge --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/inbox-unsubscribe-purge .claude/skills/inbox-unsubscribe-purge && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
inbox-unsubscribe-purge
GitHub stars
1.4k
Token cost
~1.1k tokens
SKILL.md length
586 words
Files
1
Skills in repo
1,348
Repo updated
First seen
Licence
MIT

At a glance

Cut inbox volume at the source — the unsubscribe purge that classifies recurring senders into kill/digest/keep, executes safely (real unsubscribes vs.

  • Works in 5 steps: Census before action: search per sender… → The kill test: would you notice if it… → The safety line: known-legitimate… → …
  • Asked my inbox is all newsletters
  • SKILL.md covers What This Skill Produces, Required Inputs, Framework: The Purge Rules and Output Format, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Inbox Unsubscribe Purge is an agent skill from mohitagw15856/pm-claude-skills. 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.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Productivity & Automation, covering Email management and Newsletters. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.

When your agent uses it

  • Asked my inbox is all newsletters
  • Mass unsubscribe safely
  • Cut my email volume
  • Set up filters for the noise

Example prompts

  • “/inbox-unsubscribe-purge”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Census before action: search per sender (from:newsletter@x.com), count the last 90 days — volume × read-rate sorts everything. The top ten…
  2. The kill test: would you notice if it stopped? Not "is it good" — would you notice. Unread-for-a-month newsletters, notification emails…
  3. The safety line: known-legitimate senders (real newsletters, real companies) → unsubscribe link is safe and usually works. Unknown/sketchy…
  4. Digest beats trickle for the keepers: surviving newsletters get a filter to skip the inbox into a @read-later label, read in one weekly…
  5. The maintenance rule: every new recurring sender gets the kill test on first arrival — one decision at first touch beats a re-purge every…

What it can do on your machine

Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Inbox Unsubscribe Purge loads about 1.1k tokens when it runs. Until then it costs about 119 tokens; SKILL.md has 586 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~119
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 586 words, ~1,150 tokens.

Download SKILL.mdSave it as .claude/skills/inbox-unsubscribe-purge/SKILL.md (or your agent's skills folder).
name
inbox-unsubscribe-purge
description
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.

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

  1. Census before action: search per sender (from:newsletter@x.com), count the last 90 days — volume × read-rate sorts everything. The top ten senders are usually half the noise; purge by impact order, not inbox order.
  2. The kill test: would you notice if it stopped? Not "is it good" — would you notice. Unread-for-a-month newsletters, notification emails duplicating app pings, and every marketing list fail the test. Kill without ceremony.
  3. The safety line: known-legitimate senders (real newsletters, real companies) → unsubscribe link is safe and usually works. Unknown/sketchy senders → the link confirms your address is live; report as spam instead, never click. The test: did you knowingly sign up? No → spam-report path.
  4. Digest beats trickle for the keepers: surviving newsletters get a filter to skip the inbox into a @read-later label, read in one weekly sitting. Notifications that must exist (CI, mentions) get their source settings tightened first — filtering email that shouldn't be sent is fixing the wrong end.
  5. The maintenance rule: every new recurring sender gets the kill test on first arrival — one decision at first touch beats a re-purge every quarter. The purge is an event; the test is a habit.
Show full SKILL.md (190 more words)Show less

Output Format

Unsubscribe Purge: [inbox]

The Census

SenderVolume /90dActually read?Verdict

Execution

Kill (safe unsubscribe): [list] · Spam-report (never click): [list, with why] · Digest: [list → the filter rule, in platform syntax] · Source-settings homework: [the app notifications to turn off at origin]

The Filters

[The actual rules, platform syntax, paste-ready]

Quality Checks

  • The census is by measured volume, not by annoyance salience
  • Every kill passed the would-you-notice test
  • The click/never-click line is applied per sender, with the sketchy ones named
  • Digest filters skip the inbox, not just label it
  • Notification volume is fixed at the source where a source setting exists

Anti-Patterns

  • Do not click unsubscribe on spam — it's a liveness beacon; report instead
  • Do not keep newsletters aspirationally — the read-rate is the vote, not the intention
  • Do not build filters for email that shouldn't exist — source settings first
  • Do not purge alphabetically — impact order; the top ten senders are half the volume
  • Do not skip the first-touch habit — without it, the purge is an annual chore instead of a one-time fix

Example Trigger Phrases

  • "My inbox is all newsletters."
  • "Cut my email volume."
  • "Set up filters for the noise."

© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/inbox-unsubscribe-purge of mohitagw15856/pm-claude-skills.

Open the folder on GitHubat commit 1cbf1f0

Compare with similar skills

Inbox Unsubscribe Purge next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Inbox Unsubscribe Purge compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Inbox Unsubscribe Purge this skillmohitagw15856/pm-claude-skills1.4k—~1.1kAutomated safety check: PassMIT
Triage Superhuman Inboxsuperset-sh/superset15k—~1.2kAutomated safety check: PassCustom licence
Gmail Triggervellum-ai/vellum-assistant1.4k—~1.7kAutomated safety check: PassMIT
Spark Recipe Inbox By Categoryreaddle/spark-cli-skills149—~531Automated safety check: PassMIT
Inbox CleanupHybridAIOne/hybridclaw159—~702Automated safety check: PassMIT
Loop Covercharlie947/motion-graphics-skills180—~939Automated safety check: PassMIT

Similar skills

  • Triage Superhuman Inbox

    superset-sh/superset

    Work through a Superhuman inbox — sort what is there into needs a reply, waiting on someone else, worth knowing, and noise, then archive, star, label, remind, or unsubscribe only as the user directs.

    15k GitHub stars~1.2k tokensUpdated today
    Productivity & AutomationAuto-check passed
  • Gmail Trigger

    vellum-ai/vellum-assistant

    Beta. An agent skill from vellum-ai/vellum-assistant.

    1.4k GitHub stars~1.7k tokensUpdated 2 days ago
    Productivity & AutomationAuto-check passed
  • Spark Recipe Inbox By Category

    readdle/spark-cli-skills

    Process inbox in priority order by Spark's smart categories: priority first, then people, invites, notifications, newsletters.

    149 GitHub stars~531 tokensUpdated 4 days ago
    Productivity & AutomationAuto-check passed
  • Inbox Cleanup

    HybridAIOne/hybridclaw

    Tidy a crowded inbox by archiving newsletters, promotions and notifications in bulk, with a card the user approves and undo for 30 days.

    159 GitHub stars~702 tokensUpdated yesterday
    Productivity & AutomationAuto-check passed
  • Loop Cover

    charlie947/motion-graphics-skills

    Turn a newsletter or blog cover into a seamless looping GIF at 896 x 640, 180 frames at 20fps.

    180 GitHub stars~939 tokensUpdated today
    Media & CreativeAuto-check passed
  • Gog Weekly Digest

    openclaw/gogcli

    Read-only weekly digest across Google Calendar, Gmail, and Tasks with gog.

    8.5k GitHub stars~264 tokensUpdated yesterday
    Writing & ContentAuto-check passed

More from mohitagw15856/pm-claude-skills

All 1,348 skills in this repo
  • Car Tco

    mohitagw15856/pm-claude-skills

    Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Cs Health Scorecard

    mohitagw15856/pm-claude-skills

    Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~2.4k tokensUpdated 2 days ago
    Auto-check passed
  • Exit Waterfall

    mohitagw15856/pm-claude-skills

    Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Feature Prioritisation

    mohitagw15856/pm-claude-skills

    Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.

    1.4k GitHub stars~2k tokensUpdated 2 days ago
    Auto-check passed
  • Fire Number

    mohitagw15856/pm-claude-skills

    Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.

    1.4k GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed
  • Freelance Rate

    mohitagw15856/pm-claude-skills

    Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.

    1.4k GitHub stars~1.2k tokensUpdated 2 days ago
    Auto-check passed

Questions about Inbox Unsubscribe Purge

What does Inbox Unsubscribe Purge do?

Cut inbox volume at the source — the unsubscribe purge that classifies recurring senders into kill/digest/keep, executes safely (real unsubscribes vs. Inbox Unsubscribe Purge is an agent skill from mohitagw15856/pm-claude-skills. Cut inbox volume at the source — the unsubscribe purge that classifies recurring senders into kill/digest/keep, executes safely (real unsubscribes vs.

When should I use Inbox Unsubscribe Purge?

Inbox Unsubscribe Purge fits situations like: asked my inbox is all newsletters; mass unsubscribe safely; cut my email volume; set up filters for the noise.

How do I install Inbox Unsubscribe Purge in Claude Code?

Run `npx skills add mohitagw15856/pm-claude-skills --skill inbox-unsubscribe-purge -a claude-code`. Or copy the skill folder (skills/inbox-unsubscribe-purge in mohitagw15856/pm-claude-skills) into .claude/skills/inbox-unsubscribe-purge in your project. Claude Code loads it when a task matches its description.

How do I install Inbox Unsubscribe Purge in Codex?

Run `npx skills add mohitagw15856/pm-claude-skills --skill inbox-unsubscribe-purge -a codex`. Or copy the skill folder (skills/inbox-unsubscribe-purge in mohitagw15856/pm-claude-skills) into .agents/skills/inbox-unsubscribe-purge in your project. Codex loads it when a task matches its description.

Can I use Inbox Unsubscribe Purge in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill inbox-unsubscribe-purge -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/inbox-unsubscribe-purge, .gemini/skills/inbox-unsubscribe-purge, .github/skills/inbox-unsubscribe-purge and .opencode/skills/inbox-unsubscribe-purge in your project.

What does Inbox Unsubscribe Purge need to run?

SKILL.md names no scripts, command-line tools or credentials: Inbox Unsubscribe Purge is instructions for the agent only.

Does Inbox Unsubscribe Purge access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Inbox Unsubscribe Purge safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Inbox Unsubscribe Purge use?

Inbox Unsubscribe Purge is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Inbox Unsubscribe Purge use?

About 1.1k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Inbox Unsubscribe Purge?

Skills that share tags, products or a category with Inbox Unsubscribe Purge: Triage Superhuman Inbox (superset-sh/superset, 15k stars), Gmail Trigger (vellum-ai/vellum-assistant, 1.4k stars), Spark Recipe Inbox By Category (readdle/spark-cli-skills, 149 stars) and Inbox Cleanup (HybridAIOne/hybridclaw, 159 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Inbox Unsubscribe Purge?

mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.

Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.