cold-email-deliverability
Check Email Deliverability Before Launch
Authentication gaps and domain reputation problems can disrupt outreach before a campaign starts. This skill guides 15 readiness checks and organizes failures into prioritized fixes.
Установить с помощью моего Агента
Скопируйте этот запрос в своего Агента. Он содержит каноническую страницу Skill и манифест.
Review the Skillstore skill "cold-email-deliverability" from https://skillstore.io/skills/cmj-hub-cold-email-deliverability.md and its manifest at https://skillstore.io/api/skills/cmj-hub-cold-email-deliverability/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Ваш Агент по-прежнему должен показать план и запросить все подтверждения, требуемые политикой безопасности.
Ресурсы для AI-агентов
Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.
Протестировать
Использование «cold-email-deliverability». Fourteen checks passed, but SPF does not include our sending provider. Summarize readiness and the next action.
Ожидаемый результат:
- Checklist score: 93.3/100, grade B.
- Launch status: hold. The SPF failure remains a blocker despite the numerical grade.
- First action: correct provider authorization in SPF, check the DNS lookup limit, and verify authentication before sending.
Использование «cold-email-deliverability». Ten checks passed. Mailbox age, sending volume, reply ratio, reverse DNS, and blacklist checks failed. Prioritize the fixes.
Ожидаемый результат:
- Checklist score: 66.7/100, grade D. Hold the campaign.
- Resolve the blacklist issue first and verify reverse DNS with the sending provider.
- Reduce sending volume, continue mailbox preparation, and review reply performance before reassessing.
Аудит безопасности
Средний рискAll 28 static findings are false positives involving Markdown, legitimate diagnostic lookups, public reference links, or a documentation path. No evidence found of credential theft, destructive actions, or prompt injection. One semantic issue remains: score-based launch advice can conflict with mandatory authentication and blacklist blockers.
Подтверждённые проблемы безопасности (1)
Факторы риска
⚙️ Внешние команды (23)
🌐 Доступ к сети (2)
📁 Доступ к файловой системе (1)
Поделиться и цитировать этот отчет
Делитесь версионным отчетом об оценке, нейтральным значком, встраиваемой карточкой и цитатами. Skillstore публикует доказательства, не решая, безопасен ли этот Skill.
Копировать ссылку на отчёт
https://skillstore.io/skills/cmj-hub-cold-email-deliverability/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportЗначок Markdown
[](https://skillstore.io/skills/cmj-hub-cold-email-deliverability?utm_source=security_passport_badge)Значок HTML
<a href="https://skillstore.io/skills/cmj-hub-cold-email-deliverability?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cmj-hub-cold-email-deliverability/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Встраиваемая карточка
<iframe src="https://skillstore.io/embed/skills/cmj-hub-cold-email-deliverability.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
cmj-hub. (2026). cold-email-deliverability security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/cmj-hub-cold-email-deliverability/audits/1Цитата BibTeX
@techreport{cmj-hub-cmj-hub-cold-email-deliverability-2026,
author = {cmj-hub},
title = {cold-email-deliverability security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/cmj-hub-cold-email-deliverability/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: "cold-email-deliverability security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "cmj-hub"
date-released: "2026-10-03"
url: "https://skillstore.io/skills/cmj-hub-cold-email-deliverability/audits/1"
identifiers:
- type: other
value: "skillstore:cmj-hub-cold-email-deliverability:audit:1"
description: "Skillstore immutable audit report identifier"
Оценка Skillstore
Почему такая оценка Достоверность доказательств: СреднийЧто вы можете построить
Review a First Outreach Campaign
Check domain authentication, mailbox age, and sending volume before starting outreach.
Prepare a Domain Remediation Plan
Review DNS and reputation findings and prioritize the fixes that affect campaign readiness.
Standardize Client Readiness Reviews
Apply the same 15-point checklist across client sending domains and record unresolved blockers.
Попробуйте эти промпты
Check deliverability for [sending_domain]. Ask for missing sending details and explain which checks require manual verification.
Review SPF, DKIM, and DMARC for [sending_domain] using provider [inbox_provider] and selector [selector]. Report observed evidence and prioritize authentication failures.
Review [sending_domain] for [from_address]. Provider: [provider]; mailbox age: [days]; daily volume: [volume]; reply ratio: [percent]. Include reputation and warm-up checks.
Run the 15-point review for [sending_domain] using [sending_details]. Show evidence, unavailable checks, score, and fix order. Keep launch blocked until blocker checks pass.
Лучшие практики
- Provide the sending domain, provider, DKIM selector, sending IP, mailbox age, volume, and recent reply ratio when available.
- Record observed evidence and keep unavailable checks unverified instead of treating them as passes.
- Resolve authentication failures and blacklist hits before sending, regardless of the numerical score.
Избегать
- Treating a high checklist score as proof of inbox placement or permission to ignore blockers.
- Providing API keys or mailbox credentials when public lookups and nonsecret sending details are sufficient.
- Applying DNS changes or increasing sending volume without verifying findings and current provider requirements.