CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deliverability-qa

Use when the user asks to "run a deliverability pre-flight before I send", "check my SPF/DKIM/DMARC/BIMI", "why am I landing in spam / promotions", or "score my sender reputation and list hygiene"; runs the ONE-TIME pre-send SEND S1 authentication pre-flight and builds the SEND S (Sender-integrity / Deliverability) evidence read — DNS + DMARC-RUA auth, domain/IP reputation, inbox placement, content/link/render, and point-in-time bounce/complaint hygiene — using Pass/Partial/Fail/Unknown/N/A states and scoring only at complete applicable coverage. Not for the recurring hygiene trend — use list-hygiene-monitor; not for final EQS or veto verdicts — use email-quality-auditor; not for segments/suppression lists — use list-segment-builder. 邮件送达率预检/SPF DKIM DMARC认证/发件域声誉

Quality

88%

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

77%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.

A well-structured, highly actionable pre-flight workflow with explicit validation gates and clean one-level reference separation; the one real weakness is redundancy — the EQS/list-hygiene-monitor boundary is repeated so often it inflates token cost without adding information. The Chinese-language displayName/summary in frontmatter is fine, and the body stays instruction-dense rather than educational.

Suggestions

State the S1 pre-flight boundary and the list-hygiene-monitor vs. one-time-snapshot distinction once (e.g., in the Scope guard section) and cut the repetitions in the intro paragraph, step 1, and step 6 to save tokens.

Name the inbox-placement and reputation pass/partial thresholds inline (as done for the 0.1% complaint red line) or point to the exact section of send-benchmark.md, so the run doesn't require opening the reference to apply them.

Include the Pass = 10 / Partial = 5 / Fail = 0 scoring rule (or an explicit pointer to the checklist's scoring section) in step 8 so the S-score computation is self-contained.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows (no "what is DMARC" padding) and every section carries operational content, but the scope guard against list-hygiene-monitor and email-quality-auditor is restated nearly verbatim at least four times (intro paragraph, step 6, step 1's "Restate the scope line", the standalone Scope guard paragraph, and Next Best Skill), which is unnecessary repetition that could be tightened. This fits the level-3 anchor ("mostly efficient but... could be tightened") better than level 4, where over-explanation would be only minor.

3 / 5

Actionability

Concrete, executable guidance throughout: exact commands ("python3 \"${CLAUDE_PLUGIN_ROOT}/scripts/connectors/doh.py\" auth <domain> [--selector <esp-dkim-selector>]"), specific numbers (profile weights 0.30/0.20/0.35/0.25, "spam-complaint red line < 0.1%"), typed S1 flag states, and a real referenced checklist file. Minor gaps keep it below 5: the inbox-placement and reputation thresholds are deferred to send-benchmark.md rather than stated ("state inbox vs spam vs promotions placement against the threshold" never names the threshold), and the S-scoring formula (Pass = 10 / Partial = 5 / Fail = 0) lives only in the reference file.

4 / 5

Workflow Clarity

The eight numbered steps are clearly sequenced (scope/profile → S1 auth → reputation → placement → content scan → hygiene → S2 context → score), and each evidence-gathering step carries an explicit validation gate: "If the DMARC RUA report is absent, mark the authentication item Unknown and the run NEEDS_INPUT — never pass-by-default", "require 100% applicable qualified-item coverage. Only then score S", plus termination stop conditions and a "Done when" completion contract. This matches the level-5 anchor's explicit validation steps and error-recovery routing.

5 / 5

Progressive Disclosure

The body is a clear ~80-line overview with well-signaled, one-level-deep references: the checklist detail is split into the real references/deliverability-checklist.md (44 lines, verified present), and Reference Materials annotates each link (send-benchmark.md, skill-contract.md, CONNECTORS.md, SECURITY.md, consent-registry) with what it provides. Navigation is easy and nothing that belongs in a separate file is inlined.

5 / 5

Total

17

/

20

Passed

Description

100%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.

The description is exemplary: it pairs concrete natural-language trigger phrases with a comprehensive enumeration of the skill's actions and output states, and it carves out three sibling skills by name to prevent mis-triggering. The trailing Chinese keyword string slightly pads length, but every clause carries disambiguating or triggering information rather than fluff.

DimensionReasoningScore

Specificity

The description enumerates the full concrete scope: "runs the ONE-TIME pre-send SEND S1 authentication pre-flight and builds the SEND S (Sender-integrity / Deliverability) evidence read — DNS + DMARC-RUA auth, domain/IP reputation, inbox placement, content/link/render, and point-in-time bounce/complaint hygiene — using Pass/Partial/Fail/Unknown/N/A states", covering every sub-area the skill body's steps address. It matches the anchor for multiple specific concrete actions with comprehensive coverage, not the level-4 anchor ("minor gaps").

5 / 5

Completeness

It opens with an explicit "Use when the user asks to..." clause listing concrete trigger phrases, and separately states the what (one-time pre-flight building the SEND S evidence read with per-item states and scoring only at complete applicable coverage). Both what and when are explicit and concrete, matching the level-5 anchor exactly.

5 / 5

Trigger Term Quality

It quotes the exact natural phrases a user would say — "run a deliverability pre-flight before I send", "check my SPF/DKIM/DMARC/BIMI", "why am I landing in spam / promotions", "score my sender reputation and list hygiene" — plus domain jargon (SPF, DKIM, DMARC, BIMI, RUA) and bilingual (Chinese) synonyms, giving comprehensive coverage including variations. Not the level-4 anchor, since no common natural terms are missing.

5 / 5

Distinctiveness Conflict Risk

The niche is clear (one-time pre-send deliverability pre-flight) and it explicitly disambiguates the three adjacent skills: "Not for the recurring hygiene trend — use list-hygiene-monitor; not for final EQS or veto verdicts — use email-quality-auditor; not for segments/suppression lists — use list-segment-builder". This is minimal conflict risk, beyond the level-4 anchor's "minor overlap risk".

5 / 5

Total

20

/

20

Passed

Validation

75%

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

Validation — 12 / 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: 24 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing, 1 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

email/setup/deliverability-qa/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.