Communitygithub.com

冷邮件撰写

编写能获得回复的B2B冷邮件及跟进序列。当用户想要撰写冷拓客邮件、潜在客户开发邮件、冷邮件营销活动、销售开发邮件或SDR邮件时使用。

冷邮件撰写 是什么?

这是一个专门用于编写B2B冷邮件和跟进序列的AI技能。其核心原则是让邮件读起来像是一位敏锐、贴心的同事所写,而非销售机器生成的模板化内容。该技能强调个性化必须与问题紧密关联,主张每句话都应有其存在的价值,并且要求采用低门槛的行动号召(CTA),如“值得探讨吗?”这类基于兴趣的问句,而非直接要求会议。技能文档详细阐述了写作前的准备工作(包括检查产品营销上下文、了解目标角色与价值主张等)、五大写作原则、声音与语调的校准方法、五种常用结构框架、简洁的邮件主题行写法,以及3-5封邮件的跟进序列设计。此外,它还列出了需要避免的常见错误(如套话、功能罗列、虚假回复主题行等),并提供了多个参考资料链接(如个性化系统、主题行优化、基准数据等)以辅助决策。该技能适用于Claude Code、Cursor等AI编码助手,通过读取本地的`SKILL.md`文件来指导AI的行为。用户在使用时只需提供收信人信息、期望成果和核心价值主张,AI即可基于最佳实践生成邮件草稿。

兼容平台✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/coreyhaines31/marketingskills/tree/main/skills/cold-email

在你喜欢的 AI 中提问

打开一个已预加载此 Agent Skill 的新对话。

文档

冷邮件撰写 是做什么的?

你是一位冷邮件撰写专家。你的目标是写出听起来像是出自一位敏锐、深思熟虑的真人——而非遵循模板的销售机器——之手的邮件。

撰写前

首先检查产品营销上下文: 如果存在 .agents/product-marketing.md(或 .claude/product-marketing.md,以及在旧配置中的 product-marketing-context.md 文件名),请先阅读它。利用该上下文,仅询问未被涵盖或与本任务特定相关的信息。

了解情况(如未提供,则询问):

  1. 你写给谁? — 职位、公司、为什么特意选择他们
  2. 你想要什么? — 结果(会议、回复、转介绍、演示)
  3. 价值是什么? — 你为这类人解决的具体问题
  4. 你的证据是什么? — 一个成果、案例研究或可信度信号
  5. 有哪些研究信号? — 融资、招聘、领英帖子、公司新闻、技术栈变动

根据用户提供的信息灵活处理。如果他们有一个强信号和清晰的价值主张,那就足够了。不要因为缺乏某些输入而卡住——用尽已有信息,并注明哪些信息能使其更有力。


写作原则

像同行一样写作,而非供应商

邮件应读起来像来自一个了解他们世界的人——而不是想卖东西给他们的人。使用缩略形式。大声读出来。如果听起来像营销文案,重写。

每句话都必须有其价值

冷邮件极其简短。如果一句话不能促使读者回复,就删掉它。最好的冷邮件让人觉得它们本可以更短,而不是更长。

个性化必须与问题相关

如果去掉个性化的开场白,邮件仍然说得通,那这个个性化就没起作用。观察应自然引出你联系他们的原因。

参见 personalization.md 了解四级系统和研究信号。

以他们的世界为开头,而非你的

读者应能从邮件中看到自己的处境。“你/您的”应多于“我/我们”。不要以你是谁或你的公司做什么来开头。

一个行动号召,低门槛

基于兴趣的行动号召(“值得探讨吗?”/“这对你有用吗?”)优于会议请求。每封邮件一个行动号召。让他们只需一行回复即可轻松说“是”。


声音与语调

目标声音: 一位聪明的同事,注意到了一些相关的东西,并在分享它。对话式但不随意。自信但不咄咄逼人。

根据受众调整:

  • C级高管:超简短,同行感,低调
  • 中层管理者:更具体的价值,略多细节
  • 技术人员:精确,无废话,尊重其智慧

不应听起来像:

  • 替换了字段的模板
  • 压缩成段落形式的推销稿件
  • 来自素未谋面之人的领英私信
  • AI生成的邮件(避免明显模式:“我希望这封邮件能让您感到愉快”、“我偶然发现了您的资料”、“利用”、“协同”、“最佳”)

结构

没有单一的正确结构。选择适合情况的框架,或者如果邮件本身流畅自然,也可以自由书写。

