list-hygiene-monitor
Use when the user asks to "watch my list health over time", "flag decaying / unengaged subscribers on a schedule", "why is my open rate drifting down / bounces creeping up", or "build me a re-permission and prune worklist"; runs the scheduled SEND list-decay + suppression-drift watch — an engagement-recency cohort read (30/90/180/365-day), hard-bounce and spam-complaint trend vs benchmark, suppression-list growth/leakage check, and a segmented re-permission / sunset / prune worklist tied to SEND S (list hygiene) and E (engagement-decay) sub-items. Not for the one-time pre-send authentication p
npx skills add aaron-he-zhu/aaron-marketing-skills --skill list-hygiene-monitor --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.
# List Hygiene Monitor The ongoing hygiene watch, not the pre-flight — a scheduled read of list decay and suppression drift that turns the ESP export into a segmented **re-permission / sunset / prune worklist**. It cohorts the list by engagement recency (30/90/180/365-day last-open/click), trends hard-bounce and spam-complaint rates against benchmark and the prior baseline, and checks suppression-list growth and leakage — feeding the SEND **S (Sender-integrity / Deliverability, list-hygiene sub-item)** and **E (Engagement, engagement-decay / sunset sub-item)** signals. **Scope guard: this skill produces the recurring hygiene worklist and the S-hygiene / E-decay reads only; it does NOT run the one-time authentication pre-flight ([deliverability-qa](../deliverability-qa/SKILL.md)), own the consent / suppression record ([consent-registry](../../../protocol/consent-registry/SKILL.md)), or compute the profile-weighted EQS / enforce the `S1`/`S2`/`N1`/`D1` vetoes ([email-quality-auditor](../../deliver/email-quality-auditor/SKILL.md)).** deliverability-qa answers "will this one send land?"; this skill answers "is the list rotting between sends, and who do I re-permission or prune?" — buil
- Quick Start
- Skill Contract
- Handoff Summary
- Data Sources
- Instructions
- Save Results
- Reference Materials
- Next Best Skill
What does the list-hygiene-monitor skill do?
Use when the user asks to "watch my list health over time", "flag decaying / unengaged subscribers on a schedule", "why is my open rate drifting down / bounces creeping up", or "build me a re-permission and prune worklist"; runs the scheduled SEND list-decay + suppression-drift watch — an engagement-recency cohort read (30/90/180/365-day), hard-bounce and spam-complaint trend vs benchmark, suppression-list growth/leakage check, and a segmented re-permission / sunset / prune worklist tied to SEND S (list hygiene) and E (engagement-decay) sub-items. Not for the one-time pre-send authentication p
How do I install it?
Run `npx skills add aaron-he-zhu/aaron-marketing-skills --skill list-hygiene-monitor --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 aaron-he-zhu/aaron-marketing-skills, a repository with 2,508 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.