Cold Outbound Sequencer
Use when the user asks to "build a B2B cold-outbound sequence", "design reply-triage...
Install
npx skills add aaron-he-zhu/aaron-marketing-skills --skill cold-outbound-sequencer -g -a claude-code -y- Repository
- aaron-he-zhu/aaron-marketing-skills3k
- Category
- Design
- Updated
- 3d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 2,989 tokens
- Runs scripts
- No, instructions only
What it does
Use when the user asks to "build a B2B cold-outbound sequence", "design reply-triage branching", "plan a domain warmup / sending throttle", or "make my outbound CAN-SPAM / opt-in compliant"; produces a multi-step outbound sequence with reply-triage branches (positive / objection / referral / not-now / opt-out), a warmup + send-throttle ramp schedule, jurisdiction opt-in/CAN-SPAM guardrails (guidance, not legal advice), and a SEND S-dimension read. Not for B2C lifecycle flows, use email-sequence-designer; not for the consent record, use consent-registry; not for computing EQS, use email-quality-auditor. B2B冷启动外联序列/回复分流/域名预热
Cold Outbound Sequencer
Designs a B2B cold-outbound program: the multi-step sequence with reply-triage branching, the domain/mailbox warmup ramp and per-mailbox send throttle that keep it out of spam, and the CAN-SPAM / opt-in jurisdiction guardrails it must obey. It maps each step's timing and exit rule, routes every reply type to a branch, sets a ramp schedule that protects sender reputation, and states the compliance guardrails as guidance the user must confirm with counsel. It reads the SEND S (Sender-integrity / Deliverability) lever for outbound but does not compute the final EQS, does not own the consent record, and does not give legal advice.
Quick Start
Build a 5-step cold-outbound sequence for [ICP] from [sending domain/mailbox]. Here is my target list source and its jurisdiction mix: [paste/path].
Design reply-triage branching for my outbound: route positive / objection / referral / not-now / opt-out to the right next action.
I have 3 new sending mailboxes on a fresh domain. Plan a warmup ramp and a per-mailbox daily send throttle before I start the sequence.
Skill Contract
Expected output: a cold-outbound sequence map (per-step timing, goal, exit conditions), a reply-triage branch table routing every reply type, a warmup + send-throttle ramp schedule (per-mailbox daily volume by week), a jurisdiction guardrail block (CAN-SPAM required elements, opt-in-jurisdiction flags, labeled guidance, not legal advice), a SEND S-dimension read with sub-item notes and the Cold-outbound typed profile named, and the standard handoff summary.
