| name | cold-outbound-sequencer |
| slug | aaron-cold-outbound-sequencer |
| displayName | Cold Outbound Sequencer · B2B冷启动外联序列 |
| summary | B2B冷启动外联序列/回复分流/域名预热 |
| description | 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冷启动外联序列/回复分流/域名预热 |
| version | 20.1.0 |
| license | Apache-2.0 |
| compatibility | Claude Code and compatible agent-skill hosts |
| homepage | https://github.com/aaron-he-zhu/aaron-marketing-skills |
| when_to_use | Use when designing a B2B cold-outbound email program before writing the individual emails: a multi-step prospecting sequence with per-step timing and exit rules, the reply-triage branching that routes each reply type, a domain/mailbox warmup ramp and per-mailbox sending throttle to protect deliverability, and the CAN-SPAM / opt-in jurisdiction guardrails the sequence must respect. Activate when the user has a target list or ICP and wants the sequence map, the warmup/throttle schedule, and the compliance guardrails before creative or send-testing begins. Not for consented B2C lifecycle automation and not for adjudicating the consent record itself. |
| argument-hint | <sequence goal or ICP> [sending domain/mailbox setup] [target jurisdiction(s)] [list source] |
| metadata | {"author":"aaron-he-zhu","version":"20.1.0","discipline":"email","phase":"deliver","geo-relevance":"low","hermes":{"tags":["marketing","email","deliver"],"category":"email"},"openclaw":{"emoji":"✉️","homepage":"https://github.com/aaron-he-zhu/aaron-marketing-skills"}} |
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.
- Reads: the sequence goal or ICP, the sending-domain/mailbox setup (how many mailboxes, domain age, current warmup state), the target list source and its jurisdiction mix, current bounce/spam-complaint signals from a
~~email platform sending report when available, and the SEND cold-outbound profile (S=.35 E=.25 N=.15 D=.25) from send-benchmark.md.
- Writes: a user-facing sequence map + warmup/throttle schedule + guardrail block, and a reusable handoff summary to
memory/email/cold-outbound-sequencer/YYYY-MM-DD-<sequence-or-icp>.md.
- Promotes: chosen sequence structure, warmup/throttle schedule, the jurisdictions in scope, the S-dimension read, and missing exports/consent-basis gaps to
memory/hot-cache.md and memory/open-loops.md; propose durable outbound-cadence or list-source decisions as pending-decision items — never write directly.
