메뉴
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에서 현재 제공할 수 있는 파일을 다운로드하세요.
Query and manage the BuildOS Supabase database. Use for debugging data issues, checking users, LLM usage, queue jobs, schema questions, or admin database operations with safety checks.
Build animations in React Native and Expo, making the decisions in the order that determines whether they feel right — should it animate, which thread it runs on, which properties, spring or timing, how the gesture hands off, how it degrades. Writes the implementation with Reanimated, Gesture Handler, Expo Router and expo-haptics. Use when animating anything in an Expo app, adding gestures, sheets, screen transitions, press feedback or haptics, or fixing motion that stutters on device. For web animation use `animate`.
Build an animation from scratch, making the decisions in the order that determines whether it feels right — should it animate at all, what purpose, which tool, which properties, which curve and duration, how it interrupts, how it exits. Writes the implementation. Use when asked to animate something, add motion, make a component feel alive, or build a transition. For critiquing existing motion use review-animations; for auditing a whole codebase use improve-animations.
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. | 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. |
| 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.