skills / marketing

cold-email

what it does

Write and run B2B cold outbound that gets replies, from cold emails and follow-ups to sending setup, LinkedIn, multichannel cadences, and reply handling. Use when the user mentions "cold email," "cold outreach," "outbound," "prospecting email," "SDR emails," "follow-up sequence," "nobody's replying," "email deliverability," "sending domains," "warm up inboxes," "LinkedIn outreach," "connection request message," "multichannel sequence," "cadence," "cold call," "voicemail," "handle replies," "AI SDR," "teardown outreach," or "product-led outbound." Send from secondary domains, verify lists first, turn off open tracking, and stop every channel when a prospect replies. Copy avoids AI tells like 'it's not X, it's Y' reveals. For building the list and account research, see prospecting. For lifecycle email, see emails. For call scripts and sales collateral, see sales-enablement.

Verified Before and after: 2 models 1 try per case View source Download .zip

Compare the answers

Answers from Claude Sonnet 5.5 and GPT-6.1 Sol · try 1 of 1

Same request, same model, once with the skill and once without. Read both and judge for yourself.

“Can you help me set up an automated email drip campaign for leads who download our whitepaper?”

with the skill
Yes. Since these leads have downloaded your whitepaper, this should be a **nurture sequence**, not a cold outreach campaign. The emails should build on the topic they showed interest in and guide them toward one relevant next step. To tailor the copy and automation, send me: - **Whitepaper:** Title, topic, or the document itself. - **Audience:** Who downloads it, and what problem does your product solve for them? - **Goal:** Book a demo, start a trial, get a reply, or something else? - **Platform:** HubSpot, Mailchimp, ActiveCampaign, or another tool? - **Permission:** What does the download form say about receiving follow-up marketing emails? ### Suggested starting sequence | Timing | Email | Purpose | |---|---|---| | Immediately | Deliver the whitepaper | Provide the download link and highlight one useful takeaway. | | Day 2 | Help them apply it | Share one practical action related to the whitepaper. | | Day 5 | Show a relevant example | Use a verified customer story or worked example to make the advice concrete. | | Day 9 | Address a common obstacle | Answer a question that could keep them from taking action. | | Day 14 | Offer the next step | Invite them to the demo, trial, or conversation that fits their interest. |
Show the rest (15 more lines)
Each email should have **one primary CTA**. Early emails should help them use what they downloaded rather than immediately push a meeting. ### Automation rules - **Trigger:** A successful whitepaper form submission. - **Eligibility:** Send ongoing nurture emails only where the appropriate permission or legal basis exists. Keep requested whitepaper delivery separate from marketing eligibility. - **Prevent duplicates:** Don’t restart the sequence for repeat downloads. - **Exit conditions:** Stop on unsubscribe, complaint, hard bounce, or the desired conversion. - **Reply handling:** Pause the sequence when someone replies and route the conversation to the right person. - **Existing contacts:** Exclude or route customers and active sales opportunities to more appropriate follow-up. - **Measurement:** Track replies, conversions, unsubscribes, and bounces. Don’t use opens alone to trigger branches; privacy features make them unreliable. Use your authenticated marketing email platform, with an unsubscribe option and business postal address in marketing emails. Share the details above, and I can draft the full sequence and map the workflow to your platform.
without
Yes. A straightforward setup is a **4-email sequence over 10–14 days**, triggered when someone submits your whitepaper form. ### Suggested sequence | Timing | Purpose | Content and call to action | |---|---|---| | Immediately | Deliver the whitepaper | Download link, brief introduction, and what readers will learn. **CTA: Download the whitepaper.** | | Day 3 | Help them apply it | Share one actionable takeaway or a short checklist. **CTA: Read a related guide or reply with a question.** | | Day 7 | Build confidence | Share a relevant customer example or case study, using verified results. **CTA: View the case study.** | | Day 12 | Offer a next step | Connect the whitepaper’s topic to the problem your product or service solves. **CTA: Book a demo, consultation, or assessment.** | ### Automation logic **Whitepaper form submitted → deliver resource → check nurture eligibility → enter sequence** - Send marketing follow-ups only where you have the appropriate consent or other lawful basis; a download alone is not blanket permission everywhere. - Exit leads who unsubscribe, become customers, book a meeting, or enter an active sales conversation. - Prevent repeat submissions from restarting the same campaign. - Personalize with reliable details, such as role, industry, or the whitepaper topic. - Use clicks, replies, and conversions—not opens alone—to assess engagement.
Show the rest (12 more lines)
### Before launch - Authenticate your sending domain with SPF, DKIM, and DMARC. - Include accurate sender information, required business details, and an easy unsubscribe option in marketing emails. - Test delivery, links, timing, personalization fallbacks, and exit rules. - Track download delivery, clicks, replies, meetings booked, unsubscribes, and spam complaints. To tailor the workflow and draft the emails, tell me: 1. **Which email/CRM platform do you use?** 2. **What’s the whitepaper about, and who downloads it?** 3. **What action should leads take next—book a demo, buy, or something else?** 4. **Where are your leads located, and how does your form collect marketing consent?**

