# Cold Email Sequence > Use to draft a 4-touch cold email sequence with behavior-based branching. Each touch has a different angle (pain, proof, peer, parting). Output is paste-ready for any sequencer (Apollo, Outreach, Smartlead). Drafts only; never sends. - Skill: `shyamw-cloud/cold-email-sequence` (Agent Skill) - Install (CLI): `npx skillmds@latest add shyamw-cloud/cold-email-sequence` - Raw SKILL.md: https://api.skillmd.com/api/skills/shyamw-cloud/cold-email-sequence/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Productivity - Author: shyamw-cloud (https://skillmd.com/u/shyamw-cloud) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/shyamw-cloud/cold-email-sequence --- # cold-email-sequence A working cold sequence is **four touches over two weeks**, each with a different angle. If they reply at any point, the sequence stops. If they open but don't reply, branch to a softer angle. If they don't open, change the subject line and angle entirely. ## Inputs to gather - **ICP / persona** — who is this targeting? (Role, company shape, trigger.) - **Offer** — one sentence on what we sell and the outcome we deliver. - **Proof point** — one customer quote, case study, or metric we can cite. - **Personalization variables** — `{{first_name}}`, `{{company}}`, `{{recent_event}}`, etc. - **CTA preference** — meeting, reply with yes/no, content asset? ## Sequence shape | Touch | Day | Angle | Subject line shape | Length | |---|---|---|---|---| | 1 | Day 0 | **Pain** — name their problem precisely | Question or fragment | ≤ 90 words | | 2 | Day 3 | **Proof** — one peer's outcome | "How {{peer}} did X" | ≤ 90 words | | 3 | Day 7 | **Peer / pattern** — observation about their segment | Insight | ≤ 110 words | | 4 | Day 14 | **Parting** — "closing the loop" | "should I close the loop?" | ≤ 50 words | Branching: - **Replied** → stop sequence, hand to AE. - **Opened ≥ 2x, no reply** → on Touch 3, switch to a question-only email (no pitch). - **No opens** → on Touch 2, swap subject style (fragment → question or vice versa). ## Hard rules - Subject line: ≤ 6 words, lowercase unless proper noun. - Body opens with a sentence about *them*, not about us. - One link maximum per email. Track it. - One CTA per email. Either a meeting time or a yes/no question. - No `{{first_name}}` in the first sentence — too obvious. - No "hope this finds you well", "quick question", "just checking in", "circling back." ## Output format ``` ## Touch 1 — Day 0 — Pain Subject: Preview: --- CTA: P.S. Why this works: ``` Repeat for Touches 2-4. End with: ``` ## Branching logic - Replied → stop, route to AE - Opened 2+ no reply → on Touch 3 swap to - No opens after Touch 1 → on Touch 2 swap subject to ## Variables to fill - {{first_name}} - {{company}} - {{recent_event}} ← most likely to be empty; populate from research before send ```