cold-outbound-sequencer
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-qual
npx skills add aaron-he-zhu/aaron-marketing-skills --skill cold-outbound-sequencer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 ti
- Quick Start
- Skill Contract
- Handoff Summary
- Data Sources
- Instructions
- Decision Gates
- Save Results
- Reference Materials
- Next Best Skill
What does the cold-outbound-sequencer skill do?
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-qual
How do I install it?
Run `npx skills add aaron-he-zhu/aaron-marketing-skills --skill cold-outbound-sequencer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From aaron-he-zhu/aaron-marketing-skills, a repository with 2,508 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.