cold-outbound-sequencer skill | PlugMCP

cold-outbound-sequencer skill | PlugMCP

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.

Confirm the typed profile — this skill uses SEND cold-outbound (S 0.35 · E 0.25 · N 0.15 · D 0.25; send-benchmark.md §Profiles and Scoring). Outbound is deliverability-sensitive, so S is the lever this skill reads; the profile still reserves 0.25 for direct outcomes.
Design the sequence — specify each step's channel, timing (delay from prior step), the goal that step moves, and its exit rule. Every step must carry a hard exit-on-reply and a hard exit-on-opt-out; add exit-on-bounce and a natural end (do not loop). Keep total touches within a defensible window rather than mailing indefinitely — over-touching a cold list is the outbound analogue of the SEND-E over-frequency guardrail (a reputation-wasting flag, not a veto).
Route reply-triage branching — build a branch table that routes every reply type to a next action: positive (hand to sales / book), objection (rebuttal branch), referral (re-route to named contact, log the referral), not-now (defer + re-enroll date), and opt-out / unsubscribe (suppress immediately, stop all steps, hand the fact to consent-registry). No reply type may fall through to "continue the sequence."
Plan warmup + send throttle — for new domains/mailboxes set a warmup ramp (per-mailbox daily send volume by week, starting low and stepping up) before the sequence runs at full volume, and a steady-state per-mailbox daily cap. Spread volume across mailboxes rather than pushing one over its cap. This protects sending-domain/IP reputation — the S reputation and bounce/complaint sub-items. Label ramp numbers Estimated when they are category-standard rather than measured from the user's own warmup data.
State CAN-SPAM required elements — the sequence must carry: accurate From / reply-to identity, a non-deceptive subject line, a physical postal address, and a working opt-out honored promptly. State these as guardrails the creative and send-config must satisfy; the sequence design leaves room for them but this skill does not write the copy or verify the live header.
Flag opt-in-jurisdiction scope — if the target list mixes jurisdictions, flag where cold email needs a lawful basis beyond CAN-SPAM's opt-out model. The lawful basis on record is the SEND S2 input that only consent-registry holds and only email-quality-auditor adjudicates. If no accepted record exists, mark the qualified item Unknown and the run NEEDS_INPUT; do not assume Pass or infer a veto.
Read SEND S + annotate — evaluate the outbound-relevant S items (SPF/DKIM/DMARC alignment · reputation · hard-bounce · complaint · recorded consent) as Pass/Partial/Fail/Unknown/N/A and name the Cold-outbound profile. Emit a 0–100 S read only at complete applicable coverage; otherwise return NEEDS_INPUT/UNDECIDED/NOT_SCORED with no score. Do not compute EQS or fire S1/S2/N1/D1 vetoes — surface typed evidence and hand off.