agentleFS
CodeAlive-AICodeAlive-AI/ceo-ai-os/skills/cold-email/SKILL.md

cold-email

Skill9 starsChanged 6 months agoMITView on GitHub

Write B2B cold emails and follow-up sequences that get replies. Use for "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email," "nobody's replying to my emails," "how do I write a cold email." For sending and tracking outreach, see outreach-sender. For warm/lifecycle emails, see email-sequence. For sales strategy, see founder-sales.

97 other projects use a version of this, 67 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use free-tools, popups and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CesarjoquinSkill

    free-tools

    When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," "free resource," "ROI calculator," "grader tool," "audit tool," "should I build a free tool," or "tools for lead gen." Use this whenever someone wants to build something useful and give it away to attract leads or earn links. For downloadable content lead magnets (ebooks, checklists, templates), see lead-magnets.

    Also in 25 projects that use this

  • CesarjoquinSkill

    popups

    When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," "overlay," "collect emails with a popup," "exit popup," "scroll trigger," "sticky bar," or "notification bar." Use this for any overlay or interrupt-style conversion element. For forms outside of popups, see cro. For general page conversion optimization, see cro.

    Also in 23 projects that use this

  • coreyhaines31Skill

    marketing-council

    When the user wants multiple expert perspectives on a marketing question — a simulated board of advisors staffed by legendary marketers (Seth Godin, David Ogilvy, Eugene Schwartz, April Dunford, Rory Sutherland, Alex Hormozi, Byron Sharp, and more). Also use when the user mentions 'marketing council,' 'board of advisors,' 'advisory board,' 'what would Seth Godin say,' 'what would Ogilvy think,' 'channel Hormozi,' 'get multiple perspectives,' 'debate this,' 'have the council review,' 'marketing mentors,' or asks how a famous marketer would approach their problem. The council gives each advisor's take through their documented frameworks, surfaces where they disagree, and synthesizes a recommendation. For executing the winning direction, hand off to positioning, offers, copywriting, ads, or the relevant skill.

    Also in 18 projects that use this

  • Hussain-ElfalahSkill

    andreessen

    Also in 4 projects that use this

  • Hussain-ElfalahSkill

    business-investment-advisor

    Also in 4 projects that use this

  • roerohanSkill

    emails

    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.

    Also in 24 projects that use this

  • +5 more from Cesarjoquin
  • +1 more from Hussain-Elfalah

The file

We split this skill into the rules it gives an agent

5 rules. 3 are common, 1 is distinctive, and 1 is very specific to this project.

  • 3

    Common

    Most of the 90 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Before helping, read MEMORY.md for: current wedge, ICP, competitors, PMF stage, system constraint.

    line 9
  2. Distinctive:

    Follow output preferences from USER.md (language, format, platform constraints).

    line 11
  3. Common:

    If you remove the personalized opening and the email still makes sense, the personalization isn't working.

    line 45
  4. Common:

    Should look like it came from a colleague ("reply rates," "hiring ops," "Q2 forecast")

    line 93
  5. Common:

    No product pitches, no urgency, no emojis, no prospect's first name

    line 94

“Common” is measured: kept by at least 6 in 10 of the 90 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

[YOUR_PRODUCT] Context

Before helping, read MEMORY.md for: current wedge, ICP, competitors, PMF stage, system constraint. Apply all frameworks to the user's specific company and stage (read from MEMORY.md). Follow output preferences from USER.md (language, format, platform constraints). For chat platforms: max 15 lines, no markdown tables, be concrete and actionable.

Cold Email Writing

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.

Before Writing

Understand the situation (ask if not provided):

  1. Who are you writing to? — Role, company, why them specifically
  2. What do you want? — The outcome (meeting, reply, intro, demo)
  3. What's the value? — The specific problem you solve for people like them
  4. What's your proof? — A result, case study, or credibility signal
  5. Any research signals? — Funding, hiring, LinkedIn posts, company news, tech stack changes

