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

89%

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

81%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-constructed instruction skill: an unambiguous 8-step workflow with genuine validation gates (Unknown/NEEDS_INPUT instead of pass-by-default), concrete thresholds, and executable connector commands. The main costs are the four-fold repetition of the scope guard and a web of cross-skill references whose targets fall outside this bundle.

Suggestions

State the scope guard (no EQS computation, no veto enforcement, trend belongs to list-hygiene-monitor) once in the intro and once in the Scope guard section, and cut the restatements in step 1, step 8, and the S2/hygiene steps to a short pointer — this would recover conciseness without losing the boundary.

Verify or inline-fallback the connector commands: scripts/connectors/doh.py and resend.py are referenced as executable but the scripts/ directory is not part of this bundle, so a missing file breaks the copy-paste path.

Move the per-profile S-weight table (0.30/0.20/0.35/0.25) and the spam-content/link/render criteria into references/deliverability-checklist.md, keeping only the profile names and red-line thresholds in SKILL.md, so the body is a leaner overview pointing one level deep.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence — no basic DMARC/reputation concept explanations, and specifics like the 0.1% complaint red line and per-profile weights (0.30/0.20/0.35/0.25) earn their tokens. However, the scope guard (this skill does NOT compute EQS or enforce vetoes; the trend belongs to list-hygiene-monitor) is restated at least four times — intro paragraph, step 1, step 8, the 'Scope guard' paragraph, and Next Best Skill — which is more than the 'minor instances' of anchor 5 but better than the 'unnecessary explanation' of anchor 3.

4 / 5

Actionability

Gives two copy-paste-ready commands ('python3 "${CLAUDE_PLUGIN_ROOT}/scripts/connectors/doh.py" auth <domain> [--selector <esp-dkim-selector>]' and 'resend.py domains'), exact thresholds, typed profiles, and a deterministic state machine. It falls short of anchor 5 because the referenced connector scripts and most cross-referenced files (../../../references/send-benchmark.md, CONNECTORS.md, skill-contract.md) are not present in the bundle, so the commands' executability cannot be fully confirmed, and the workflow inputs remain placeholders ('[paste/path]', '[name]').

4 / 5

Workflow Clarity

Eight clearly sequenced numbered steps with explicit validation checkpoints throughout: missing DMARC RUA or seed test forces the item to 'Unknown' and the run to 'NEEDS_INPUT — never pass-by-default', a 'Done when' contract, defined S1 flag outcomes, and Termination rules (stop on veto-candidate or Unknown). This matches anchor 5's 'clear sequence with explicit validation steps; feedback loops; checklists' — the detailed checklist is split into references/deliverability-checklist.md, which exists and matches its description.

5 / 5

Progressive Disclosure

Good structure: an overview body with clearly labeled sections, a Reference Materials list, and the detailed checklist correctly split into the bundle's one real file, references/deliverability-checklist.md, referenced one level deep. It does not reach anchor 5 because most other references point outside the skill directory (../../../references/*, ../../deliver/email-quality-auditor, ../list-hygiene-monitor, protocol/consent-registry) and cannot be resolved from the bundle, and some step-level detail (e.g., per-profile benchmark rows) is inlined where the checklist file could carry it.

4 / 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.

An exemplary description: it names the domain and specific actions, quotes four natural user trigger phrases (plus Chinese synonyms), and explicitly fences off the three adjacent skills to prevent mis-triggering. The only nitpick is density — it packs a lot into one field — but every clause is informative rather than padded, so verbosity is not penalized.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'DNS + DMARC-RUA auth, domain/IP reputation, inbox placement, content/link/render, and point-in-time bounce/complaint hygiene' — plus the explicit output states 'Pass/Partial/Fail/Unknown/N/A'. Coverage of the deliverability pre-flight domain is comprehensive, matching the anchor-5 example; it is not anchor 4 because no capability area is missing.

5 / 5

Completeness

Both 'what' (runs the S1 authentication pre-flight and builds the SEND S evidence read across five named areas with named output states) and 'when' ('Use when the user asks to... [four concrete trigger phrases]') are explicitly and clearly answered with concrete trigger phrases, exactly matching the anchor-5 example.

5 / 5

Trigger Term Quality

Quotes natural user phrases verbatim ('"check my SPF/DKIM/DMARC/BIMI"', '"why am I landing in spam / promotions"', '"score my sender reputation and list hygiene"') and adds Chinese-language synonyms ('邮件送达率预检/SPF DKIM DMARC认证/发件域声誉'), giving comprehensive natural-term coverage including synonyms. Internal jargon (SEND S, EQS) appears in the 'what' clause, not the triggers, so it does not dilute the natural keywords.

5 / 5

Distinctiveness Conflict Risk

Clear niche (one-time pre-send deliverability snapshot) with explicit negative triggers that route adjacent requests elsewhere: '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 stronger than anchor 4's 'minor overlap risk' — conflicts with closely related sibling skills are actively pre-empted.

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.