email-deliverability
Make sure email actually reaches inboxes. Use this skill when setting up email authentication (SPF, DKIM, DMARC), diagnosing emails landing in spam, planning a domain reputation strategy, monitoring sender reputation, or hardening against email spoofing. Triggers on email deliverability, SPF, DKIM, DMARC, spam folder, sender reputation, mailbox provider, soft bounces, bounce rate, BIMI, MTA-STS, deliverability audit. Also triggers when a marketing or transactional email isn't reaching users.
Profile →npx skills add rampstackco/claude-skills --skill email-deliverability --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.
# Email Deliverability Get email into inboxes, not spam folders. Set up authentication. Monitor reputation. Diagnose problems before they hurt the business. --- ## When to use - Setting up email for a new domain - A meaningful percentage of email is going to spam - Customers report they're not receiving emails - Setting up DMARC, SPF, or DKIM - Hardening against domain spoofing - Migrating email service providers - Sender reputation has dropped - Pre-launch audit before sending volume increases ## When NOT to use - Writing the email content itself (use `email-sequences`) - Designing the email program strategy (use `email-sequences`) - DNS records in general (use `domain-strategy`) - Outbound spam coming FROM your account (different problem; investigate compromised credentials) --- ## Required inputs - The sending domain(s) - The email service provider (ESP, transactional service, mail server) - Current DNS records (or access to them) - Email volume (transactional vs marketing, daily volume) - Current deliverability state (if known: bounce rate, spam complaints) --- ## The framework: 3 pillars Email deliverability rests on three pillars. Weakness in any one limits the others. ### Pi
- When to use
- When NOT to use
- Required inputs
- The framework: 3 pillars
- Pillar 1: Authentication
- Pillar 2: Reputation
- Pillar 3: List quality and engagement
- Workflow
- Step 1: Audit current state
- Step 2: Fix authentication
- Step 3: Set up monitoring
- Step 4: Address list hygiene
- Step 5: Content and pattern audit
- Step 6: Plan for growth
dig +short txt example.com dig +short txt selector1._domainkey.example.com dig +short txt _dmarc.example.com
What does the email-deliverability skill do?
Make sure email actually reaches inboxes. Use this skill when setting up email authentication (SPF, DKIM, DMARC), diagnosing emails landing in spam, planning a domain reputation strategy, monitoring sender reputation, or hardening against email spoofing. Triggers on email deliverability, SPF, DKIM, DMARC, spam folder, sender reputation, mailbox provider, soft bounces, bounce rate, BIMI, MTA-STS, deliverability audit. Also triggers when a marketing or transactional email isn't reaching users.
How do I install it?
Run `npx skills add rampstackco/claude-skills --skill email-deliverability --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 rampstackco/claude-skills, a repository with 515 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.