做什么
写入 B2B 冷信邮件和获得回复的后继序列
技能库 智客分类:Agent 工作流 cold-email
写入 B2B 冷取邮件和获得回复的后继序列 。 当用户想要写冷的外延电子邮件、 搜索电子邮件、 冷的电子邮件活动、 销售开发电子邮件或特别提款权电子邮件时使用 。 当用户提到“冷酷的外联”、“探险邮件”、“外出邮件”、“电子邮件引领”、“接触前景”、“销售邮件”、“后续邮件序列”、“没有人回复我的邮件”或“我如何写冷酷邮件”时, 覆盖主题行,开行行行,身体复制,CTA,个性化,多触地后续序列. 关于温暖/生命周期的电子邮件序列,请参见电子邮件。 关于电子邮件以外的销售担保,见销售担保.
官方网址:skills.sh
先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。
写入 B2B 冷信邮件和获得回复的后继序列
用户希望写冷的外联邮件、探矿邮件、冷的电子邮件宣传、销售开发电子邮件或特别提款权电子邮件。 当用户提到“冷漠的外联”、“探险电子邮件”、“外出电子邮件”、“电子邮件引领”、“接触前景”、“销售电子邮件”、“fol”时也使用
按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Cold Email Writing、Before Writing、Writing Principles、Write like a peer, not a vendor、Every sentence must earn its place、Personalization must connect to the problem。
文件分析:除 SKILL.md 外,正文引用了 references/personalization.md、references/frameworks.md、references/subject-lines.md、references/follow-up-sequences.md、references/benchmarks.md,属于带资源的技能包,这些文件按需再读。
Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences. For warm/lifecycle email sequences, see emails. For sales collateral beyond emails, see sales-enablement.
Cold Email WritingBefore WritingWriting PrinciplesWrite like a peer, not a vendorEvery sentence must earn its placePersonalization must connect to the problemLead with their world, not yoursOne ask, low frictionVoice & ToneStructureSubject LinesFollow-Up Sequences
来源分类:skills.sh agent-skill
namecold-emaildescriptionreferences/personalization.mdreferences/frameworks.mdreferences/subject-lines.mdreferences/follow-up-sequences.mdreferences/benchmarks.md以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。
具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗
先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。
该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。
复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。
把 Agent Skill「cold-email」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-3a968114016d7a8c-%E5%86%B7%E7%94%B5%E5%AD%90%E9%82%AE%E4%BB%B6.html 请存为 .cursor/skills/cold-email/SKILL.md 或 .claude/skills/cold-email/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。 该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/coreyhaines31/marketingskills 取完整目录,不要只建一个 SKILL.md。
需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。
npx skills add 'https://github.com/coreyhaines31/marketingskills' --list
npx skills add 'https://github.com/coreyhaines31/marketingskills' --skill 'cold-email'
CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。
You are an expert cold email writer. Your goal is to write emails that sound like they came from a sharp, thoughtful human — not a sales machine following a template.
Check for product marketing context first:
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Understand the situation (ask if not provided):
Work with whatever the user gives you. If they have a strong signal and a clear value prop, that's enough to write. Don't block on missing inputs — use what you have and note what would make it stronger.
The email should read like it came from someone who understands their world — not someone trying to sell them something. Use contractions. Read it aloud. If it sounds like marketing copy, rewrite it.
Cold email is ruthlessly short. If a sentence doesn't move the reader toward replying, cut it. The best cold emails feel like they could have been shorter, not longer.
If you remove the personalized opening and the email still makes sense, the personalization isn't working. The observation should naturally lead into why you're reaching out.
See personalization.md for the 4-level system and research signals.
The reader should see their own situation reflected back. "You/your" should dominate over "I/we." Don't open with who you are or what your company does.
Interest-based CTAs ("Worth exploring?" / "Would this be useful?") beat meeting requests. One CTA per email. Make it easy to say yes with a one-line reply.
The target voice: A smart colleague who noticed something relevant and is sharing it. Conversational but not sloppy. Confident but not pushy.
Calibrate to the audience:
What it should NOT sound like:
There's no single right structure. Choose a framework that fits the situation, or write freeform if the email flows naturally without one.
Common shapes that work:
For the full catalog of frameworks with examples, see frameworks.md.
Short, boring, internal-looking. The subject line's only job is to get the email opened — not to sell.
See subject-lines.md for the full data.
Each follow-up should add something new — a different angle, fresh proof, a useful resource. "Just checking in" gives the reader no reason to respond.
See follow-up-sequences.md for cadence, angle rotation, and breakup email templates.
Before presenting, gut-check:
The references contain performance data if you need to make informed choices:
Use this data to inform your writing — not as a checklist to satisfy.
Agent 工作流
创造有效技能指南。 当用户想创造出新的技能(或更新现有的技能),以专业知识,工作流程,或工具集成来扩展克洛德的能力时,应该使用这种技能.
Agent 工作流
使用ClawdHub CLI搜索,安装,更新并发布从taladhub.com的代理技能. 需要获取苍蝇上的新技能时使用,将安装的技能同步到最新版本或特定版本,或者发布 npm-instainddhub CLI 的新/更新的技能文件夹.
Agent 工作流
管弦乐团多代理团队,任务设定周期,交接协议,审查工作流程. 使用时间: (1)建立2+特派员队伍,具有不同专业,(2)确定任务路线和生命周期(收录框_ spec_建设_审查_完成),(3)在特派员之间制定交接协议,(4)建立审查和质量关口,(5)管理特派员之间的交流和文物共享.
Agent 工作流
Spec-first,TDD,子代理驱动的软件开发工作流程. 当:(1)构建任何新功能或应用——触发脑暴_计划_子代理执行回路,(2)调试出一个bug或测试失败——触发系统性的根起过程,(3)用户说"让我们构建","帮助我计划","我想添加X",或"这个被打破",(4)完成一个功…