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.

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

Source material given with the request

Her reply: "Thanks, but we already use Crewcast for this." Background: I sell Plotline, a field-service scheduling app. She's a dispatch manager at a 40-technician HVAC company. Teams usually switch to us from Crewcast when they add a second branch, because Crewcast schedules one location at a time. She's on step 2 of a 5-email automated sequence.
with the skill
## Send this (as a reply in the same thread) > Makes sense, and if it's working for you, there's no reason to change. > > The one time teams your size usually look at us is when they add a second branch, since Crewcast schedules one location at a time. Is a second location anything on your radar, or is it staying at one for the foreseeable future? > > If it's the latter, I'll leave you be. It acknowledges the objection without arguing, names the single situation where switching makes sense, and asks one easy-to-answer question with a graceful way out. It's about 65 words, so she can answer in one line. ## What else to do 1. **Pause the sequence now.** A reply on any channel stops everything. If email 3 fires tomorrow after she's answered, you'll look careless, and a follow-up on top of a "no thanks" is the kind of thing that triggers spam complaints. Do this before anything else. 2. **Send the reply yourself, not from automation.** Objection replies are "agent drafts, human sends." Send it from the same mailbox, in the same thread, preferably today. 3. **Double-check the Crewcast claim.** You're stating a fact about a competitor to someone who uses it daily. If Crewcast has added multi-location support recently, she'll know and you'll lose credibility. Verify it's still accurate, or soften it to "in our experience, teams hit a wall when they add a second branch." 4. **Log it in your CRM.** Record the reply type (objection: incumbent), the sequence and step (step 2), the date, and her competitor (Crewcast). The competitor field is useful for later retros and for a "uses Crewcast" segment. 5. **Check other channels.** If you've viewed her on LinkedIn or have a connection request pending, hold off on anything further until she responds. ## What happens next
Show the rest (8 more lines)
| Her response | What you do | |---|---| | "Yes, we're opening a second branch" | Treat it as positive. Reply fast with two specific times plus a booking link. | | "Not for a while" or gives a date | Thank her, set a reminder for that date, and keep the sequence stopped. | | "No, staying at one location" or silence | Don't resume the automated sequence. One reply, then stop. Add her to a nurture list or a reminder to revisit in 6 months. | | "Remove me" or irritation | Suppress on every channel immediately. | Resuming steps 3 to 5 after a thoughtful objection reply isn't worth it. She's told you where she stands, and the second-branch question is your one real shot with her.
without
## What to send Keep it short, don't argue with her, and ask one qualifying question: > Hi [Name], > > Thanks for the quick reply, and understood. Crewcast works well for a lot of teams. > > One question, since it's the main time we hear from Crewcast users: are you staying at one location, or is a second branch on the horizon? That's where Crewcast tends to get tight, since it schedules one location at a time. > > If not, no need to reply and I'll stay out of your inbox. > > [Your name] **Why this works:** - It accepts her answer instead of pushing back, which earns you a hearing. - The question is easy to answer and qualifies her. You don't know if she has or wants multiple branches, and that's your whole wedge. - It leads with a fact about a specific limitation, not a feature pitch. - The opt-out line lowers pressure, which makes a reply more likely.
Show the rest (10 more lines)
## What else to do 1. **Pause her in the automated sequence now.** She replied, so step 3 shouldn't fire. Sending a generic follow-up right after a personal reply looks careless. Most tools pause on reply automatically, but verify. 2. **Check for branch signals before you send.** Look at her company website, Google Maps, and LinkedIn for multiple locations, job posts in a new city, or expansion news. If she already has or is opening a second branch, make the question more direct, for example: "I saw you're opening in [city]. How are you planning to handle scheduling across both?" 3. **Log it in your CRM.** Tag her "uses Crewcast," note the branch count, and record the date. 4. **Decide the follow-up in advance.** - If she answers with a second branch coming, offer a short call or a one-page comparison on multi-location scheduling. - If she says single location, thank her, close it out, and set a reminder to check back in 6 months or when she posts about expansion. - If she doesn't reply, don't resume the sequence. Send at most one short nudge in 1-2 weeks, then stop. 5. **Save the objection.** If "we already use Crewcast" comes up often, it's worth a template and a short multi-branch comparison page you can link when someone engages.

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.