Work with whatever the user gives you. Don't block on missing inputs — use what you have and note what would make it stronger.


Writing Principles

Write like a peer, not a vendor

The email should read like it came from someone who understands their world. Use contractions. Read it aloud. If it sounds like marketing copy, rewrite it.

Every sentence must earn its place

Cold email is ruthlessly short. If a sentence doesn't move the reader toward replying, cut it.

Personalization must connect to the problem

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.

Lead with their world, not yours

"You/your" should dominate over "I/we." Don't open with who you are or what your company does.

One ask, low friction

Interest-based CTAs ("Worth exploring?" / "Would this be useful?") beat meeting requests. One CTA per email.


Voice & Tone

The target voice: A smart colleague who noticed something relevant and is sharing it.

Calibrate to the audience:

  • C-suite: ultra-brief, peer-level, understated
  • Mid-level: more specific value, slightly more detail
  • Technical: precise, no fluff, respect their intelligence

What it should NOT sound like:

  • A template with fields swapped in
  • A pitch deck compressed into paragraph form
  • AI-generated ("I hope this email finds you well," "I came across your profile," "leverage," "synergy")

Structure

Choose a framework that fits the situation:

  • Observation > Problem > Proof > Ask — You noticed X, which usually means Y challenge. We helped Z with that. Interested?
  • Question > Value > Ask — Struggling with X? We do Y. Company Z saw [result]. Worth a look?
  • Trigger > Insight > Ask — Congrats on X. That usually creates Y challenge. We've helped similar companies with that.
  • Story > Bridge > Ask — [Similar company] had [problem]. They [solved it this way]. Relevant to you?

For the full catalog of frameworks with examples, see frameworks.md.


Subject Lines

Short, boring, internal-looking. The subject line's only job is to get the email opened.

  • 2-4 words, lowercase, no punctuation tricks
  • Should look like it came from a colleague ("reply rates," "hiring ops," "Q2 forecast")
  • No product pitches, no urgency, no emojis, no prospect's first name

See subject-lines.md for the full data.


Follow-Up Sequences

Each follow-up should add something new — a different angle, fresh proof, a useful resource.

  • 3-5 total emails, increasing gaps between them
  • Each email should stand alone
  • The breakup email is your last touch — honor it

See follow-up-sequences.md for cadence, angle rotation, and breakup email templates.


Quality Check

Before presenting, gut-check:

  • Does it sound like a human wrote it? (Read it aloud)
  • Would YOU reply to this if you received it?
  • Does every sentence serve the reader, not the sender?
  • Is the personalization connected to the problem?
  • Is there one clear, low-friction ask?

What to Avoid

  • Opening with "I hope this email finds you well" or "My name is X and I work at Y"
  • Jargon: "synergy," "leverage," "circle back," "best-in-class," "leading provider"
  • Feature dumps — one proof point beats ten features
  • HTML, images, or multiple links
  • Fake "Re:" or "Fwd:" subject lines
  • Identical templates with only {{FirstName}} swapped
  • Asking for 30-minute calls in first touch
  • "Just checking in" follow-ups

Data & Benchmarks

  • benchmarks.md — Reply rates, conversion funnels, common mistakes
  • personalization.md — 4-level personalization system, research signals
  • subject-lines.md — Subject line data and optimization
  • follow-up-sequences.md — Cadence, angles, breakup emails
  • frameworks.md — All copywriting frameworks with examples

Related Skills

  • outreach-sender — send orchestration: takes cold-email drafts → humanizer → approval → Gmail send
  • pipeline-manager — pipeline context for personalization
  • founder-sales — sales strategy and signal-based outreach workflow
  • humanizer — polish emails to remove AI patterns (critical for credibility)
  • email-sequence — warm/lifecycle sequences (not cold outreach)
  • prospect-demo — personalized demo snippets to include in emails
  • sales-qualification — lead qualification before outreach

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.