CtrlK
BlogDocsLog inGet started
Tessl Logo

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认证/发件域声誉

70

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, actionable pre-flight skill with an explicit validated workflow and clean progressive disclosure. Its main weakness is repetition: the same scope-guard boundary is asserted in four places, inflating tokens without adding clarity.

Suggestions

Consolidate the SEND-S / EQS scope-guard into a single canonical statement (e.g., keep it once in the Skill Contract and reference it from the intro, step 8, and Next Best Skill) to remove the four-way restatement and tighten conciseness.

Pull the two or three most decisive S1 pass/partial/veto-candidate criteria (e.g., 'no DMARC record → veto-candidate', 'p=none + aligned/passing → Partial') inline into step 2 so the core decision is actionable without opening the checklist, raising actionability toward 5.

In the repeated 'Not for…use X' routing, state each sibling-skill handoff once in Next Best Skill rather than re-deriving it in the Data Sources, step 6, and step 7 prose.

DimensionReasoningScore

Conciseness

Assumes Claude's intelligence (no padding about what SPF/DKIM/DMARC are) and concrete thresholds earn efficiency, but the SEND-S/EQS scope-guard boundary is restated four times (intro, step 8, a dedicated 'Scope guard' block, and Next Best Skill) — noticeable redundancy that could be tightened to one canonical statement.

3 / 5

Actionability

Gives executable commands ('python3 …/connectors/resend.py domains', 'python3 …/connectors/doh.py auth <domain> [--selector …]'), specific numeric thresholds (spam-complaint <0.1%, profile weights 0.30/0.20/0.35/0.25) and copy-pasteable Quick Start prompts; not 5 because the detailed per-check criteria live in the referenced checklist rather than inline.

4 / 5

Workflow Clarity

An 8-step numbered sequence with explicit validation checkpoints at each step (Unknown → NEEDS_INPUT, never pass-by-default, 100% applicable-coverage gate before scoring) plus termination rules (visited-set, max-depth:3, ambiguity stop) and a stop-on-veto-candidate feedback loop; this read-only QA skill has no destructive/batch op, so the cap does not apply.

5 / 5

Progressive Disclosure

Clear sectioned overview (Quick Start, Skill Contract, Data Sources, Instructions, Save Results, Reference Materials, Next Best Skill) with one-level-deep, well-signaled references; the in-bundle references/deliverability-checklist.md is a real file and cross-skill links are cleanly enumerated rather than nested.

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.

An exemplary description: concrete actions, verbatim natural trigger phrases, explicit what-and-when, and clear de-confliction from sibling skills. Token-dense but every clause earns its place.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'runs the ONE-TIME pre-send SEND S1 authentication pre-flight', 'builds the SEND S evidence read — DNS + DMARC-RUA auth, domain/IP reputation, inbox placement, content/link/render, and point-in-time bounce/complaint hygiene' — with comprehensive coverage; not below 5 because no concrete action is missing from the pre-flight scope.

5 / 5

Completeness

Explicitly answers both — 'what' (pre-flight + evidence read + Pass/Partial/Fail/Unknown/N/A scoring) and 'when' via concrete 'Use when the user asks to…' trigger phrases; the 'Not for…use X' negative scope further sharpens the when.

5 / 5

Trigger Term Quality

Quotes natural user phrases verbatim ('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 Chinese synonyms, covering synonyms and acronyms users actually say.

5 / 5

Distinctiveness Conflict Risk

Clear deliverability pre-flight niche with explicit negative routing to sibling skills (list-hygiene-monitor, email-quality-auditor, list-segment-builder), minimizing wrong-skill conflict; voice is third person so no specificity penalty applies.

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.

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