CtrlK
BlogDocsLog inGet started
Tessl Logo

email-deliverability

Make sure email actually reaches inboxes. Use this skill when setting up email authentication (SPF, DKIM, DMARC), diagnosing emails landing in spam, planning a domain reputation strategy, monitoring sender reputation, or hardening against email spoofing. Triggers on email deliverability, SPF, DKIM, DMARC, spam folder, sender reputation, mailbox provider, soft bounces, bounce rate, BIMI, MTA-STS, deliverability audit. Also triggers when a marketing or transactional email isn't reaching users.

70

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 skill body organized around three pillars and an 8-step workflow with a cleanly separated reference playbook. Strongest on progressive disclosure; slight room to tighten prose and make validation gates fully explicit.

Suggestions

Make validation gates explicit as feedback loops (e.g., 'after combining SPF senders, re-run dig and confirm the lookup count is under 10 before proceeding') to push workflow_clarity to 5.

Trim editorial asides like 'The single biggest deliverability lever for most senders is list hygiene' to keep conciseness lean.

Convert the SPF/DKIM fix orders into copy-pasteable command sequences where possible (e.g., a one-liner to count SPF lookups) to lift actionability.

DimensionReasoningScore

Conciseness

Dense and operational, assuming Claude's competence without padding concepts it already knows; a few editorializing asides ('The single biggest deliverability lever…') could be trimmed.

4 / 5

Actionability

Provides executable `dig` commands, copy-paste DNS record templates, and specific numeric targets; the SPF/DKIM fix orders are procedural steps rather than runnable scripts, leaving minor gaps.

4 / 5

Workflow Clarity

An 8-step sequenced workflow with real checkpoints (test-send verify, monitor reports 2-4 weeks, gradual pct gating) and an implicit monitor→fix→increase feedback loop; a few validation gates are implicit rather than spelled out.

4 / 5

Progressive Disclosure

Clear overview with a single one-level-deep reference (references/dmarc-rollout-playbook.md, verified to exist) signaled in a dedicated 'Reference files' section with a concise description.

5 / 5

Total

17

/

20

Passed

Description

95%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, well-targeted description that clearly states capability and trigger conditions with comprehensive keyword coverage. Minor specificity drag comes from one slightly abstract phrasing ('planning a domain reputation strategy').

DimensionReasoningScore

Specificity

Lists several concrete actions ('setting up email authentication (SPF, DKIM, DMARC)', 'diagnosing emails landing in spam', 'monitoring sender reputation', 'hardening against email spoofing') with only minor abstraction in 'planning a domain reputation strategy'.

4 / 5

Completeness

Explicitly answers both 'what' ('Make sure email actually reaches inboxes') and 'when' ('Use this skill when…', 'Also triggers when…') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive trigger coverage including natural phrases ('emails landing in spam', 'spam folder') and technical acronyms (SPF, DKIM, DMARC, BIMI, MTA-STS) plus the user-facing phrasing 'marketing or transactional email isn't reaching users'.

5 / 5

Distinctiveness Conflict Risk

Clear email-deliverability niche with distinct technical triggers (DMARC, BIMI, MTA-STS, sender reputation) that are unlikely to fire for unrelated skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
rampstackco/claude-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.