How do I install the Org Email Subscriptions skill?

Run npx skillmds@latest add pooriaarab/org-email-subscriptions in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Org Email Subscriptions safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Org Email Subscriptions?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Org Email Subscriptions free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Org Email Subscriptions?

pooriaarab (@pooriaarab) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Org Email Subscriptions by pooriaarab

Name: Org Email Subscriptions
Author: pooriaarab

Org Email Subscriptions

Use when the user wants an unsubscribe pass on email — identifying senders the user no longer reads, mass-unsubscribing via List-Unsubscribe headers, archiving historical mail from those senders. Companion to org-gmail. Triggers: 'unsubscribe from newsletters', 'stop email spam'.

pooriaarab 2b23303 2.2 KB Updated Sep 17, 2026

File contents

Email Subscriptions Organizer

Mass-unsubscribe pass on Gmail (or any IMAP-accessible mailbox).

Requirements

Gmail account access (gws CLI or Gmail API), or any IMAP mailbox.
Sender frequency analyzer (read-only).

Step 1 — Ask the User First

1. Account scope — personal / work / both?
2. Threshold — show senders with > N emails in last 12 months who you've opened < M times?
3. Approval style — per-sender (most control), bucket-of-similar (fast), or "unsubscribe everything-shopping/everything-news"?
4. Post-unsubscribe — also archive their historical emails?
5. Whitelist — list senders to never unsubscribe from (banking, family, security alerts)?

Steps (TBD)

Inventory — count messages per sender domain, last-opened heuristic from Gmail metadata.
Classify — actionable / newsletter / shopping / notification / other.
Plan — proposed unsubscribe list.
Approve — batch by category.
Apply — fire List-Unsubscribe headers, log per-sender result.
Verify — re-scan inbox after 1 week to confirm sender frequency dropped.

Surface-specific notes

List-Unsubscribe is the gold standard — RFC 8058 one-click unsubscribe. Most modern senders comply.
Some senders' unsubscribe links require a logged-in browser session (terrible UX) — flag those for manual.
Don't auto-unsubscribe from any banking, government, or security-alert sender. Default whitelist.
Unsubscribe = sender stops sending. Already-received mail sticks around — separate archive pass.

---name: org-email-subscriptionsdescription: Use when the user wants an unsubscribe pass on email — identifying senders the user no longer reads, mass-unsubscribing via List-Unsubscribe headers, archiving historical mail from those senders. Companion to org-gmail. Triggers: 'unsubscribe from newsletters', 'stop email spam'.---# Email Subscriptions OrganizerMass-unsubscribe pass on Gmail (or any IMAP-accessible mailbox).## Requirements- Gmail account access (`gws` CLI or Gmail API), or any IMAP mailbox.- Sender frequency analyzer (read-only).## Step 1 — Ask the User First```1. Account scope — personal / work / both?2. Threshold — show senders with > N emails in last 12 months who you've opened < M times?3. Approval style — per-sender (most control), bucket-of-similar (fast), or "unsubscribe everything-shopping/everything-news"?4. Post-unsubscribe — also archive their historical emails?5. Whitelist — list senders to never unsubscribe from (banking, family, security alerts)?```## Steps (TBD)1. **Inventory** — count messages per sender domain, last-opened heuristic from Gmail metadata.2. **Classify** — actionable / newsletter / shopping / notification / other.3. **Plan** — proposed unsubscribe list.4. **Approve** — batch by category.5. **Apply** — fire `List-Unsubscribe` headers, log per-sender result.6. **Verify** — re-scan inbox after 1 week to confirm sender frequency dropped.## Surface-specific notes- **`List-Unsubscribe` is the gold standard** — RFC 8058 one-click unsubscribe. Most modern senders comply.- Some senders' unsubscribe links require a logged-in browser session (terrible UX) — flag those for manual.- Don't auto-unsubscribe from any banking, government, or security-alert sender. Default whitelist.- Unsubscribe = sender stops sending. Already-received mail sticks around — separate archive pass.## See also- [`../org-life-organizer/_lib/taxonomy.md`](../org-life-organizer/_lib/taxonomy.md)- [`../org-life-organizer/_lib/patterns.md`](../org-life-organizer/_lib/patterns.md)- [`../org-gmail/SKILL.md`](../org-gmail/SKILL.md) — runs the broader Gmail pass; this is the focused unsubscribe slice

Frequently asked questions