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.

“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?”

with the skill
## How many and how far apart Send **4 follow-ups after your first email, 5 touches total**, with gaps that widen: | Touch | Day | Angle | |---|---|---| | Email 1 (sent) | 0 | Your original | | Follow-up 1 | 3 | New angle or insight | | Follow-up 2 | 8 | Social proof from a similar company | | Follow-up 3 | 14 | Useful resource, no pitch | | Follow-up 4 | 21-28 | Breakup | Send Tuesday to Thursday, 9-11am or 1-3pm in their time zone. Avoid Monday mornings and Friday afternoons. Roughly half of replies come from follow-ups, but returns drop after the fourth, so don't go past this. ## The sequence Brackets are placeholders. I haven't seen your first email or your proof points, so fill these with real specifics. Send each one as a reply in the same thread (a real reply, not a fake "Re:" subject). **Follow-up 1 (day 3): new angle**
Show the rest (35 more lines)
> One thing I left out. Teams your size usually lose a few hours a week to [specific pain, e.g., onboarding paperwork and time-off requests living in spreadsheets]. We've been helping [similar company] get that into one place. > > Is that on your plate right now? **Follow-up 2 (day 8): proof** > [Customer], a [size/industry] company, was dealing with [problem] before they switched. Within [timeframe] they [specific result]. > > Happy to send the short version of how they set it up if that's useful. **Follow-up 3 (day 14): resource** > I put together a one-page checklist on [topic, e.g., what to have in place before a hiring wave]. No pitch attached. > > Want me to send it over? **Follow-up 4 (day 21-28): breakup** > Looks like the timing isn't right, so I'll stop emailing. If [problem] moves up the list later, reply anytime and I'll pick it back up. > > Good luck with [their goal, e.g., the Q3 hiring push]. ## Rules to follow - **Honor the breakup.** Once sent, don't contact them again. - **Stop everything on any reply**, on any channel, including LinkedIn. - **Keep each email under about 75 words.** Each must make sense on its own, since they may not have read the others. - **No "just checking in," "bumping this," or "I never heard back."** All of these lower reply rates. - **Add a plain-text opt-out line and your postal address** to your signature, e.g., "If this isn't relevant, reply 'no' and I won't follow up." - **Turn off open and click tracking.** Judge the sequence by replies. - **Only one link in total, and none in the early emails.** Follow-up 3 offers the checklist instead of attaching it. ## What would make this stronger If you send me your first email, the prospect's role and company size, and one real customer result, I can tailor each follow-up with actual specifics. If you have a trigger signal like a hiring push, new funding, or a new HR leader, I can build the angle around that, which usually outperforms generic follow-ups.
without
# Follow-up sequence for HR software ## How many and how far apart **4 follow-ups over about 3.5 weeks** (5 emails total including your original) is a solid default for B2B cold outreach. | Email | Timing | Angle | |---|---|---| | Original | Day 1 | Intro | | Follow-up 1 | Day 4 | Quick bump + one specific value point | | Follow-up 2 | Day 9 | Social proof / case study | | Follow-up 3 | Day 16 | New angle or useful resource | | Follow-up 4 | Day 24 | Breakup email | Space them closer at the start, then wider apart. Send Tuesday through Thursday mornings when you can. If you can, mix in a LinkedIn touch or a call between emails, since multi-channel gets noticeably better response than email alone. --- ## The emails **Follow-up 1 (Day 4): short bump**
Show the rest (64 more lines)
Subject: Re: [original subject] Hi [Name], Just floating this back to the top of your inbox. In case it's useful, the main thing we help with is [specific pain, e.g., cutting onboarding time in half / eliminating manual payroll entry]. Worth a quick 15-minute chat this week? [Your name] --- **Follow-up 2 (Day 9): social proof** Subject: How [similar company] handled [HR problem] Hi [Name], I thought this might be relevant: [Customer name], a [size/industry] company, was struggling with [problem]. After switching to [Your product], they [specific result, e.g., reduced time-to-hire by 30%]. If [problem] is on your radar at [Prospect's company], I'd be happy to show you how they did it. Open to a short call [day/time]? [Your name] --- **Follow-up 3 (Day 16): new angle or resource** Subject: [Resource] for [their role/industry] Hi [Name], Not sure if the timing is right for a software conversation, so I thought I'd share something useful regardless: [link to guide, checklist, benchmark report, or compliance update relevant to their world]. If it sparks any questions about [topic], I'm happy to talk. And if someone else on your team owns HR tech decisions, I'd appreciate a pointer. [Your name] --- **Follow-up 4 (Day 24): breakup** Subject: Should I close the loop? Hi [Name], I've reached out a few times and haven't heard back, so I'll assume HR software isn't a priority right now. No hard feelings. If things change, or if I should be talking to someone else, just let me know. Otherwise, I'll stop emailing. Best, [Your name] --- ## Tips - **Keep each email under 100 words.** Shorter gets more replies. - **Don't write "just checking in."** Every email should add something new. - **Use one clear ask per email**, ideally a low-commitment one like a 15-minute call. - **Stop when they reply**, even if it's a "not now." Move them to a longer-term nurture list and check back in 2-3 months. If you tell me your prospect's role, company size, and your main selling point, I can tailor these with real specifics.

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.