email-quality-auditor
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.
Install / Use
npx skills add aaron-he-zhu/aaron-marketing-skills --skill email-quality-auditorInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
CommunicationSupported Platforms
Our assessment of email-quality-auditor
email-quality-auditor scores 90/100 on our quality scale, 210th of 395 Communication skills we index.
Its SKILL.md is 8.1 KB long, well organised into 17 sections with 1 code example: a thorough specification that gives an agent plenty to work with.
With 2,835 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so email-quality-auditor is actively maintained.
- Our last check on 2026-10-30 found the source still online.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
email-quality-auditor compared with similar skills
All 4 of these similar skills score higher than email-quality-auditor; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| email-quality-auditor (this skill)by aaron-he-zhu | 90 | 2.8k | 53d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
Frequently asked questions
- How do I install email-quality-auditor?
- Run
npx skills add aaron-he-zhu/aaron-marketing-skills --skill email-quality-auditor. The install tabs above show the steps for each supported agent. - Which AI agents does email-quality-auditor work with?
- It is written for Claude Code, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is email-quality-auditor safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is email-quality-auditor still maintained?
- The repository was last updated about 2 months ago, so email-quality-auditor is actively maintained.
Skill content
View source on GitHubname: 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: "20.1.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": "20.1.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 Reads
../../../references/auditor-runbook.md../../../references/scoring-semantics.md../../../references/send-benchmark.md../../../references/runtime-invocation.mdreferences/auditor-runtime.md
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 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.
Evidence and Scoring
- Freeze evidence and reconcile provider cohorts/windows before comparing rates.
- Score all 20
S1..D5criteria. Every observed state requires source/date/type/confidence. E2is N/A with reason when opens/CTOR are not used.N3/N5are conditional by program design. Missing records or exports are Unknown, not N/A.- Verify vetoes:
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.
- Run the typed scorer. Use clicks/replies/downstream actions as primary engagement evidence where available; opens/CTOR remain caveated proxy 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.
§2 SEND Worked Examples
- Complete newsletter profile, raw 81, no veto/fail:
DONE/SHIP, final 81. - Complete promotional profile, raw 76, one verified S1 failure:
DONE_WITH_CONCERNS/FIX, final 59. - Complete profile, verified S2 and N1 failures:
DONE/BLOCK, no final score. - Consent provenance absent: S2 Unknown,
NEEDS_INPUT/UNDECIDED, no score.
§3 SEND Guardrails
- DMARC
p=nonewith aligned SPF/DKIM and active monitoring is not automatically an S1 failure. - Provider one-click-unsubscribe policy and statutory duties must be named separately.
- Opens and CTOR require MPP segmentation/proxy caveat; they cannot establish human attention alone.
- A newsletter need not have cart/post-purchase flows; score only journeys applicable to its declared program.
- Over-frequency is a serious E4/E5 finding, not an automatic veto.
§5 SEND Translation
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.
Report and Verdict
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.
Validation Checkpoints
- Program/profile/provider/window/list age/market/MPP share are declared.
- Live suppression state was verified by replay, not a stale projection or pending proposal.
- All 20 states are valid; conditional N/A has a reason.
- Provider metrics and reconciled outcome truth are separated.
- No email/provider mutation occurred without separate explicit approval.
Persistence
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.
Reference Materials
Next Best Skill
- Authentication/placement: deliverability-qa
- Consent/suppression: consent-registry
- Lifecycle: email-sequence-designer
- Experiment: send-experiment-designer
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
