Agent skill · marketing growth · aiskillstore
emaildeliverabilityskill
Use when Codex, Hermes, OpenClaw, Claude Code, Cowork, or another AI agent needs to plan, review, implement, audit, or improve email work focused on inbox placement, authentication, sender reputation, complaint control, and remediation workflows. Triggers include requests about DNS authentication audits, warmup plans, complaint spike triage, blocklist checks, bounce analysis, and reputation recovery.
Why this skill is useful
Provides domain-specific knowledge on email deliverability issues, including authentication checks and remediation workflows that the AI wouldn't reliably generate on its own.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Email Deliverability Skill Protect the sender before chasing growth. Separate authentication, reputation, content, list quality, and provider issues before recommending action. Scope inbox placement, authentication, sender reputation, complaint control, and remediation workflows. Request Signals DNS authentication audits, warmup plans, complaint spike triage, blocklist checks, bounce analysis, and reputation recovery. Guardrails 1. Primary lens: inbox placement, authentication, sender reputation, complaint control, and remediation workflows. 2. Common request signals: DNS authentication audits, warmup plans, complaint spike triage, blocklist checks, bounce analysis, and reputation recovery. 3. Default posture: Protect the sender before chasing growth. Separate authentication, reputation, content, list quality, and provider issues before recommending action. 4. Useful output family: DNS/authentication audits, reputation triage notes, warmup schedules, suppression reviews, monitoring plans, and remediation runbooks. 5. Production boundary: separate recommendation from execution. 6. Evidence boundary: say which source material supports the recommendation. 7. Review boundary: identify the human owner for risky changes. 8. Data boundary: do not assume missing fields, consent, or suppression state. Execution Path 1. Classify the deliverability problem: authentication failure, bounce spike, complaint spike, spam-folder placement, throttling, blocklist, or engagement decay. 2. Collect evidence by domain, provider, segment, campaign, and time window rather than treating all mail as one stream. 3. Check SPF, DKIM, DMARC, custom tracking domain, bounce domain, alignment, and recent DNS changes. 4. Review list acquisition, consent, suppression, frequency, reactivation, and recent imports for reputation risk. 5. Recommend a staged remediation plan with stop-loss thresholds, monitoring cadence, and owner for each action. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/emaildeliverabilityskill