Review an email program before release using 20 SEND criteria. Checks authentication, consent, unsubscribe handling, claims, engagement, and outcome evidence, then reports a release verdict, required fixes, or specific gaps that prevent scoring.
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评分/发送前放行
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
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.
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.
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.
| 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 |
../../../references/auditor-runbook.md../../../references/scoring-semantics.md../../../references/send-benchmark.md../../../references/runtime-invocation.mdreferences/auditor-runtime.mdRead ../../../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 main. Before deterministic calls, follow runtime-invocation.md, resolve AARON_SKILLS_ROOT="${CLAUDE_PLUGIN_ROOT:-$(git rev-parse --show-toplevel 2>/dev/null || true)}", and require the scorer, validator, and typed catalogs. If unavailable, return score_state: NOT_SCORED / score_confidence: not_scored with no gate verdict or persistent artifact.
Declare profile (promotional|retention|cold-outbound|newsletter), target/program, provider, market, normalized window, list age, MPP share, and observation date.
S1..D5 criteria. Every observed state requires source/date/type/confidence.E2 is N/A with reason when opens/CTOR are not used. N3/N5 are conditional by program design. Missing records or exports are Unknown, not N/A.SEND-S1: required authentication is demonstrably broken/unaligned.SEND-S2: a purchased/scraped/unlawful list is verified; missing provenance is Unknown.SEND-N1: opt-out is broken/absent or a recorded suppression is not honored.SEND-D1: material claim/disclosure/offer term fails approved evidence.For a send-only review without enough program evidence, report the verified red-line checks and exact gaps but return NOT_SCORED/UNDECIDED; “no blocker observed in supplied evidence” is not a full SEND SHIP verdict.
DONE/SHIP, final 81.DONE_WITH_CONCERNS/FIX, final 59.DONE/BLOCK, no final score.NEEDS_INPUT/UNDECIDED, no score.p=none with aligned SPF/DKIM and active monitoring is not automatically an S1 failure.Explain channel and recipient risk in plain language. On trace request, qualify SEND-S1/S2/N1/D1 and show the underlying DNS/event/rendered evidence.
Begin with the auditor-runbook's exact typed conversation header. Never replace status, verdict, or score_state with prose; list each explicitly missing qualified item as ``ID: `unknown``` before findings.
Show verdict, profile/context, score or coverage/interval, confidence, S/E/N/D detail, outcome truth set, verified critical controls, Unknown inputs, and fix owners. Do not claim deliverability/inbox placement from DNS alone and do not execute a send.
Persist only after explicit authorization to memory/audits/email/YYYY-MM-DD-<topic>.md. Preserve the scorer's orthogonal status and verdict; validate the complete v3 draft with validate-audit-artifact.py against the intended --relative-path, persist only through one full-content Write, and revalidate the target per the auditor runbook. Edit/shell/MCP mutations of the reserved sink are unsupported. Do not autonomously modify consent, claims, provider settings, or hot cache.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Audit paid advertising accounts before increasing spend by comparing campaign exports with your own sales or lead records. Review 20 criteria covering measurement, spending, and safety, then receive a decision and prioritized fixes.
Create paid-ad headlines, descriptions, and opening hooks that match the destination page. Build a matrix of messaging angles and variants, check format limits, and flag unsupported claims or policy risks before handing the set off for review.
Plan advertising and landing page experiments with a clear hypothesis, controlled variants, sample sizes, and duration. Interpret exported results by separating statistical evidence from meaningful business impact, applying an action rule only when its owner approved it in advance.
Design employee and founder sharing programs with voluntary participation, personalized share kits, disclosure lines, and staggered posting windows. Get roster and Slack or Teams distribution specifications, plus safeguards against identical coordinated posts and organized engagement exchanges.
Reconcile paid advertising conversions with GA4 or ecommerce order records. Identify duplicate and unmatched claims, align attribution windows and currencies, compare how models assign credit, and assess additional orders when test and control data are available.
Turn customer interviews and won or lost deal notes into a map of buyer beliefs, recurring objections, and reasons to switch or stay. Each finding includes its evidence, with suggested ways to address objections and clear labels for assumptions.