SkillsAdd

kensaurus/cursor-kenji

enhance-email-deliverability

Audit and fix transactional/marketing deliverability — SPF, DKIM, DMARC, reputation, bounce/complaint handling, list hygiene, unsubscribe compliance — so mail lands in the inbox. Use when "emails go to spam", "set up SPF/DKIM", or "check deliverability". Templates stay on design-email.

First seen Aug 18, 2026

Installation

$ npx skills add kensaurus/cursor-kenji --skill enhance-email-deliverability
View on skills.sh ↗ GitHub repository ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

deliverability-qa Similar name
aaron-he-zhu/aaron-marketing-skills

Use when the user asks to "run a deliverability pre-flight before I send", "check my SPF/DKIM/D…

10 installs
message-deliverability-optimization Similar name
louisblythe/sales-skills

When the user wants to build or improve a sales bot's ability to manage sender reputation and e…

320 installs
deliverability-checker Similar name
guia-matthieu/clawfu-skills

Check email deliverability and DNS configuration. Use when: diagnosing email delivery issues; s…

228 installs
email-deliverability Similar name
rampstackco/claude-skills

Make sure email actually reaches inboxes.

213 installs
twilio-sendgrid-deliverability-advisor Similar name
twilio/ai

Diagnostic and advisory skill for email deliverability problems. Use when a developer asks why …

139 installs
email-deliverability Similar name
maddhruv/absolute

Use this skill when optimizing email deliverability, sender reputation, or authentication. Trig…

136 installs

Also in this package

Other skills from kensaurus/cursor-kenji · top by installs.

npx skills add kensaurus/cursor-kenji
audit-performance 37 audit-code-quality 37 debug-fe-be-integration 36 debug-error 36 audit-code-review 36 audit-accessibility 36 enhance-web-redesign 35 enhance-web-ui 35 audit-security 34 backend-patterns 34

Browse all from kensaurus/cursor-kenji

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 9
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

LicenseMIT

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 5,484 B
  • docs SUMMARY.md 326 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

enhance-email-deliverability — Inbox placement & lawful send

Degree of freedom: MIXED — T1 is the priority. Scoring auth/hygiene [HIGH freedom]; DNS/config apply [LOW freedom — after approval]. Audit-and-fix. Templates stay on design-email.

Close the gap between "the email sends" and "the email arrives". A beautiful transactional template in spam is a broken signup flow.

Deliverability = authentication + reputation + hygiene + compliance. Miss any one and placement collapses.

Audit first. Apply DNS/config on approval. Template markup stays on design-email.

This skill vs neighbors

Skill Owns
enhance-email-deliverability (this) SPF/DKIM/DMARC, bounces, complaints, unsubscribe headers
design-email Template markup, copy, React Email / MJML
plan-privacy-compliance Consent to collect; this owns consent to send
audit-analytics Whether open/click events fire (not inbox placement)

Keep enhance-* here (audit-and-fix, same family as enhance-web-seo). Do not steal "build a welcome email" from design-email.

How to reason

  1. Observe — SPF/DKIM/DMARC records and a real message's Authentication-Results
  2. Interpret — pass raw SPF/DKIM but fail alignment? +all? DNS-only DKIM?
  3. Classify — auth fail / hygiene hole / compliance miss / template (hand off)
  4. Severity — no DMARC or +all blocks inbox placement

Worked example

Observe: one SPF with +all; DKIM TXT present; no DMARC; marketing and
password-resets share example.com.
Interpret: anyone can spoof; Gmail/Yahoo bulk will fail; a campaign
complaint can sink transactional mail.
Classify: auth fail + domain mixing.
Fix: SPF -all (or ~all while warming), DMARC p=none+rua then
tighten, split transactional vs marketing domains — apply DNS only after approval.

Phase 0 — Detect sending setup [HIGH freedom]

  • Provider: Resend / Postmark / SES / SendGrid / Mailgun / SMTP
  • Sending domain(s) and DNS host
  • Transactional vs marketing — they should not share a domain
  • Where templates live (hand content issues to design-email)

Phase 1 — Authentication (pass/fail gate) [HIGH freedom; headers not DNS-only]

SPF — Authorizes the provider. Exactly one record. Under 10 DNS lookups. Not +all.

DKIM — Signing on at the provider; public key in DNS; real message headers signed (not DNS-only). 2048-bit keys.

DMARC — Record present. p=none (monitor) vs quarantine / reject. rua reporting address. Gmail/Yahoo require DMARC for bulk senders. Alignment: visible From domain matches SPF/DKIM domains. Misalignment passes raw SPF/DKIM and still fails DMARC.

PTR / dedicated IP — if self-hosted or dedicated: PTR set, warmed, not blocklisted.

Phase 2 — Reputation & hygiene [HIGH freedom]

Bounces — Hard bounces via webhook → suppression list honored on every send.

Complaints — Feedback loops / provider webhooks → immediate suppress.

List hygiene (marketing) — Opted-in only (cross-check plan-privacy-compliance). No purchased lists. Inactive addresses removed.

Sending patterns — Warm new domains. Separate transactional vs marketing so a campaign complaint does not sink password resets.

Content flags — Image-only, spammy phrasing, broken links, missing plain-text → design-email.

Phase 3 — Compliance footer [HIGH freedom]

  • Marketing: functional unsubscribe and one-click List-Unsubscribe

headers (Gmail/Yahoo bulk). Transactional is exempt only if it is genuinely transactional.

  • Physical address + sender ID — CAN-SPAM (US) and Japan 特定電子メール法

for advertising mail.

  • Unsubscribes honored on the next send.

Definition of Done

  • Streams identified and separated
  • SPF / DKIM (real headers) / DMARC + alignment scored
  • Bounce + complaint → suppression list
  • Consent + inactive policy noted
  • Warming addressed if cold
  • One-click unsubscribe on marketing; legal footer present
  • Template flags handed to design-email
  • DNS/config applied only after approval

Self-critique before applying DNS [LOW freedom — do not skip]

  1. Real headers — DKIM scored from a sent message, not DNS-only
  2. Alignment — From domain matches SPF/DKIM domains
  3. Streams split — marketing must not share the transactional domain
  4. Right owner — markup/copy → design-email
  5. Apply only on approval

Output format

  1. Auth table — SPF / DKIM / DMARC / alignment — pass/fail + exact fix
  2. Hygiene — bounce / complaint / list / warming
  3. Compliance — unsubscribe / footer / law
  4. Fix plan — auth first, then hygiene, then compliance
  5. Apply approved DNS/config; templates → design-email

Related

  • design-email — markup and copy
  • plan-privacy-compliance — consent to collect / to mail
  • audit-analytics — open/click instrumentation
  • backend-patterns — webhook + suppression store