菜单
Child skill for checking sender trust, cold-domain readiness, inbox caps, warmup, bounce risk, and complaint safeguards before scaled cold outreach.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Wolverine971/buildos-platform --skill cold-email-deliverability-readiness命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | Cold Email Deliverability Readiness |
| description | Child skill for checking sender trust, cold-domain readiness, inbox caps, warmup, bounce risk, and complaint safeguards before scaled cold outreach. |
| skill_type | procedure |
| altitude | task |
| activation | progressive |
| preserve_markdown | true |
| parent_id | cold_email_engagement_first_outreach |
| depth | 1 |
| legacy_paths |
| ["cold_email_outreach.deliverability","cold_email_outreach.sender_readiness"] |
| path | apps/web/src/lib/services/agentic-chat/tools/skills/definitions/cold_email_deliverability_readiness/SKILL.md |
Sender-trust and deliverability gate run before scaled cold outreach. This is a procedure skill at task
altitude, operating as a child of cold_email_engagement_first_outreach. Use this child skill when scaled
sending, cold domains, inbox health, or low opens matter. It checks sender trust, cold-domain readiness, inbox
caps, warmup, bounce risk, and complaint safeguards, then returns a pass / blocked / manual-only readiness
decision with the required fixes before scale.
550 5.7.515)Provider Requirement Matrix. Use this when volume, cold domains, sender trust, or compliance boundaries matter. Recheck official provider/regulator sources before operational send recommendations because requirements change. Provider data below is a source snapshot dated 2026-06-10.
| Area | Google/Gmail | Yahoo | Microsoft Outlook | Cold Email Decision |
|---|---|---|---|---|
| Bulk threshold | 5,000+ messages/day to personal Gmail from same primary domain triggers bulk-sender status. | Treat high volume as needing authentication, reputation, and unsubscribe hygiene. | 5,000+ messages/day to Outlook.com domains triggers SPF/DKIM/DMARC enforcement. | If near 5,000/day to any major mailbox provider, run full bulk-sender readiness before scale. |
| Enforcement mode | As of Nov 2025, Google rejects non-compliant bulk mail at the SMTP server level (not just spam-foldering). Postmaster Tools v2 reports binary Pass/Fail compliance. | Expect rejection-style enforcement to follow the Google/Microsoft direction; verify current Yahoo policy before scale. | As of 2025, Microsoft rejects unauthenticated senders at 5,000+/day with error 550 5.7.515 (Junk-foldering began 2025-05-05, then rejection). | Treat authentication/compliance failure as a hard send block — mail is rejected at the server, not merely junked. In 2026, low opens are more likely a compliance/placement failure than a copy failure. |
| SPF | Required for bulk senders. | Required/best practice. | Required for high-volume senders. | Block scale until SPF passes for every sending domain/provider. |
| DKIM | Required for bulk senders. | Required/best practice. | Required for high-volume senders. | Block scale until DKIM signs correctly. |
| DMARC | Required for bulk senders with at least p=none; From alignment matters. | Required/best practice. | Required for senders at 5,000+/day; failures rejected with 550 5.7.515 (as of 2025). | Block scale until DMARC exists and aligns with sender identity. |
| Forward/reverse DNS | Google requires valid PTR and matching forward DNS for sending IPs. | Sender infrastructure should identify sending sources clearly. | Sender reputation depends on clean authenticated infrastructure. | For shared ESPs, verify provider handles this. For owned infrastructure, block until DNS is correct. |
| TLS | Google requires TLS for bulk senders. | Use modern authenticated mail infrastructure. | Use compliant authenticated mail infrastructure. | Block if sender cannot confirm TLS support through ESP/MTA. |
| Header accuracy | Google flags malformed or deceptive headers/content. | Sender identity and message authenticity matter. | Authentication and non-deceptive identity matter. |
| Region/Source | Baseline Requirements | Cold Email Decision |
|---|---|---|
| FTC CAN-SPAM, United States | Accurate header/from info, non-deceptive subject, clear sender identity, physical postal address, clear opt-out, timely opt-out processing. | No deceptive packaging. Include required identity/opt-out mechanics for commercial email. |
| ICO PECR, UK | Electronic mail marketing rules distinguish consent, soft opt-in, corporate subscribers, and individual subscribers. | If UK/EU recipients are involved and consent basis is unclear, route to legal/compliance review or manual-only. |
| CRTC CASL, Canada | Consent, identification, and unsubscribe requirements apply; rules are stricter than U.S. CAN-SPAM. | If Canadian recipients are involved and consent basis is unclear, block scale until reviewed. |
Pass for scaled sending only when SPF, DKIM, DMARC, sender identity, unsubscribe/suppression, bounce/complaint monitoring, list source, recipient geography, and consent posture are known.
Block scale for missing authentication, spoofed or unclear identity, no opt-out/suppression path, unknown risky geography, complaint/bounce spikes, or attempts to fix low replies by increasing volume. As of Nov 2025 (Google server-level rejection) and 2025 (Microsoft 550 5.7.515), missing authentication means rejection at the server, not spam-folder placement — there is no partial-delivery middle ground at volume.
Manual-only is acceptable for one-off strategic, investor, or relationship emails where volume is negligible and the sender is real.
| Reject deceptive From, Re:, Fwd:, hidden content, spoofed identity, or unclear sender. |
| One-click unsubscribe | Required for marketing/promotional bulk mail and must be honored quickly. | Required/recommended for bulk and commercial senders. | High-volume senders should support compliant unsubscribe practices. | For scaled cold campaigns, include unsubscribe handling and suppression workflow. |
| Complaint rate | Google says keep user-reported rate below 0.1% and avoid 0.3% or higher. | Complaints affect reputation and delivery. | Reputation/complaints affect junking and blocking. | Stop or narrow if complaints rise. Do not increase volume to compensate. |