Skills emaildeliverabilityskill

📦

emaildeliverabilityskill

Name: emaildeliverabilityskill
Author: Sequenzy

Content revision r1 Safe

Improve Email Deliverability Workflows

Email deliverability problems can hide across DNS, reputation, list quality, and provider behavior. This skill helps Claude, Codex, and Claude Code build clear audits, triage notes, and remediation plans.

Supports: Claude Codex Code(CC)

📊 74 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "emaildeliverabilityskill" from https://skillstore.io/skills/sequenzy-emaildeliverabilityskill.md and its manifest at https://skillstore.io/api/skills/sequenzy-emaildeliverabilityskill/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sequenzy-emaildeliverabilityskill.md Signed manifest GET /api/skills/sequenzy-emaildeliverabilityskill/manifest Signed lockfile GET /api/skills/sequenzy-emaildeliverabilityskill/lockfile

Test it

Using "emaildeliverabilityskill". A new sending domain needs authentication review before campaign launch.

Expected outcome:

A DNS audit separates SPF, DKIM, DMARC, tracking domain, and bounce-domain checks, then lists approvals before changes.

Using "emaildeliverabilityskill". Complaint rate increased after a reactivation campaign.

Expected outcome:

A triage note segments complaints by source and campaign, pauses risky sends, and defines continue, slow, or stop thresholds.

Using "emaildeliverabilityskill". A sender needs a ramp plan after provider migration.

Expected outcome:

A warmup schedule ties volume to complaint, bounce, engagement, and provider signals, with daily monitoring and owner assignments.

Security Audit

Safe

v3 • 7/6/2026 Open versioned report

Static analysis reported no suspicious patterns across this prompt-only skill. Manual review found no prompt injection, code execution, network access, credential handling, or unsafe autonomous action intent. The skill requires explicit approval for high-risk email system changes.

Files scanned

Lines analyzed

Review items

False positives ignored

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/sequenzy-emaildeliverabilityskill/audits/3?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sequenzy-emaildeliverabilityskill/security.svg)](https://skillstore.io/skills/sequenzy-emaildeliverabilityskill?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sequenzy-emaildeliverabilityskill?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sequenzy-emaildeliverabilityskill/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sequenzy-emaildeliverabilityskill.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

Sequenzy. (2026). emaildeliverabilityskill security audit report (audit version 3) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sequenzy-emaildeliverabilityskill/audits/3

BibTeX citation

@techreport{sequenzy-sequenzy-emaildeliverabilityskill-2026,
  author = {Sequenzy},
  title = {emaildeliverabilityskill security audit report (audit version 3)},
  institution = {Skillstore},
  year = {2026},
  number = {3},
  url = {https://skillstore.io/skills/sequenzy-emaildeliverabilityskill/audits/3},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "emaildeliverabilityskill security audit report (audit version 3)"
version: "unspecified"
type: report
authors:
  - name: "Sequenzy"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/sequenzy-emaildeliverabilityskill/audits/3"
identifiers:
  - type: other
    value: "skillstore:sequenzy-emaildeliverabilityskill:audit:3"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Audit Domain Authentication

Review SPF, DKIM, DMARC, tracking, bounce, and alignment evidence before a campaign or migration.

Triage Reputation Incidents

Separate complaint, bounce, blocklist, provider, and list-quality causes before choosing a remediation path.

Plan Controlled Sending Ramps

Create warmup schedules with monitoring cadence, stop-loss thresholds, and explicit approval gates.

Try These Prompts

Audit DNS Authentication

Use $emaildeliverabilityskill to review SPF, DKIM, DMARC, tracking domain, and bounce domain status. Separate missing records from alignment failures.

Triage Complaint Spike

Use $emaildeliverabilityskill to analyze a complaint spike by provider, campaign, segment, consent source, recent imports, and time window. Recommend pause and resume thresholds.

Build Warmup Plan

Use $emaildeliverabilityskill to create a warmup plan tied to volume, complaint rate, bounce rate, engagement, and mailbox provider response.

Design Recovery Runbook

Use $emaildeliverabilityskill to build a recovery runbook covering blocklists, bounces, complaints, suppression review, owner assignments, monitoring, and approval gates.

Best Practices

Provide domain, provider, segment, campaign, and time-window data before requesting remediation.
Keep live DNS, suppression, import, migration, and automation changes behind explicit approval.
Segment complaint and bounce rates by source and campaign before changing content or volume.

Avoid

Treating all mailbox providers, campaigns, and contact sources as one stream.
Increasing send volume before resolving complaint, bounce, or authentication issues.
Editing DNS or suppression rules without an owner, approval record, and rollback plan.