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 a cold email to the head of operations at Tidemark Fulfillment. We sell a shift scheduling tool for warehouses.”

Source material given with the request

Signal: Tidemark posted 6 night-shift picker jobs on its careers page last week. Product: Rostrly builds warehouse shift schedules from order forecasts and lets workers swap shifts from their phones. Proof: one customer, a 3-site warehouse operator, cut overtime hours 22% in the first quarter. Goal: get a reply, not necessarily a meeting yet.
with the skill
**Subject:** night shift hiring Hi [First name], Saw the six night-shift picker openings on your careers page. When nights add headcount, the schedule often gets rebuilt around guesses, and overtime covers whatever the guesses miss. Rostrly builds shifts from order forecasts and lets workers swap from their phones. A 3-site warehouse operator cut overtime hours 22% in their first quarter. Is nights schedule coverage something you're actively working on? [Your name] [Company, postal address] If this isn't relevant, reply "no" and I won't follow up. **Notes** - **The hook:** I didn't assume why they're hiring (growth vs. turnover), since the posting doesn't tell you. The "often" phrasing holds up either way. If you know which it is, say so and sharpen the opener. - **The ask:** It's a question they can answer in one line, which fits your goal of getting a reply rather than a meeting. - **Proof:** I kept it anonymous and exactly as you gave it. If you can name the customer or give the size (e.g., "about 200 pickers"), it will land harder. - **Sending:** Plain text, no link, no tracking, from a secondary domain. Verify the address before sending, and send Tuesday to Thursday mid-morning in their time zone.
Show the rest (1 more line)
- **Follow-up (day 3):** Add a new angle instead of "checking in." For example, the shift-swap side: "Most swap requests at sites like yours go through a supervisor's phone or a group chat. Rostrly moves that to workers' phones with the supervisor approving." Then a case-study or breakup email later in the sequence.
without
**Subject options:** - Night-shift picker hiring at Tidemark - Quick question on night-shift coverage - Overtime and night shifts --- **Email:** Hi [First name], I saw Tidemark posted six night-shift picker roles last week. Is that growth, turnover, or both? I ask because new night hires often get covered with overtime until they're trained, and shift swaps tend to turn into a mess of texts and calls to a supervisor. Rostrly builds warehouse schedules from order forecasts, so staffing follows expected volume. Workers can swap shifts from their phones without a supervisor in the middle. One 3-site warehouse operator we work with cut overtime hours 22% in their first quarter. Is night-shift coverage something you're actively working on, or is it already under control? A one-line answer is plenty. Thanks,
Show the rest (14 more lines)
[Name] [Title, Rostrly] --- **Why it's built this way:** - **The opener is a question about their situation.** It shows you did your homework and is easy to answer, which serves the goal of getting a reply. - **It doesn't assume the reason for the hiring.** You don't know whether it's growth or churn, so asking avoids sounding presumptuous. - **One proof point, stated plainly.** It names the customer type and the timeframe so the 22% is credible without sounding like a case-study pitch. - **The ask is a one-line reply**, not a meeting. If they respond, you can earn the call in the next message. **Optional tweaks:** - If you can verify that Tidemark runs multiple sites or has a seasonal peak coming, add one clause about it in the first line. - If you have permission to name the customer, or can give a more specific descriptor (e.g., "a 3PL" or "an e-commerce fulfillment operator"), swap it in. Specificity improves replies.

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.