cold-outbound-sequencer

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

On user confirmation, save to `memory/email/cold-outbound-sequencer/YYYY-MM-DD-<sequence-or-icp>.md`

propose durable outbound-cadence or list-source decisions as `pending-decision` items — never write `decisions.md` directly.

Audit 0.4.1 · source sha f8baaf29ece3 · 31 Oct 2026Report an issue or request a re-scan

• Publisheraaron-he-zhu GitHub userOwner of the repository this skill is read from
• Source folderaaron-he-zhu/aaron-marketing-skills/email/deliver/cold-outbound-sequencerThe exact folder we audited
• LicenceApache-2.0As the repository states it
• Commit pinned for this verdictf8baaf29ece3A new audit runs when the source changes
• Repository statusNot archivedPushed today
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its 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…

---
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.2.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.2.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](../../../references/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 `decisions.md` directly.
- **Done when**: every sequence step has timing, a goal, and an explicit exit rule; reply-triage routes positive / objection / referral / not-now / opt-out; a per-mailbox warmup ramp and daily send throttle are specified; the CAN-SPAM required elements and any opt-in-jurisdiction flags are stated as guidance with a "confirm with counsel" caveat; and the SEND **S** read is emitted with the Cold-outbound typed profile named.
- **Primary next skill**: [consent-registry](../../../protocol/consent-registry/SKILL.md) to record the lawful basis for each list source (the S2 input), or [email-quality-auditor](../email-quality-auditor/SKILL.md) to score the program and enforce S1/S2/N1/D1.

### Handoff Summary

> Emit the standard shape from [skill-contract.md §Handoff Summary Format](../../../references/skill-contract.md).

## Data Sources

Tier 1 works from the user's own inputs: the ICP, list source, mailbox/domain setup, and target jurisdictions pasted directly, plus a manual `~~email platform` export for current per-mailbox volume, bounce rate, and spam-complaint signals when available. A keyless DNS check and DMARC aggregate (RUA) report inform the **S** authentication read; if absent, mark applicable qualified items Unknown, the run `NEEDS_INPUT`, and emit no S score from partial coverage. Keyed sending-platform APIs are optional Tier-2/3 conveniences, never a Tier-1 preconditi

Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

1. 2026-10-31
   !CAUTION B 89 / 100

   first audit · source f8baaf29ece3

Questions about cold-outbound-sequencer

• github.com/aaron-he-zhu/aaron-marketing-skills/tree/main/email/d — the audited source at commit f8baaf29ece3 and every finding aboveObserved · 31 Oct 2026

Spotted something wrong? Report a correction · Methodology