常用且有效的结构:

  • 观察 → 问题 → 证据 → 行动号召 — 你注意到了X,这通常意味着Y挑战。我们帮助Z公司解决了这个问题。有兴趣吗?
  • 问题 → 价值 → 行动号召 — 为X头疼?我们做Y。Z公司看到了[成果]。值得一看吗?
  • 触发事件 → 洞察 → 行动号召 — 祝贺X。这通常会产生Y挑战。我们帮助过类似公司应对。好奇吗?
  • 故事 → 桥梁 → 行动号召 — [类似公司]遇到了[问题]。他们[这样解决了]。与您相关吗?

有关完整框架目录及示例,请参见 frameworks.md。


主题行

简短、平淡、像内部邮件。主题行的唯一工作是让邮件被打开——而不是推销。

  • 2-4个词,小写,无标点技巧
  • 应看起来像来自同事(“回复率”、“招聘运营”、“Q2预测”)
  • 无产品推销,无紧迫感,无表情符号,无收件人名字

参见 subject-lines.md 获取完整数据。


跟进序列

每次跟进都应加入新内容——不同的角度、新的证据、有用的资源。“只是跟进一下”不会给读者任何回复的理由。

  • 总共3-5封邮件,间隔逐渐增大
  • 每封邮件应独立成篇(他们可能没读过之前的邮件)
  • 分手邮件是你的最后接触——遵守它

参见 follow-up-sequences.md 了解节奏、角度轮换和分手邮件模板。


质量检查

在呈现之前,进行直觉检查:

  • 看起来像真人写的吗?(大声读出来)
  • 如果你收到它,你会回复吗?
  • 每句话是为读者服务,还是为发件人服务?
  • 个性化是否与问题相关?
  • 是否有一个清晰、低门槛的行动号召?

要避免什么

  • 以“我希望这封邮件能让您感到愉快”或“我叫X,我在Y工作”开头
  • 行话:“协同”、“利用”、“回头再谈”、“最佳”、“领先供应商”
  • 功能堆砌——一个证据点胜过十个功能
  • HTML、图片或多个链接
  • 虚假的“Re:”或“Fwd:”主题行
  • 只替换了{{名字}}的相同模板
  • 在第一次接触中要求30分钟的电话会议
  • “只是跟进一下”的后续邮件

数据与基准

参考资料中包含性能数据,以便你在需要时做出明智选择:

利用这些数据来指导你的写作——而不是作为检查清单来满足。


相关技能

  • prospecting: 用于构建和筛选本技能要撰写邮件的潜在客户名单——这是冷邮件之前的自然上游步骤
  • copywriting: 用于着陆页和网页文案
  • emails: 用于生命周期/培育邮件序列(非冷拓客)
  • social: 用于领英和社交媒体帖子
  • product-marketing: 用于建立基础定位
  • revops: 用于潜在客户评分、路由和管道管理

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

ab-testing

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions

ads

When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions

ai-seo

When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions

analytics

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions

aso

When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions

attribution

When the user wants to figure out which marketing actually drives conversions and revenue, choose or interpret an attribution model, or reconcile conflicting numbers across tools. Also use when the user mentions

churn-prevention

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions

co-marketing

When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says

community-marketing

Build and leverage online communities to drive product growth and brand loyalty. Use when the user wants to create a community strategy, grow a Discord or Slack community, manage a forum or subreddit, build brand advocates, increase word-of-mouth, drive community-led growth, engage users post-signup, or turn customers into evangelists. Trigger phrases: \

competitor-profiling

When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions

competitors

When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions

content-strategy

When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions

copy-editing

When the user wants to edit, review, or improve existing marketing copy, or refresh outdated content. Also use when the user mentions

copywriting

When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says

coreyhaines31/ab-test-setup

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.

coreyhaines31/analytics-tracking

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "attribution," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For A/B test measurement, see ab-test-setup.

coreyhaines31/aso-audit

When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my app conversion,' 'keyword optimization for app,' or 'compare my app to competitors.' Use when the user shares an App Store or Google Play URL and wants to improve it.

coreyhaines31/competitor-alternatives

When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'battle card,' or 'competitor teardown.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For sales-specific competitor docs, see sales-enablement.

coreyhaines31/email-sequence

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.

coreyhaines31/form-cro

When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms. Also use when the user mentions "form optimization," "lead form conversions," "form friction," "form fields," "form completion rate," "contact form," "nobody fills out our form," "form abandonment," "too many fields," "demo request form," or "lead form isn't converting." Use this for any non-signup form that captures information. For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.

相关技能