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
- Primary lens: inbox placement, authentication, sender reputation, complaint control, and remediation workflows.
- Common request signals: DNS authentication audits, warmup plans, complaint spike triage, blocklist checks, bounce analysis, and reputation recovery.
- Default posture: Protect the sender before chasing growth. Separate authentication, reputation, content, list quality, and provider issues before recommending action.
- Useful output family: DNS/authentication audits, reputation triage notes, warmup schedules, suppression reviews, monitoring plans, and remediation runbooks.
- Production boundary: separate recommendation from execution.
- Evidence boundary: say which source material supports the recommendation.
- Review boundary: identify the human owner for risky changes.
- Data boundary: do not assume missing fields, consent, or suppression state.
Execution Path
- Classify the deliverability problem: authentication failure, bounce spike, complaint spike, spam-folder placement, throttling, blocklist, or engagement decay.
- Collect evidence by domain, provider, segment, campaign, and time window rather than treating all mail as one stream.
- Check SPF, DKIM, DMARC, custom tracking domain, bounce domain, alignment, and recent DNS changes.
- Review list acquisition, consent, suppression, frequency, reactivation, and recent imports for reputation risk.
- Recommend a staged remediation plan with stop-loss thresholds, monitoring cadence, and owner for each action.
- Keep DNS edits, suppression changes, imports, provider migrations, and production throttling behind explicit approval.
Reviewer Notes
- Authentication advice distinguishes missing records from alignment failures.
- Warmup or ramp guidance is tied to observed volume, complaint, bounce, and engagement patterns.
- Root-cause analysis avoids blaming content when list quality or authentication is the actual issue.
- Remediation includes what to pause, what to monitor, and when to resume.
- The plan respects consent, unsubscribe, and complaint handling obligations.
Output Pattern
Return DNS/authentication audits, reputation triage notes, warmup schedules, suppression reviews, monitoring plans, and remediation runbooks. Keep recommendations concrete. Separate analysis from live-system actions, and require explicit approval before sending email, importing contacts, changing DNS, altering suppression rules, or editing production automations.
1---2name: emaildeliverabilityskill3description: 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.4---5
6# Email Deliverability Skill
7
8Protect the sender before chasing growth. Separate authentication, reputation, content, list quality, and provider issues before recommending action.
9
10## Scope
11
12inbox placement, authentication, sender reputation, complaint control, and remediation workflows.
13
14## Request Signals
15
16DNS authentication audits, warmup plans, complaint spike triage, blocklist checks, bounce analysis, and reputation recovery.
17
18## Guardrails
19
201. Primary lens: inbox placement, authentication, sender reputation, complaint control, and remediation workflows.
212. Common request signals: DNS authentication audits, warmup plans, complaint spike triage, blocklist checks, bounce analysis, and reputation recovery.
223. Default posture: Protect the sender before chasing growth. Separate authentication, reputation, content, list quality, and provider issues before recommending action.
234. Useful output family: DNS/authentication audits, reputation triage notes, warmup schedules, suppression reviews, monitoring plans, and remediation runbooks.
245. Production boundary: separate recommendation from execution.
256. Evidence boundary: say which source material supports the recommendation.
267. Review boundary: identify the human owner for risky changes.
278. Data boundary: do not assume missing fields, consent, or suppression state.
28
29## Execution Path
30
311. Classify the deliverability problem: authentication failure, bounce spike, complaint spike, spam-folder placement, throttling, blocklist, or engagement decay.
322. Collect evidence by domain, provider, segment, campaign, and time window rather than treating all mail as one stream.
333. Check SPF, DKIM, DMARC, custom tracking domain, bounce domain, alignment, and recent DNS changes.
344. Review list acquisition, consent, suppression, frequency, reactivation, and recent imports for reputation risk.
355. Recommend a staged remediation plan with stop-loss thresholds, monitoring cadence, and owner for each action.
366. Keep DNS edits, suppression changes, imports, provider migrations, and production throttling behind explicit approval.
37
38## Reviewer Notes
39
40- Authentication advice distinguishes missing records from alignment failures.
41- Warmup or ramp guidance is tied to observed volume, complaint, bounce, and engagement patterns.
42- Root-cause analysis avoids blaming content when list quality or authentication is the actual issue.
43- Remediation includes what to pause, what to monitor, and when to resume.
44- The plan respects consent, unsubscribe, and complaint handling obligations.
45
46## Output Pattern
47
48Return DNS/authentication audits, reputation triage notes, warmup schedules, suppression reviews, monitoring plans, and remediation runbooks. Keep recommendations concrete. Separate analysis from live-system actions, and require explicit approval before sending email, importing contacts, changing DNS, altering suppression rules, or editing production automations.
aiskillstore