| name | email-quality-auditor |
| slug | aaron-email-quality-auditor |
| displayName | Email Quality Auditor · 邮件质量审计 |
| summary | 邮件质量审计/EQS评分/发送前放行 |
| description | Use when the user asks to "audit an email program" or "is this campaign safe to send"; runs a typed 20-item SEND profile with authentication, consent, opt-out, and claim veto checks on own evidence. Not for building deliverability setup — use deliverability-qa; not for designing lifecycle flows — use email-sequence-designer. 邮件质量审计/EQS评分/发送前放行 |
| version | 19.0.0 |
| license | Apache-2.0 |
| compatibility | Claude Code and compatible agent-skill hosts |
| homepage | https://github.com/aaron-he-zhu/aaron-marketing-skills |
| when_to_use | Use when checking an email program or send before release, or when authentication, consent, suppression, engagement quality, lifecycle fit, claims, or outcome attribution are in doubt. |
| argument-hint | <ESP/DMARC/outcome evidence> [promotional|retention|cold-outbound|newsletter] |
| allowed-tools | WebFetch |
| class | auditor |
| metadata | {"author":"aaron-he-zhu","version":"19.0.0","discipline":"email","phase":"deliver","geo-relevance":"low","hermes":{"tags":["marketing","email","deliver"],"category":"email"},"openclaw":{"emoji":"✉️","homepage":"https://github.com/aaron-he-zhu/aaron-marketing-skills"}} |
Email Quality Auditor
Audit one email program/profile and observation window with SEND. Open rate is MPP-sensitive proxy evidence; direct action and the program's declared outcome truth set carry the outcome read.
When This Must Trigger
- Before a material broadcast/sequence release when channel safety is uncertain.
- When authentication, consent, suppression, complaints, frequency, claims, or attribution need a gate.
- When the user requests an EQS/SEND baseline or rerun.
Quick Start
Audit this newsletter using the last 90 days, provider split, MPP share, and subscription truth set.
Check this promotional send against DMARC, consent events, live suppressions, claims, and order IDs.
Skill Contract
Reads: one program/profile, normalized window, provider evidence, live consent/suppression state, rendered messages, and outcome truth. Writes: only a permissioned v3 artifact. Done when: all expected SEND states are explicit and the scorer result is reported without sending email or changing provider settings.
Use deliverability-qa to repair authentication, consent-registry for lawful-basis/suppression facts, email-sequence-designer for journeys, and send-experiment-designer for preregistered tests.
Data Sources
| Need | Preferred evidence |
|---|
| Authentication | DNS, message headers, DMARC aggregate evidence |
| Consent/suppression | Append-only consent events plus current live projection |
| Placement/reputation | Provider/seed panel and dated ESP/provider reports |
| Engagement | Cohort/provider/MPP-segmented ESP export |
| Lifecycle | Trigger/flow configuration and event export |
| Outcome | Ecommerce, CRM, subscription, sponsorship, or named equivalent truth set |
| Content | Rendered message/destination and approved claim/disclosure state |
Instructions
Runtime and Setup
Read ../../../references/auditor-runbook.md, scoring-semantics.md, send-benchmark.md, and the SEND catalog entry. Standalone installs use bundled immutable references/auditor-runtime.md; never fetch mutable . Before deterministic calls, follow , resolve , and require the scorer, validator, and typed catalogs. If unavailable, return / with no gate verdict or persistent artifact.
