[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KBJPK0BAYNQCMP31643KHH":3,"skill-same:01M6KBJPK0BAYNQCMP31643KHH":103},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":64,"repositoryHtmlUrl":65,"repositoryHomepageUrl":6,"ownerHtmlUrl":66,"ownerBlogUrl":67,"ownerDescription":6,"updatedAt":68,"install":69,"resources":82},"01M6KBJPK0BAYNQCMP31643KHH","cold-email",null,"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\u002Fnurture to opted-in subscribers) — this is unsolicited outreach to new prospects. NOT for lifecycle emails, newsletters, or drip campaigns (use email-sequence).","afaizalam2003\u002FMaster-claude-skill","afaizalam2003","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F222019359?v=4","01M6K8F2XNT0HKBPF00JQ78SV3","Faiz Alam","01M6K8F31EBXAPER0EG8R9HTR5",3,"MIT","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Fcold-email\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"email","cold","cold email","drip campaigns","sequence","for","follow-up","touch","emails","campaigns","b2b","cold outreach","up","use","sales","write","marketing","improve","lifecycle","prospecting","2026-11-10 10:12:30",false,"---\nname: \"cold-email\"\ndescription: \"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\u002Fnurture to opted-in subscribers) — this is unsolicited outreach to new prospects. NOT for lifecycle emails, newsletters, or drip campaigns (use email-sequence).\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Md Faiz Alam\n  category: marketing\n  updated: 2026-03-06\n---\n\n# Cold Email Outreach\n\nYou 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.\n\n## Before Starting\n\n**Check for context first:**\nIf `marketing-context.md` exists, read it before asking questions.\n\nGather this context:\n\n### 1. The Sender\n- Who are they at this company? (Role, seniority — affects how they write)\n- What do they sell and who buys it?\n- Do they have any real customer results or proof points they can reference?\n- Are they sending as an individual or as a company?\n\n### 2. The Prospect\n- Who is the target? (Job title, company type, company size)\n- What problem does this person likely have that the sender can solve?\n- Is there a specific trigger or reason to reach out now? (funding, hiring, news, tech stack signal)\n- Do they have specific names and companies to personalize to, or is this a template for a segment?\n\n### 3. The Ask\n- What's the goal of the first email? (Book a call? Get a reply? Get a referral?)\n- How aggressive is the timeline? (SDR with daily send volume vs founder doing targeted outreach)\n\n---\n\n## How This Skill Works\n\n### Mode 1: Write the First Email\nWhen they need a single first-touch email or a template for a segment.\n\n1. Understand the ICP, the problem, and the trigger\n2. Choose the right framework (see `references\u002Fframeworks.md`)\n3. Draft first email: subject line, opener, body, CTA\n4. Review against the principles below — cut anything that doesn't earn its place\n5. Deliver: email copy + 2-3 subject line variants + brief rationale\n\n### Mode 2: Build a Follow-Up Sequence\nWhen they need a multi-email sequence (typically 4-6 emails).\n\n1. Start with the first email (Mode 1)\n2. Plan follow-up angles — each email needs a different angle, not just a nudge\n3. Set the gap cadence (Day 1, Day 4, Day 9, Day 16, Day 25)\n4. Write each follow-up with a standalone hook that doesn't require reading previous emails\n5. End with a breakup email that closes the loop professionally\n6. Deliver: full sequence with send gaps, subject lines, and brief on what each email does\n\n### Mode 3: Iterate from Performance Data\nWhen they have an active sequence and want to improve it.\n\n1. Review their current sequence emails and performance (open rate, reply rate)\n2. Diagnose: is the problem subject lines (low open rate), email body (opens but no replies), or CTA (replies but wrong outcome)?\n3. Rewrite the underperforming element\n4. Deliver: revised emails + diagnosis + test recommendation\n\n---\n\n## Core Writing Principles\n\n### 1. Write Like a Peer, Not a Vendor\n\nThe 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.\n\n**The test:** Would a friend send this to another friend in business? If the answer is no — rewrite it.\n\n- ❌ \"I'm reaching out because our platform helps companies like yours achieve unprecedented growth...\"\n- ✅ \"Noticed you're scaling your SDR team — timing question: are you doing outbound email in-house or using an agency?\"\n\n### 2. Every Sentence Earns Its Place\n\nCold 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.\n\nRead your draft aloud. The moment you hear yourself droning, stop and cut.\n\n### 3. Personalization Must Connect to the Problem\n\nGeneric 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.\n\nReal 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.\"\n\nThe personalization must connect to the reason you're reaching out.\n\n### 4. Lead With Their World, Not Yours\n\nThe opener should be about them — their situation, their problem, their context. Not about you or your product.\n\n- ❌ \"We're a sales intelligence platform that...\"\n- ✅ \"Your recent TechCrunch piece mentioned you're entering the SMB market — that transition is notoriously hard to do with an enterprise-built playbook.\"\n\n### 5. One Ask Per Email\n\nDon'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.\n\n---\n\n## Voice Calibration by Audience\n\nAdjust tone, length, and specificity based on who you're writing to:\n\n| Audience | Length | Tone | Subject Line Style | What Works |\n|----------|--------|------|-------------------|------------|\n| C-suite (CEO, CRO, CMO) | 3-4 sentences | Ultra-brief, peer-level, strategic | Short, vague, internal-looking | Big problem → relevant proof → one question |\n| VP \u002F Director | 5-7 sentences | Direct, metrics-conscious | Slightly more specific | Specific observation + clear business angle |\n| Mid-level (Manager, Analyst) | 7-10 sentences | Practical, shows you did homework | Can be more descriptive | Specific problem + practical value + easy CTA |\n| Technical (Engineer, Architect) | 7-10 sentences | Precise, no fluff | Technical specificity | Exact problem → precise solution → low-friction ask |\n\nThe 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.\n\n---\n\n## Subject Lines: The Anti-Marketing Approach\n\nThe 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.\n\nThe best cold email subject lines look like internal emails. They're short, slightly vague, and create just enough curiosity to click.\n\n### What Works\n\n| Pattern | Example | Why It Works |\n|---------|---------|-------------|\n| Two or three words | `quick question` | Looks like an actual email from a colleague |\n| Specific trigger + question | `your TechCrunch piece` | Specific enough to not look like spam |\n| Shared context | `re: Series B` | Feels like a follow-up, not cold |\n| Observation | `your ATS setup` | Specific, relevant, not salesy |\n| Referral hook | `[mutual name] suggested I reach out` | Social proof front-loaded |\n\n### What Kills Opens\n\n- ALL CAPS anything\n- Emojis in subject lines (polarizing, often spam-filtered)\n- Fake Re: or Fwd: (people have learned this trick — it damages trust)\n- Asking a question in the subject line (e.g., \"Are you struggling with X?\") — sounds like an ad\n- Mentioning your company name (\"Acme Corp: helping you achieve...\")\n- Numbers that feel like blog headlines (\"5 ways to improve your...\")\n\n---\n\n## Follow-Up Strategy\n\nMost deals happen in follow-ups. Most follow-ups are useless. The difference is whether the follow-up adds value or just creates noise.\n\n### Cadence\n\n| Email | Send Day | Gap |\n|-------|----------|-----|\n| Email 1 | Day 1 | — |\n| Email 2 | Day 4 | +3 days |\n| Email 3 | Day 9 | +5 days |\n| Email 4 | Day 16 | +7 days |\n| Email 5 | Day 25 | +9 days |\n| Breakup | Day 35 | +10 days |\n\nGaps increase over time. You're persistent but not annoying.\n\n### Follow-Up Rules\n\n**Each follow-up must have a new angle.** Rotate through:\n- New piece of evidence (case study, data point, recent result)\n- New angle on the problem (a different pain point in their world)\n- Related insight (something you noticed about their industry, tech stack, or news)\n- Direct question (just ask plainly — sometimes clarity cuts through)\n- Reverse ask (ask for referral to the right person if you can't reach them)\n\n**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.\n\n**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.\n\n### The Breakup Email\n\nThe last email in a sequence should close the loop professionally. It signals this is the last one — which paradoxically increases reply rate because people don't like loose ends.\n\nExample breakup:\n> \"I'll stop cluttering your inbox after this one. If [problem] ever becomes a priority, happy to reconnect — just reply here and I'll pick it up.\n>\n> If there's someone else at [Company] I should speak with, a name would go a long way.\n>\n> Either way — good luck with [whatever's relevant].\"\n\nSee `references\u002Ffollow-up-playbook.md` for full cadence templates and angle rotation guide.\n\n---\n\n## What to Avoid\n\nThese are not suggestions — they're patterns that mark you as a non-human and kill reply rates:\n\n| ❌ Avoid | Why It Fails |\n|----------|-------------|\n| \"I hope this email finds you well\" | Instant tell that this is templated. Cut it. |\n| \"I wanted to reach out because...\" | 3-word delay before actually saying anything |\n| Feature dump in email 1 | Nobody cares about features when they don't trust you yet |\n| HTML templates with logos and colors | Looks like marketing, gets spam-filtered |\n| Fake Re:\u002FFwd: subject lines | Feels deceptive — kills trust before the first word |\n| \"Just checking in\" follow-ups | Adds no value, removes credibility |\n| Opening with \"My name is X and I work at Y\" | They can see your name. Start with something interesting. |\n| Social proof that doesn't connect to their problem | \"We work with 500 companies\" means nothing without context |\n| Long-form case study in email 1 | Save it for follow-up when they've shown interest |\n| Passive CTAs (\"Let me know if you're interested\") | Weak. Ask a direct question or propose a specific next step. |\n\n---\n\n## Deliverability Basics\n\nA great email sent from a flagged domain never lands. Basics you need to have in place:\n\n- **Dedicated sending domain** — don't send cold email from your primary domain. Use `mail.yourdomain.com` or `outreach.yourdomain.com`.\n- **SPF, DKIM, DMARC** — all three must be configured and passing. Use mail-tester.com to verify.\n- **Domain warmup** — new domains need 4-6 weeks of warmup (start with 20\u002Fday, ramp up over time).\n- **Plain text emails** — or minimal HTML. Heavy HTML triggers spam filters.\n- **Unsubscribe mechanism** — required legally (CAN-SPAM, GDPR). Include a simple opt-out.\n- **Sending limits** — stay under 100-200 emails\u002Fday per domain until established reputation.\n- **Bounce rate** — above 5% hurts deliverability. Verify email lists before sending.\n\nSee `references\u002Fdeliverability-guide.md` for domain warmup schedule, SPF\u002FDKIM setup, and spam trigger word list.\n\n---\n\n## Proactive Triggers\n\nSurface these without being asked:\n\n- **Email opens with \"My name is\" or \"I'm reaching out because\"** → rewrite the opener. These are dead-on-arrival openers. Flag and offer an alternative that leads with their world.\n- **First email is longer than 150 words** → almost certainly too long. Flag word count and offer to trim.\n- **No personalization beyond first name** → templated feel will hurt reply rates. Ask if there's a trigger or signal they can work with.\n- **Follow-up says \"just checking in\" or \"circling back\"** → useless follow-up. Ask what new angle or value they can bring to that touchpoint.\n- **HTML email template** → recommend plain text. Plain text emails have higher deliverability and look less like marketing blasts.\n- **CTA asks for 30-45 minute meeting in email 1** → too high-friction for cold outreach. Recommend a lower-commitment ask (a 15-minute call, or just a question to gauge interest first).\n\n---\n\n## Output Artifacts\n\n| When you ask for... | You get... |\n|---------------------|------------|\n| Write a cold email | First-touch email + 3 subject line variants + brief rationale for structure choices |\n| Build a sequence | 5-6 email sequence with send gaps, subject lines per email, and angle summary for each follow-up |\n| Critique my email | Line-by-line assessment + rewrite + explanation of each change |\n| Write follow-ups only | Follow-up emails 2-6 with unique angles per email + breakup email |\n| Analyze sequence performance | Diagnosis of where the sequence breaks (subject\u002Fbody\u002FCTA) + specific rewrite recommendations |\n\n---\n\n## Communication\n\nAll output follows the structured communication standard:\n- **Bottom line first** — answer before explanation\n- **What + Why + How** — every finding has all three\n- **Actions have owners and deadlines** — no \"we should consider\"\n- **Confidence tagging** — ? verified \u002F ? medium \u002F ? assumed\n\n---\n\n## Related Skills\n\n- **email-sequence**: For lifecycle and nurture emails to opted-in subscribers. Use email-sequence for onboarding flows, re-engagement campaigns, and automated drips. NOT for cold outreach — that's cold-email.\n- **copywriting**: For marketing page copy. Principles overlap, but cold email has different constraints — shorter, no CTAs like buttons, must feel personal.\n- **content-strategy**: For creating the content assets (case studies, guides) you reference in cold email follow-ups. Good follow-up sequences often link to content.\n- **marketing-strategy-pmm**: For positioning and ICP definition. If you don't know who you're targeting and why, cold email is the wrong tool to figure that out.\n","# Cold Email Outreach\n\nYou 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.\n\n## Before Starting\n\n**Check for context first:**\nIf `marketing-context.md` exists, read it before asking questions.\n\nGather this context:\n\n### 1. The Sender\n- Who are they at this company? (Role, seniority — affects how they write)\n- What do they sell and who buys it?\n- Do they have any real customer results or proof points they can reference?\n- Are they sending as an individual or as a company?\n\n### 2. The Prospect\n- Who is the target? (Job title, company type, company size)\n- What problem does this person likely have that the sender can solve?\n- Is there a specific trigger or reason to reach out now? (funding, hiring, news, tech stack signal)\n- Do they have specific names and companies to personalize to, or is this a template for a segment?\n\n### 3. The Ask\n- What's the goal of the first email? (Book a call? Get a reply? Get a referral?)\n- How aggressive is the timeline? (SDR with daily send volume vs founder doing targeted outreach)\n\n---\n\n## How This Skill Works\n\n### Mode 1: Write the First Email\nWhen they need a single first-touch email or a template for a segment.\n\n1. Understand the ICP, the problem, and the trigger\n2. Choose the right framework (see `references\u002Fframeworks.md`)\n3. Draft first email: subject line, opener, body, CTA\n4. Review against the principles below — cut anything that doesn't earn its place\n5. Deliver: email copy + 2-3 subject line variants + brief rationale\n\n### Mode 2: Build a Follow-Up Sequence\nWhen they need a multi-email sequence (typically 4-6 emails).\n\n1. Start with the first email (Mode 1)\n2. Plan follow-up angles — each email needs a different angle, not just a nudge\n3. Set the gap cadence (Day 1, Day 4, Day 9, Day 16, Day 25)\n4. Write each follow-up with a standalone hook that doesn't require reading previous emails\n5. End with a breakup email that closes the loop professionally\n6. Deliver: full sequence with send gaps, subject lines, and brief on what each email does\n\n### Mode 3: Iterate from Performance Data\nWhen they have an active sequence and want to improve it.\n\n1. Review their current sequence emails and performance (open rate, reply rate)\n2. Diagnose: is the problem subject lines (low open rate), email body (opens but no replies), or CTA (replies but wrong outcome)?\n3. Rewrite the underperforming element\n4. Deliver: revised emails + diagnosis + test recommendation\n\n---\n\n## Core Writing Principles\n\n### 1. Write Like a Peer, Not a Vendor\n\nThe 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.\n\n**The test:** Would a friend send this to another friend in business? If the answer is no — rewrite it.\n\n- ❌ \"I'm reaching out because our platform helps companies like yours achieve unprecedented growth...\"\n- ✅ \"Noticed you're scaling your SDR team — timing question: are you doing outbound email in-house or using an agency?\"\n\n### 2. Every Sentence Earns Its Place\n\nCold 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.\n\nRead your draft aloud. The moment you hear yourself droning, stop and cut.\n\n### 3. Personalization Must Connect to the Problem\n\nGeneric 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.\n\nReal 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.\"\n\nThe personalization must connect to the reason you're reaching out.\n\n### 4. Lead With Their World, Not Yours\n\nThe opener should be about them — their situation, their problem, their context. Not about you or your product.\n\n- ❌ \"We're a sales intelligence platform that...\"\n- ✅ \"Your recent TechCrunch piece mentioned you're entering the SMB market — that transition is notoriously hard to do with an enterprise-built playbook.\"\n\n### 5. One Ask Per Email\n\nDon'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.\n\n---\n\n## Voice Calibration by Audience\n\nAdjust tone, length, and specificity based on who you're writing to:\n\n| Audience | Length | Tone | Subject Line Style | What Works |\n|----------|--------|------|-------------------|------------|\n| C-suite (CEO, CRO, CMO) | 3-4 sentences | Ultra-brief, peer-level, strategic | Short, vague, internal-looking | Big problem → relevant proof → one question |\n| VP \u002F Director | 5-7 sentences | Direct, metrics-conscious | Slightly more specific | Specific observation + clear business angle |\n| Mid-level (Manager, Analyst) | 7-10 sentences | Practical, shows you did homework | Can be more descriptive | Specific problem + practical value + easy CTA |\n| Technical (Engineer, Architect) | 7-10 sentences | Precise, no fluff | Technical specificity | Exact problem → precise solution → low-friction ask |\n\nThe 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.\n\n---\n\n## Subject Lines: The Anti-Marketing Approach\n\nThe 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.\n\nThe best cold email subject lines look like internal emails. They're short, slightly vague, and create just enough curiosity to click.\n\n### What Works\n\n| Pattern | Example | Why It Works |\n|---------|---------|-------------|\n| Two or three words | `quick question` | Looks like an actual email from a colleague |\n| Specific trigger + question | `your TechCrunch piece` | Specific enough to not look like spam |\n| Shared context | `re: Series B` | Feels like a follow-up, not cold |\n| Observation | `your ATS setup` | Specific, relevant, not salesy |\n| Referral hook | `[mutual name] suggested I reach out` | Social proof front-loaded |\n\n### What Kills Opens\n\n- ALL CAPS anything\n- Emojis in subject lines (polarizing, often spam-filtered)\n- Fake Re: or Fwd: (people have learned this trick — it damages trust)\n- Asking a question in the subject line (e.g., \"Are you struggling with X?\") — sounds like an ad\n- Mentioning your company name (\"Acme Corp: helping you achieve...\")\n- Numbers that feel like blog headlines (\"5 ways to improve your...\")\n\n---\n\n## Follow-Up Strategy\n\nMost deals happen in follow-ups. Most follow-ups are useless. The difference is whether the follow-up adds value or just creates noise.\n\n### Cadence\n\n| Email | Send Day | Gap |\n|-------|----------|-----|\n| Email 1 | Day 1 | — |\n| Email 2 | Day 4 | +3 days |\n| Email 3 | Day 9 | +5 days |\n| Email 4 | Day 16 | +7 days |\n| Email 5 | Day 25 | +9 days |\n| Breakup | Day 35 | +10 days |\n\nGaps increase over time. You're persistent but not annoying.\n\n### Follow-Up Rules\n\n**Each follow-up must have a new angle.** Rotate through:\n- New piece of evidence (case study, data point, recent result)\n- New angle on the problem (a different pain point in their world)\n- Related insight (something you noticed about their industry, tech stack, or news)\n- Direct question (just ask plainly — sometimes clarity cuts through)\n- Reverse ask (ask for referral to the right person if you can't reach them)\n\n**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.\n\n**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.\n\n### The Breakup Email\n\nThe last email in a sequence should close the loop professionally. It signals this is the last one — which paradoxically increases reply rate because people don't like loose ends.\n\nExample breakup:\n> \"I'll stop cluttering your inbox after this one. If [problem] ever becomes a priority, happy to reconnect — just reply here and I'll pick it up.\n>\n> If there's someone else at [Company] I should speak with, a name would go a long way.\n>\n> Either way — good luck with [whatever's relevant].\"\n\nSee `references\u002Ffollow-up-playbook.md` for full cadence templates and angle rotation guide.\n\n---\n\n## What to Avoid\n\nThese are not suggestions — they're patterns that mark you as a non-human and kill reply rates:\n\n| ❌ Avoid | Why It Fails |\n|----------|-------------|\n| \"I hope this email finds you well\" | Instant tell that this is templated. Cut it. |\n| \"I wanted to reach out because...\" | 3-word delay before actually saying anything |\n| Feature dump in email 1 | Nobody cares about features when they don't trust you yet |\n| HTML templates with logos and colors | Looks like marketing, gets spam-filtered |\n| Fake Re:\u002FFwd: subject lines | Feels deceptive — kills trust before the first word |\n| \"Just checking in\" follow-ups | Adds no value, removes credibility |\n| Opening with \"My name is X and I work at Y\" | They can see your name. Start with something interesting. |\n| Social proof that doesn't connect to their problem | \"We work with 500 companies\" means nothing without context |\n| Long-form case study in email 1 | Save it for follow-up when they've shown interest |\n| Passive CTAs (\"Let me know if you're interested\") | Weak. Ask a direct question or propose a specific next step. |\n\n---\n\n## Deliverability Basics\n\nA great email sent from a flagged domain never lands. Basics you need to have in place:\n\n- **Dedicated sending domain** — don't send cold email from your primary domain. Use `mail.yourdomain.com` or `outreach.yourdomain.com`.\n- **SPF, DKIM, DMARC** — all three must be configured and passing. Use mail-tester.com to verify.\n- **Domain warmup** — new domains need 4-6 weeks of warmup (start with 20\u002Fday, ramp up over time).\n- **Plain text emails** — or minimal HTML. Heavy HTML triggers spam filters.\n- **Unsubscribe mechanism** — required legally (CAN-SPAM, GDPR). Include a simple opt-out.\n- **Sending limits** — stay under 100-200 emails\u002Fday per domain until established reputation.\n- **Bounce rate** — above 5% hurts deliverability. Verify email lists before sending.\n\nSee `references\u002Fdeliverability-guide.md` for domain warmup schedule, SPF\u002FDKIM setup, and spam trigger word list.\n\n---\n\n## Proactive Triggers\n\nSurface these without being asked:\n\n- **Email opens with \"My name is\" or \"I'm reaching out because\"** → rewrite the opener. These are dead-on-arrival openers. Flag and offer an alternative that leads with their world.\n- **First email is longer than 150 words** → almost certainly too long. Flag word count and offer to trim.\n- **No personalization beyond first name** → templated feel will hurt reply rates. Ask if there's a trigger or signal they can work with.\n- **Follow-up says \"just checking in\" or \"circling back\"** → useless follow-up. Ask what new angle or value they can bring to that touchpoint.\n- **HTML email template** → recommend plain text. Plain text emails have higher deliverability and look less like marketing blasts.\n- **CTA asks for 30-45 minute meeting in email 1** → too high-friction for cold outreach. Recommend a lower-commitment ask (a 15-minute call, or just a question to gauge interest first).\n\n---\n\n## Output Artifacts\n\n| When you ask for... | You get... |\n|---------------------|------------|\n| Write a cold email | First-touch email + 3 subject line variants + brief rationale for structure choices |\n| Build a sequence | 5-6 email sequence with send gaps, subject lines per email, and angle summary for each follow-up |\n| Critique my email | Line-by-line assessment + rewrite + explanation of each change |\n| Write follow-ups only | Follow-up emails 2-6 with unique angles per email + breakup email |\n| Analyze sequence performance | Diagnosis of where the sequence breaks (subject\u002Fbody\u002FCTA) + specific rewrite recommendations |\n\n---\n\n## Communication\n\nAll output follows the structured communication standard:\n- **Bottom line first** — answer before explanation\n- **What + Why + How** — every finding has all three\n- **Actions have owners and deadlines** — no \"we should consider\"\n- **Confidence tagging** — ? verified \u002F ? medium \u002F ? assumed\n\n---\n\n## Related Skills\n\n- **email-sequence**: For lifecycle and nurture emails to opted-in subscribers. Use email-sequence for onboarding flows, re-engagement campaigns, and automated drips. NOT for cold outreach — that's cold-email.\n- **copywriting**: For marketing page copy. Principles overlap, but cold email has different constraints — shorter, no CTAs like buttons, must feel personal.\n- **content-strategy**: For creating the content assets (case studies, guides) you reference in cold email follow-ups. Good follow-up sequences often link to content.\n- **marketing-strategy-pmm**: For positioning and ICP definition. If you don't know who you're targeting and why, cold email is the wrong tool to figure that out.\n",{"name":5,"license":15,"metadata":57,"description":7},{"author":58,"updated":59,"version":60,"category":48},"Md Faiz Alam",1772755200000,"1.0.0","main","0b48cbb0e6d5be6ff68c0f6b28bc0c65ee21c4a1","marketing-skill\u002Fcold-email",2,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill","https:\u002F\u002Fgithub.com\u002Fafaizalam2003","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fmdfaizalam2003\u002F","2026-04-01 04:35:43",{"source":8,"skillName":5,"commands":70,"prompt":80,"zipAvailable":81},[71,74,77],{"tool":72,"command":73},"npx","npx skills add afaizalam2003\u002FMaster-claude-skill --skill cold-email",{"tool":75,"command":76},"bunx","bunx skills add afaizalam2003\u002FMaster-claude-skill --skill cold-email",{"tool":78,"command":79},"pnpm","pnpm dlx skills add afaizalam2003\u002FMaster-claude-skill --skill cold-email","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Fcold-email\u002FSKILL.md",true,[83,89,93,97],{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fdeliverability-guide.md","REFERENCE","参考文档",9167,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Fcold-email\u002Freferences\u002Fdeliverability-guide.md",{"path":90,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Ffollow-up-playbook.md",9288,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Fcold-email\u002Freferences\u002Ffollow-up-playbook.md",{"path":94,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fframeworks.md",9209,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Fcold-email\u002Freferences\u002Fframeworks.md",{"path":98,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":101,"sourceHtmlUrl":102},"scripts\u002Femail_sequence_analyzer.py","SCRIPT","脚本",19644,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Fcold-email\u002Fscripts\u002Femail_sequence_analyzer.py",[104,132,156,180,210,230],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":113,"publishedAt":52},"01M6KC4E8MYR9DBAZTAXHKYMMH","soc2-compliance","Use when the user asks to prepare for SOC 2 audits, map Trust Service Criteria, build control matrices, collect audit evidence, perform gap analysis, or assess SOC 2 Type I vs Type II readiness.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fsoc2-compliance\u002FSKILL.md",[110],{"categoryNo":111,"categoryName":112,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000037","律师与法务",[114,115,116,117,118,119,120,121,45,122,123,124,125,126,127,128,129,130,131,37],"compliance","soc2","soc2 compliance","audit evidence","audit","collect","soc","analysis","evidence","trust","build","map","control","type","gap","readiness","gap analysis","assess",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":52},"01M6KC461R3GKGZ1TAYHVR1MW9","risk-management-specialist","Medical device risk management specialist implementing ISO 14971 throughout product lifecycle. Provides risk analysis, risk evaluation, risk control, and post-production information analysis. Use when user mentions risk management, ISO 14971, risk analysis, FMEA, fault tree analysis, hazard identification, risk control, risk matrix, benefit-risk analysis, residual risk, risk acceptability, or post-market risk.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Frisk-management-specialist\u002FSKILL.md",[],[139,140,141,142,143,144,145,50,121,45,146,147,148,149,150,151,152,153,154,155],"risk","risk management specialist","management","risk management","risk evaluation","product","Evaluation","risk matrix","iso","medical","iso 14971","identification","information","post-production","tree","matrix","implementing",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":52},"01M6KC3HF5ZFSSP2NZF68PEPFB","regulatory-affairs-head","Senior Regulatory Affairs Manager for HealthTech and MedTech companies. Prepares FDA 510(k), De Novo, and PMA submission packages; analyzes regulatory pathways for new medical devices; drafts responses to FDA deficiency letters and Notified Body queries; develops CE marking technical documentation under EU MDR 2017\u002F745; coordinates multi-market approval strategies across FDA, EU, Health Canada, PMDA, and NMPA; and maintains regulatory intelligence on evolving standards. Use when users need to plan or execute FDA submissions, navigate 510(k) or PMA approval processes, achieve CE marking, prepare pre-submission meeting materials, write regulatory strategy documents, respond to agency queries, or manage compliance documentation for medical device market access.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fregulatory-affairs-head\u002FSKILL.md",[],[163,164,165,166,167,168,169,47,170,45,171,172,173,174,175,176,177,178,179,37],"regulatory affairs head","regulatory","head","documents","devices","health","plan","strategy","standards","queries","manage","strategies","de","users","respond","medical devices","manager",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":192,"publishedAt":52},"01M6KC34Z8M1559EY1CXYBJB1A","quality-manager-qms-iso13485","ISO 13485 Quality Management System implementation and maintenance for medical device organizations. Provides QMS design, documentation control, internal auditing, CAPA management, and certification support. Use when working with medical device quality systems, preparing for ISO 13485 audits, managing regulatory compliance documentation, setting up corrective actions, or building audit preparation programs. Useful for quality management, audit preparation, regulatory compliance, medical device documentation, and corrective action workflows.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qms-iso13485\u002FSKILL.md",[186,189],{"categoryNo":187,"categoryName":188,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":190,"categoryName":191,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000032","设计师",[193,194,179,195,196,197,198,199,200,45,201,202,203,204,205,206,207,208,37,209],"quality manager qms iso13485","quality","design","workflows","validation","actions","certification","system","maintenance","document","systems","records","ISO 13485","organizations","corrective action","internal audit","preparation",{"skillNo":211,"name":212,"nameZh":6,"description":213,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":214,"categories":215,"keywords":217,"publishedAt":52},"01M6KC2FXHBHXYX2ZZ17Y3GDB4","quality-manager-qmr","Senior Quality Manager Responsible Person (QMR) for HealthTech and MedTech companies. Provides quality system governance, management review leadership, regulatory compliance oversight, and quality performance monitoring per ISO 13485 Clause 5.5.2.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qmr\u002FSKILL.md",[216],{"categoryNo":111,"categoryName":112,"taxonomyType":29,"taxonomyTypeDesc":30},[218,194,179,219,220,221,222,223,114,224,200,225,164,226,227,228,147,205,37,229],"quality manager qmr","review","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership","person",{"skillNo":231,"name":232,"nameZh":6,"description":233,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":234,"categories":235,"keywords":243,"publishedAt":52},"01M6KC1VRR5JTDBNZANHPS6VR6","quality-documentation-manager","Document control system management for medical device QMS. Covers document numbering, version control, change management, and 21 CFR Part 11 compliance. Use for document control procedures, change control workflow, document numbering, version management, electronic signature compliance, or regulatory documentation review.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-documentation-manager\u002FSKILL.md",[236,239,242],{"categoryNo":237,"categoryName":238,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":240,"categoryName":241,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":111,"categoryName":112,"taxonomyType":29,"taxonomyTypeDesc":30},[244,245,194,179,219,246,247,118,200,248,249,250,251,252,148,253,254,255,256,37],"documentation","quality documentation manager","workflow","change","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control","retention"]