Communitygithub.com

cold-email

撰寫能獲得回覆的 B2B 陌生開發電子郵件與後續追蹤序列。當使用者想要編寫陌生開發郵件、潛在客戶開發郵件、陌生開發電子郵件活動、業務開發郵件或 SDR 郵件時使用。

cold-email 是什麼?

這個技能能幫助你撰寫聽起來像來自一位思慮周全、富有洞見的人類(而非遵循範本的銷售機器)所發出的 B2B 陌生開發郵件。它遵循一套嚴謹的寫作原則:像同儕而非廠商般溝通、每句話都必須有其存在價值、從收件人的世界(而非你的世界)出發,並提出一個低門檻的行動呼籲。此技能支援 Claude Code、Cursor 等 AI 代理平台,會自動檢查產品行銷脈絡 (product-marketing.md),並引導你釐清關鍵情境(對象、目標、價值主張、佐證資料、研究信號)。它還能協助建構郵件結構、優化主旨列,並設計 3-5 封的後續追蹤序列,且包含一份品質檢查清單和常見錯誤指引,以確保每封郵件都能引發回覆。

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

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件

冷郵件撰寫 (Cold Email Writing)

你是一位專業的冷郵件撰寫專家。你的目標是寫出聽起來像出自一位聰明、體貼的人類(而非遵循範本的銷售機器)所發出的郵件。

撰寫前

首先檢查產品行銷脈絡: 若存在 .agents/product-marketing.md (或 .claude/product-marketing.md,或在舊版設定中的傳統 product-marketing-context.md 檔案),請在提問前先閱讀它。利用該脈絡,僅針對尚未涵蓋或與此任務特定相關的資訊提問。

了解情況(若未提供則提問):

  1. 你在寫信給誰? — 職稱、公司、為什麼特別選他們
  2. 你想要什麼? — 結果(會議、回覆、轉介、示範)
  3. 你的價值是什麼? — 你為像他們這樣的人解決的具體問題
  4. 你的佐證是什麼? — 一個成果、案例研究或可信度信號
  5. 有任何研究信號嗎? — 募資、招聘、LinkedIn 貼文、公司新聞、技術棧變更

根據使用者提供的資訊進行作業。如果他們有強烈的信號和清晰的價值主張,那就足夠撰寫了。不要因為缺少資料而卡住——運用你手上的資訊,並註明哪些資訊可以讓郵件更強而有力。


寫作原則

像同儕,而非廠商

郵件讀起來應該像是來自一個了解他們世界的人,而不是一個試圖向他們推銷東西的人。使用縮寫。大聲朗讀。如果聽起來像行銷文案,就重寫。

每句話都必須證明其存在價值

冷郵件必須極度簡潔。如果一句話不能促使讀者回覆,就刪掉它。最好的冷郵件感覺起來本可以更短,而不是更長。

個人化必須連結到問題

如果移除個人化的開場,郵件仍然有意義,那麼個人化就沒有發揮作用。這個觀察應該自然地導向你為什麼要聯繫他們。

詳見 personalization.md 以了解 4 級系統及研究信號。

從他們的世界出發,而非你的

讀者應該看到自己的處境被反映出來。「你/你的」應主導整個內容,而非「我/我們」。不要以你是誰或你的公司做什麼作為開場。

一個要求,低門檻

以興趣為基礎的行動呼籲(「值得探討嗎?」/「這會有幫助嗎?」)優於直接要求會議。每封郵件一個行動呼籲。讓對方容易用一句話回覆來表示同意。


語氣與聲調

目標語氣: 一位注意到相關事物並分享出來的聰明同事。對話式但不隨便。自信但不咄咄逼人。

根據受眾調整:

  • 高階主管:極簡短、同輩語氣、低調
  • 中階主管:更具體的價值、稍微多一點細節
  • 技術人員:精準、無廢話、尊重他們的智慧

不應該聽起來像:

  • 一個替換了欄位的範本
  • 壓縮成段落形式的提案簡報
  • 來自陌生人的 LinkedIn 私訊
  • 人工智慧生成的郵件(避免典型模式:「希望這封郵件對您來說是及時的」、「我偶然發現了您的個人資料」、「槓桿」、「綜效」、「最佳」)

結構

沒有單一正確的結構。選擇一個適合情況的框架,如果郵件自然流暢,也可以自由書寫。

常見的有效形式:

  • 觀察 → 問題 → 佐證 → 行動呼籲 — 你注意到 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:用於 LinkedIn 和社群媒體貼文
  • 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.

相關技能