Write cold emails and outreach with AI

Updated 2026-10-11 15 分钟 Difficulty ★☆☆☆☆Author Skills 编辑部

Skills used in this guide (3)

  • email-opsemail-opsPrimary

    以证据为先的邮箱处理流程:分类、起草、发送验证与安全的跟进确认。适合整理邮件、真实发送,或需要证明到底发没发出去。

    npx skills add affaan-m/ECC -g
  • investor-outreachinvestor-outreachSupporting

    撰写冷邮件、引荐介绍、跟进信与投资人更新。适合需要面向天使、VC、战略投资方或加速器做简洁且有针对性的沟通。

    npx skills add affaan-m/ECC -g
  • marketing-campaignmarketing-campaignSupporting

    端到端的营销活动策划与执行:受众研究、定位、切入点、落地页文案、邮件序列、社媒帖子、广告文案、短视频脚本与内容日历,作为多渠道产品发布的编排层。

    npx skills add affaan-m/ECC -g

The worst cold email is "mass-send feel" — binned as spam at a glance. The point: give the recipient profile and one real value, make it point-to-point like handwritten, not templated blast. Reply rate comes from relevance, not length.

Who this is for / not for

For:

  • Write cold emails / outreach
  • Have a list but can't personalize
  • Want batch that still feels 1:1

Not for:

  • Bought lists blast (that's spam)
  • Fabricate data for replies (integrity first)
  • Send and never optimize

Before you start

  1. Profile: role, pain, where you met/saw them.
  2. Your value: one hook they truly use.
  3. Goal: chat / forward / trial, sets CTA.

Steps

1. Install the skill

email-ops is an email-ops skill. Copy its folder into your client's skills directory (same as any Agent Skill):

ClientDirectory
Claude Code~/.claude/skills/
Codex~/.codex/skills/
Cursor~/.cursor/skills/
Trae~/.trae/skills/
CodeBuddy~/.codebuddy/skills/
Tongyi Lingma~/.lingma/skills/

2. Personalize, not template

text
Cold emails to 20 SaaS founders, goal 15-min call.
Each opens with one specific line from their site/recent move (no "congrats on funding" cliché),
body 3 lines: I noticed X → we helped similar teams hit Y → 15 min chat.
Each different, like handwritten.

3. High-value with investor-outreach

For investors/key people use investor-outreach, heavier hook & proof:

text
Outreach to an AI-tools investor: open with a podcast point they made,
bring our 30-day retention, ask a short chat. Restrained, evidence, no full deck.

4. You finalize & send

Confirm no fabricated data, clear CTA, then send.

Pitfalls

PitSymptomFix
Mass feelBinnedSpecific opener each
FabricateFake dataReal data only
Too longUnreadUnder 3 lines
No CTANo replyState the ask
Bought listSpam boxPermission list

FAQ

Batch personalized?

Yes — one real hook per recipient, then batch still reads handwritten.

Length?

Under 3 lines: noticed→value→chat. Short replies more.

Investor outreach?

Hook + real data + restraint, no long deck.

No data?

Write anyway, but persuasion needs real proof; don't invent.

No replies?

Tune opener relevance & CTA, A/B small then scale.

Related guides

Continue across these scenes:

相关源码

一句话结论

结论:冷邮件做点对点个性化、3 句内说清价值,回复率靠相关不靠篇幅,别编数据。

References