スキル email-deliverability-specialist

📦

email-deliverability-specialist

Name: email-deliverability-specialist
Author: email-marketing-skills-hub

コンテンツリビジョン r1 安全 🌐 ネットワークアクセス

Diagnose Email Deliverability Problems

Email authentication failures, filtering and consent gaps can hide behind successful delivery reports. This skill turns diagnostic evidence into prioritized findings and reversible remediation plans.

対応: Claude Codex Code(CC)

📊 71 十分

Maintain this Skill? Claim it 📊 71 十分

自分のエージェントでインストール

このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。

エージェントリクエスト

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

エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。

エージェントが読めるリソース

AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。

Markdown詳細 GET /skills/email-marketing-skills-hub-email-deliverability-specialist.md 署名済み manifest GET /api/skills/email-marketing-skills-hub-email-deliverability-specialist/manifest 署名済み lockfile GET /api/skills/email-marketing-skills-hub-email-deliverability-specialist/lockfile

テストする

「email-deliverability-specialist」を使用しています。 Synthetic receiver results show SPF and DKIM passing for mailer.example.net, but DMARC failing for a visible From domain of example.com.

期待される結果:

Observed: neither authenticated domain aligns with the visible From domain.
A second SPF record will not repair this alignment failure.
Verify platform support for aligned DKIM or a custom return path before proposing authorized changes.
Check new receiver results after implementation; authentication success does not guarantee inbox placement.

「email-deliverability-specialist」を使用しています。 An ESP reports 99% delivered and 0.1% complaints, while Yahoo reports 0.4% complaints. The team proposes doubling volume.

期待される結果:

Server acceptance does not establish inbox placement.
Compare reporting windows and denominators before interpreting the complaint-rate difference.
Investigate consent sources, suppression behavior and recent sending changes.
Do not double volume without evidence supporting expansion; define provider-specific monitoring and stopping criteria.

「email-deliverability-specialist」を使用しています。 A synthetic marketing message has a body unsubscribe link, but no evidence of one-click headers or downstream suppression.

期待される結果:

A body link alone does not establish RFC 8058 one-click support.
Inspect List-Unsubscribe, List-Unsubscribe-Post and DKIM coverage of both headers.
Test the POST flow only with an authorized synthetic subscriber.
Verify downstream suppression and processing time rather than relying only on endpoint success.

セキュリティ監査

安全

v1 • 2026/11/4 バージョン別レポートを開く

All 11 static findings are false positives in diagnostic guidance, synthetic evaluation cases or explicit safety instructions. No evidence found of credential extraction, unauthorized sending, malicious reconnaissance or prompt injection. The skill requires authorization for changes and protects private keys, recipient data and suppression records.

スキャンされたファイル

160

解析済み行数

レビュー項目

誤検知を無視

リスク要因

🌐 ネットワークアクセス (4)

evals/cases.md:6 references/authentication.md:5 references/reputation-consent.md:5 SKILL.md:12

最新の完了済み静的・セマンティック監査では、確認済みのセキュリティ検出事項は見つかりませんでした。これは、スキルに副作用がないことを証明するものではありません。

監査者: codex

このレポートを共有・引用

バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。

バージョン別レポートを開く

レポートリンクをコピー

https://skillstore.io/skills/email-marketing-skills-hub-email-deliverability-specialist/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdownバッジ

[![Skillstore security assessment](https://skillstore.io/badges/skills/email-marketing-skills-hub-email-deliverability-specialist/security.svg)](https://skillstore.io/skills/email-marketing-skills-hub-email-deliverability-specialist?utm_source=security_passport_badge)

HTMLバッジ

<a href="https://skillstore.io/skills/email-marketing-skills-hub-email-deliverability-specialist?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/email-marketing-skills-hub-email-deliverability-specialist/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

埋め込みカード

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

学術引用 (APA · BibTeX · CFF)

APA形式の引用

email-marketing-skills-hub. (2026). email-deliverability-specialist security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/email-marketing-skills-hub-email-deliverability-specialist/audits/1

BibTeX形式の引用

@techreport{email-marketing-skills-hub-email-marketing-skills-hub-email-deliverability-specialist-2026,
  author = {email-marketing-skills-hub},
  title = {email-deliverability-specialist security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/email-marketing-skills-hub-email-deliverability-specialist/audits/1},
  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: "email-deliverability-specialist security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "email-marketing-skills-hub"
date-released: "2026-11-04"
url: "https://skillstore.io/skills/email-marketing-skills-hub-email-deliverability-specialist/audits/1"
identifiers:
  - type: other
    value: "skillstore:email-marketing-skills-hub-email-deliverability-specialist:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore スコア

このスコアの理由証拠の信頼度: 中

アーキテクチャ

保守性

コンテンツ

コミュニティ

仕様準拠

作成できるもの

Investigate Authentication Failures

Reconcile receiver headers with sender configuration and public DNS to identify alignment failures and prepare controlled changes.

Plan Reputation Recovery

Compare provider complaint metrics, list provenance and sending changes to contain affected traffic and define measurable recovery steps.

Audit Subscription Workflows

Trace permission status from signup through integrations, unsubscribe processing and suppression using authorized synthetic contacts.

これらのプロンプトを試す

Triage a Delivery Problem

Our [marketing or transactional] emails reach spam at [mailbox provider]. We use [platform]. Ask for essential redacted evidence and identify initial diagnostic steps.

Explain Authentication Alignment

Review these redacted receiver headers and DNS results: [artifacts]. Explain SPF, DKIM and DMARC alignment. Separate observed facts from unknowns. Do not change settings.

Audit Consent and Unsubscribe

Audit [signup flow], [integration] and [unsubscribe evidence]. Check eligibility, one-click headers and suppression synchronization. Propose synthetic tests and identify required approvals.

Build a Controlled Recovery Plan

Using [redacted provider metrics], [SMTP errors], [sender inventory] and [recent changes], build a prioritized recovery plan. Include denominators, hypotheses, owners, approvals, rollback and stopping criteria.

ベストプラクティス

Provide redacted receiver headers, timestamped DNS evidence and provider-specific metrics with clear denominators.
Require explicit approval before sending tests, changing DNS, editing suppressions or sharing reports externally.
Verify current primary documentation and use synthetic contacts to test complete workflows.

回避

Treating authentication passes or ESP acceptance as proof of inbox placement.
Removing suppressions, buying lists or rotating domains to bypass reputation enforcement.
Deploying invented DNS values or strict DMARC policies without sender inventory, approval and rollback.

よくある質問

Which AI tools can use this skill?

The skill supports Claude, Codex and Claude Code. Live checks depend on the tools and permissions available in each environment.

Does the skill send emails or change DNS automatically?

It includes diagnostic instructions, not sending or deployment software. It requires authorization before campaign sends, DNS changes or account configuration.

Can it diagnose problems without account access?

Yes. It can analyze supplied redacted artifacts and provide read-only collection steps. It must mark unavailable checks as unknown.

Will passing SPF, DKIM and DMARC guarantee delivery?

No. Authentication does not guarantee inbox placement. Reputation, consent, filtering and recipient-provider policies remain relevant.

What information should I provide?

Provide your sending platform, affected providers, sending domains, recent changes and representative errors. Redact recipient data and never share private keys or credentials.

Does it certify legal or provider compliance?

No. It helps identify evidence and requirements, but legal obligations and provider rules require current, context-specific verification.