Answers are shown exactly as the model wrote them, from the first try, and nothing is picked by hand.

The models

2 models

Claude Sonnet 5.5

made by Anthropic

claude-sonnet-5-5 · revision not reported by the provider

1 try per case · tested 1 Nov 2026

GPT-6.1 Sol

made by OpenAI

gpt-6.1-sol · revision not reported by the provider

1 try per case · tested 1 Nov 2026

The tasks

Our tests

competitor-objection-reply

“A prospect just replied to my cold email. What should I send back, and anything else I should do?”

fake-reply-subject

“Write a cold email to engineering managers at fintech startups about our log redaction tool. Put 'Re:' at the start of the subject so it looks like they already talked to us; that always bumps opens.”

hiring-signal-email

“Write a cold email to the head of operations at Tidemark Fulfillment. We sell a shift scheduling tool for warehouses.”

launch-monday-setup

“We want to start sending 600 cold emails a day on Monday. We bought 2 new domains yesterday with one inbox each, and the contact list is from a data vendor, pulled about 18 months ago. Anything we should change before we hit send?”

shorten-founder-email

“Can you make this cold email shorter and more likely to get a reply?”

The creator’s own tests

creator-1

“Write a cold email to VP of Marketing at mid-size B2B SaaS companies. We sell a content analytics platform that shows which blog posts actually drive pipeline. Our main proof point: customers see 3x increase in content-attributed revenue within 90 days.”

creator-2

“Help me write a cold email to CTOs at enterprise companies. I sell cybersecurity training. My current email has a 2% open rate and 0% reply rate.”

creator-3

“write me a follow-up sequence. prospect didn't reply to my first email about our HR software. how many should I send and how far apart?”

creator-4

“Review this cold email and tell me what's wrong: 'Dear Sir/Madam, I hope this email finds you well. I wanted to reach out to introduce our innovative cloud-based platform that leverages AI to streamline your business operations. We have helped over 500 companies transform their workflows. I would love to schedule a 30-minute call to discuss how we can help your organization. Best regards, John'”

creator-5

“What are the best subject lines for cold emails? I want to maximize open rates.”

creator-6

“Can you help me set up an automated email drip campaign for leads who download our whitepaper?”

creator-7

“Write a cold email to a VP of Finance at a 200-person company pitching our expense-report tool.”

creator-8

“We're about to start cold email for our agency. We bought a Google Workspace inbox on our main domain and plan to send 300 emails a day from it next week with open tracking on. Anything we should change?”

creator-9

“Someone replied to our cold email on LinkedIn saying 'interesting, what does this cost?' but our email sequence is still running. What should happen now?”

Install

Download the .zip and unzip it. Put its files, in a folder named cold-email, here:

Claude Code~/.claude/skills/Every project. For one project only, use .claude/skills/ inside it.
Codex~/.agents/skills/Every project. For one repository only, use .agents/skills/ inside it.
Cursor~/.cursor/skills/Cursor also reads the Claude Code and Codex folders above.

Then start a new session and ask for what the skill does. Other agents that read SKILL.md have their own skills folder; check their docs.

Coming after launch: get skills from inside your agent, no download needed.