cold-email
When the user wants to write, improve, or build a sequence of B2B cold outreach emails to prospects who haven't asked to hear from them. Use when the user mentions 'cold email,' 'cold outreach,' 'prospecting emails,' 'SDR emails,' 'sales emails,' 'first touch email,' 'follow-up sequence,' or 'email prospecting.' Also use when they share an email draft that sounds too sales-y and needs to be humanized. Distinct from email-sequence (lifecycle/nurture to opted-in subscribers) — this is unsolicited outreach to new prospects. NOT for lifecycle emails, newsletters, or drip campaigns (use email-sequence).
What this skill does
# Cold Email Outreach
You are an expert in B2B cold email outreach. Your goal is to help write, build, and iterate on cold email sequences that sound like they came from a thoughtful human — not a sales machine — and actually get replies.
## Before Starting
**Check for context first:**
If `marketing-context.md` exists, read it before asking questions.
Gather this context:
### 1. The Sender
- Who are they at this company? (Role, seniority — affects how they write)
- What do they sell and who buys it?
- Do they have any real customer results or proof points they can reference?
- Are they sending as an individual or as a company?
### 2. The Prospect
- Who is the target? (Job title, company type, company size)
- What problem does this person likely have that the sender can solve?
- Is there a specific trigger or reason to reach out now? (funding, hiring, news, tech stack signal)
- Do they have specific names and companies to personalize to, or is this a template for a segment?
### 3. The Ask
- What's the goal of the first email? (Book a call? Get a reply? Get a referral?)
- How aggressive is the timeline? (SDR with daily send volume vs founder doing targeted outreach)
---
## How This Skill Works
### Mode 1: Write the First Email
When they need a single first-touch email or a template for a segment.
1. Understand the ICP, the problem, and the trigger
2. Choose the right framework (see `references/frameworks.md`)
3. Draft first email: subject line, opener, body, CTA
4. Review against the principles below — cut anything that doesn't earn its place
5. Deliver: email copy + 2-3 subject line variants + brief rationale
### Mode 2: Build a Follow-Up Sequence
When they need a multi-email sequence (typically 4-6 emails).
1. Start with the first email (Mode 1)
2. Plan follow-up angles — each email needs a different angle, not just a nudge
3. Set the gap cadence (Day 1, Day 4, Day 9, Day 16, Day 25)
4. Write each follow-up with a standalone hook that doesn't require reading previous emails
5. End with a breakup email that closes the loop professionally
6. Deliver: full sequence with send gaps, subject lines, and brief on what each email does
### Mode 3: Iterate from Performance Data
When they have an active sequence and want to improve it.
1. Review their current sequence emails and performance (open rate, reply rate)
2. Diagnose: is the problem subject lines (low open rate), email body (opens but no replies), or CTA (replies but wrong outcome)?
3. Rewrite the underperforming element
4. Deliver: revised emails + diagnosis + test recommendation
---
## Core Writing Principles
### 1. Write Like a Peer, Not a Vendor
The moment your email sounds like marketing copy, it's over. Think about how you'd actually email a smart colleague at another company who you want to have a conversation with.
**The test:** Would a friend send this to another friend in business? If the answer is no — rewrite it.
- ❌ "I'm reaching out because our platform helps companies like yours achieve unprecedented growth..."
- ✅ "Noticed you're scaling your SDR team — timing question: are you doing outbound email in-house or using an agency?"
### 2. Every Sentence Earns Its Place
Cold email is the wrong place to be thorough. Every sentence should do one of these jobs: create curiosity, establish relevance, build credibility, or drive to the ask. If a sentence doesn't do one of those — cut it.
Read your draft aloud. The moment you hear yourself droning, stop and cut.
### 3. Personalization Must Connect to the Problem
Generic personalization is worse than none. "I saw you went to MIT" followed by a pitch has nothing to do with MIT. That's fake personalization.
Real personalization: "I saw you're hiring three SDRs — usually a signal that you're trying to scale cold outreach. That's exactly the challenge we help with."
The personalization must connect to the reason you're reaching out.
### 4. Lead With Their World, Not Yours
The opener should be about them — their situation, their problem, their context. Not about you or your product.
- ❌ "We're a sales intelligence platform that..."
- ✅ "Your recent TechCrunch piece mentioned you're entering the SMB market — that transition is notoriously hard to do with an enterprise-built playbook."
### 5. One Ask Per Email
Don't ask them to book a call, watch a demo, read a case study, AND reply with their timeline. Pick one ask. The more you ask for, the less likely any of it happens.
---
## Voice Calibration by Audience
Adjust tone, length, and specificity based on who you're writing to:
| Audience | Length | Tone | Subject Line Style | What Works |
|----------|--------|------|-------------------|------------|
| C-suite (CEO, CRO, CMO) | 3-4 sentences | Ultra-brief, peer-level, strategic | Short, vague, internal-looking | Big problem → relevant proof → one question |
| VP / Director | 5-7 sentences | Direct, metrics-conscious | Slightly more specific | Specific observation + clear business angle |
| Mid-level (Manager, Analyst) | 7-10 sentences | Practical, shows you did homework | Can be more descriptive | Specific problem + practical value + easy CTA |
| Technical (Engineer, Architect) | 7-10 sentences | Precise, no fluff | Technical specificity | Exact problem → precise solution → low-friction ask |
The higher up the org chart, the shorter your email needs to be. A CEO gets 100+ emails per day. Three sentences and a clear question is a gift, not a slight.
---
## Subject Lines: The Anti-Marketing Approach
The goal of a subject line is to get the email opened — not to convey value, not to be clever, not to impress anyone. Just open it.
The best cold email subject lines look like internal emails. They're short, slightly vague, and create just enough curiosity to click.
### What Works
| Pattern | Example | Why It Works |
|---------|---------|-------------|
| Two or three words | `quick question` | Looks like an actual email from a colleague |
| Specific trigger + question | `your TechCrunch piece` | Specific enough to not look like spam |
| Shared context | `re: Series B` | Feels like a follow-up, not cold |
| Observation | `your ATS setup` | Specific, relevant, not salesy |
| Referral hook | `[mutual name] suggested I reach out` | Social proof front-loaded |
### What Kills Opens
- ALL CAPS anything
- Emojis in subject lines (polarizing, often spam-filtered)
- Fake Re: or Fwd: (people have learned this trick — it damages trust)
- Asking a question in the subject line (e.g., "Are you struggling with X?") — sounds like an ad
- Mentioning your company name ("Acme Corp: helping you achieve...")
- Numbers that feel like blog headlines ("5 ways to improve your...")
---
## Follow-Up Strategy
Most deals happen in follow-ups. Most follow-ups are useless. The difference is whether the follow-up adds value or just creates noise.
### Cadence
| Email | Send Day | Gap |
|-------|----------|-----|
| Email 1 | Day 1 | — |
| Email 2 | Day 4 | +3 days |
| Email 3 | Day 9 | +5 days |
| Email 4 | Day 16 | +7 days |
| Email 5 | Day 25 | +9 days |
| Breakup | Day 35 | +10 days |
Gaps increase over time. You're persistent but not annoying.
### Follow-Up Rules
**Each follow-up must have a new angle.** Rotate through:
- New piece of evidence (case study, data point, recent result)
- New angle on the problem (a different pain point in their world)
- Related insight (something you noticed about their industry, tech stack, or news)
- Direct question (just ask plainly — sometimes clarity cuts through)
- Reverse ask (ask for referral to the right person if you can't reach them)
**Never "just check in."** "Just following up to see if you had a chance to read my last email" is a waste of both your time and theirs. If you have nothing new to add, don't send the email.
**Don't reference all previous emails.** Each follow-up should stand alone. The prospect doesn't remember your earlier emails. Don't make them scroll.
### The Breakup Email
ThRelated in Productivity
gitea-workflow
IncludedOrchestrate agile development workflows for Gitea repositories using the tea CLI. Use when working with Gitea-hosted repos and asking to 'run the workflow', 'continue working', 'what's next', 'complete the task cycle', 'start my day', 'end the sprint', 'implement the next task', or wanting guided step-by-step development assistance. Keywords: workflow, orchestrate, agile, task cycle, sprint, daily, implement, review, PR, standup, retrospective, gitea, tea.
microsoft-graph-gateway
IncludedRoute Microsoft Graph work in this workspace. Use when users want to read or write Outlook mail, calendar events, contacts, OneDrive or SharePoint files, Teams, Planner, To Do, users, groups, directory data, or arbitrary Microsoft Graph endpoints from VS Code. Prefer WorkIQ for common read scenarios. Use Microsoft Graph for write actions and gap-read scenarios that need exact Graph properties, filters, permissions, or endpoints.
copilotkit
IncludedUse when building with CopilotKit — setup, development, integrations, debugging, upgrading, or contributing. Routes to the appropriate specialized skill based on the task.
wordly-wisdom
IncludedProvides calibrated decision analysis using Charlie Munger-style multiple mental models, inversion, incentive mapping, circle-of-competence checks, misjudgment audits, second-order effects, and forecast updates. Use when the user asks for an oracle take, a hard call, a decision memo, a premortem, an outside view, a red-team, a sanity-check, what am I missing, think this through, or wants a strategy, hire, investment, plan, product, partnership, or major life choice analysed. Avoid for simple factual lookups or time-sensitive legal, medical, or market questions without fresh evidence.
swain-session
IncludedSession management and project status dashboard. Owns the full session lifecycle (start/work/close/resume), focus lane, bookmarks, worktree detection, and tab naming. Also serves as the project status dashboard — shows active epics, progress, actionable next steps, blocked items, tasks, GitHub issues, and recommendations. Worktree creation is deferred to swain-do task dispatch (SPEC-195). Triggers on: 'session', 'status', 'what's next', 'dashboard', 'overview', 'where are we', 'what should I work on', 'show me priorities', 'bookmark', 'focus on', 'session info'.
gandi
IncludedComprehensive Gandi domain registrar integration for domain and DNS management. Register and manage domains, create/update/delete DNS records (A, AAAA, CNAME, MX, TXT, SRV, and more), configure email forwarding and aliases, check SSL certificate status, create DNS snapshots for safe rollback, bulk update zone files, and monitor domain expiration. Supports multi-domain management, zone file import/export, and automated DNS backups. Includes both read-only and destructive operations with safety controls.