CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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. Not for building deliverability setup — use deliverability-qa; not for designing lifecycle flows — use email-sequence-designer. 邮件质量审计/EQS评分/发送前放行

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

70%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-gated auditor workflow with explicit checkpoints, veto conditions, and persistence validation, and it is commendably free of padding. Its weaknesses are executability and bundling: the referenced runbooks, scorer, and validator script are absent from this bundle, so the detailed procedure cannot actually be followed here, and the reference sections overlap and point mostly outside the bundle.

Suggestions

Bundle or inline the execution-critical references (auditor-runbook.md, scoring-semantics.md, send-benchmark.md, runtime-invocation.md, measurement-protocol.md) — the ../../../references/ paths do not resolve in a standalone install where only references/auditor-runtime.md is present.

Ship scripts/validate-audit-artifact.py in the bundle; it is invoked by name with a --relative-path flag but no scripts/ directory exists.

Deduplicate the routing guidance (the Skill Contract prose line vs the Next Best Skill section) and resolve the §2/§3/§5 section numbering gap (no §1 or §4 appears in the body) or replace it with plain descriptive headers.

DimensionReasoningScore

Conciseness

The body is dense and lean — tables, terse bullets, no explanations of concepts Claude already knows (DMARC, MPP, and consent law are used, not taught). Not level 5 because routing guidance is stated twice ("Use `deliverability-qa` to repair authentication..." in Skill Contract and again as Next Best Skill links), and a few compressed jargon sentences ("Open rate is MPP-sensitive proxy evidence; direct action and the program's declared outcome truth set carry the outcome read") must be re-read; not level 3 because there is no padding anywhere.

4 / 5

Actionability

There is concrete structure — exact env-var resolution ("AARON_SKILLS_ROOT=\"${CLAUDE_PLUGIN_ROOT:-$(git rev-parse --show-toplevel 2>/dev/null || true)}\""), named veto IDs with conditions, exact scorer states (`score_state: NOT_SCORED`), the artifact path pattern `memory/audits/email/YYYY-MM-DD-<topic>.md`, and an invocation of `validate-audit-artifact.py --relative-path` — but the execution machinery is incomplete in this bundle: 4 of 5 Runtime Reads (`../../../references/auditor-runbook.md`, `scoring-semantics.md`, `send-benchmark.md`, `runtime-invocation.md`) and the validator script are not present, so an agent in this standalone context cannot fully execute the audit. This lands on the level-3 anchor (concrete guidance but incomplete, missing key details) rather than level 4, whose "minor gaps" these are not.

3 / 5

Workflow Clarity

The sequence is explicit and well-gated: declare profile → resolve runtime → freeze and reconcile evidence → score all 20 criteria → verify the four vetoes → run typed scorer → report with the exact typed header → validation checkpoints → persistence. It includes an explicit checklist (Validation Checkpoints), a validate→persist-once→revalidate feedback loop in Persistence, and error recovery when the scorer is unavailable (return `NOT_SCORED/UNDECIDED`), matching the level-5 anchor rather than level 4's "most checkpoints".

5 / 5

Progressive Disclosure

In-body structure is good (clear sections, details conceptually pushed to reference files, one level deep), but scored against the actual bundle most references dangle: only `references/auditor-runtime.md` exists, while the Runtime Reads and Reference Materials sections point at five `../../../references/*.md` files and the Next Best Skill section points at sibling SKILL.md files that are not in this bundle. Two overlapping reference lists (Runtime Reads vs Reference Materials, which additionally lists a `measurement-protocol.md` not in Runtime Reads) further muddy navigation. This fits the level-3 anchor (some structure, references present but organization is imperfect) rather than level 4's "most content is appropriately placed".

3 / 5

Total

15

/

20

Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete capability statement, natural quoted trigger phrases, explicit use-when guidance, and explicit negative boundaries that route adjacent jobs to sibling skills. Third-person voice is used correctly. The only blemishes are semi-opaque jargon ("typed 20-item SEND profile") and a redundant Chinese tail duplicating the summary, which costs it on specificity and trigger coverage.

DimensionReasoningScore

Specificity

The description names several concrete actions — "runs a typed 20-item SEND profile with authentication, consent, opt-out, and claim veto checks on own evidence" — which goes beyond the 1-2 actions of the level-3 anchor. It falls short of level 5 because these are sub-checks of one composite audit action rather than multiple distinct comprehensive actions, and phrases like "typed 20-item SEND profile" and "on own evidence" are semi-opaque jargon.

4 / 5

Completeness

It explicitly answers both questions: what ("runs a typed 20-item SEND profile with authentication, consent, opt-out, and claim veto checks") and when, with concrete quoted trigger phrases ("Use when the user asks to 'audit an email program' or 'is this campaign safe to send'"). This matches the level-5 anchor; it even adds explicit negative boundaries, which exceeds it.

5 / 5

Trigger Term Quality

It quotes natural phrases users would actually say — "audit an email program" and "is this campaign safe to send" — plus EQS/SEND terminology, giving good but not comprehensive coverage. Not level 5 because common variations like "pre-send check", "email QA", or "is it safe to send" are missing; not level 3 because real quoted trigger phrases are present, not just relevant keywords.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (send-readiness audit with EQS scoring) and explicitly disambiguates adjacent skills: "Not for building deliverability setup — use deliverability-qa; not for designing lifecycle flows — use email-sequence-designer". Minimal conflict risk, matching the level-5 anchor; the level-4 anchor's "minor overlap risk" understates this explicit routing.

5 / 5

Total

18

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 8 suspicious

Warning

Total

13

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

email/deliver/email-quality-auditor/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.