agentleFS
oncesylviaoncesylvia/fundraising-skills/skills/cold-email/SKILL.md

cold-email

Skill4 starsChanged 5 months agoMITView on GitHub

Write short, personalized cold fundraising emails to investors (VCs, angels) plus a polite follow-up sequence. Use when a founder says "write a cold email to an investor", "draft an outreach email to <fund/partner>", "help me email a VC", or wants to improve an existing cold email. Enforces real personalization and truthful traction — refuses spray-and-pray.

97 other projects use a version of this.

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

8 rules. 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 90 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write a cold email that earns a reply by being short, specific, and obviously researched.

    line 8
  2. Very specific:

    Read shared/references/outreach-ethics.md first.

    line 13
  3. Distinctive:

    Ask the founder for whatever is missing:

    line 19
  4. Very specific:

    One specific personalization per email: No find-and-replace {{firstName}} mail merge.

    line 51
  5. Distinctive:

    Truthful traction: Never inflate. Don't imply investors/customers you don't have.

    line 54
  6. Distinctive:

    Short: If it doesn't fit on a phone screen without scrolling, cut.

    line 56
  7. Distinctive:

    Plain text feel: No images, no heavy formatting, no tracking-pixel theater.

    line 58
  8. Very specific:

    If the founder is raising in the China market or asks for Chinese output, use references/zh-talk-tracks.md and first read …

    line 84

“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

Cold email to investors

Write a cold email that earns a reply by being short, specific, and obviously researched. The bar: the investor should feel you wrote it for them, it should be skimmable in 15 seconds, and the ask should be trivially easy to say yes to.

Read shared/references/outreach-ethics.md first. If you can't ground the email in something true and specific about this investor, it isn't ready — go research (use the investor-targeting skill) before drafting.

Gather before drafting

Ask the founder for whatever is missing:

  1. Who you're emailing — name, firm, and the specific reason they fit (a recent deal, a stated thesis, a portfolio company like yours). This is the personalization hook; without it, stop.
  2. One-liner — what you do, for whom.
  3. Traction — the 1–2 hardest, truest proof points (revenue, growth, users, notable design partners/LOIs). Use the founder's numbers verbatim.
  4. The ask & the raise — stage, how much, and what you want from this email (usually a 20–30 min call, not "let's talk").
  5. Credibility — anything that de-risks the founder (relevant background, notable existing investors/advisors — only if real).

The anatomy (keep it ~75–125 words)

See references/email-anatomy.md for the deep version. The shape:

  1. Subject line — 3–6 words, concrete, no hype. Offer two A/B options. Good: "Seed round — <category> for <customer>" / "<Mutual context> + our <metric>". Bad: "Game-changing opportunity!!!"
  2. The hook (1 sentence) — the specific, true reason you're emailing them. "I saw you led <company>'s seed — we're building the <X> version for <Y>."
  3. What you do (1 sentence) — crisp, jargon-free, the wedge.
  4. Traction (1–2 sentences) — the proof that you're worth 20 minutes. Numbers > adjectives.
  5. The ask (1 sentence) — one specific, low-friction request. "Open to a 20-min call next week?" Optionally offer the deck/data instead of attaching.
  6. Signature — name, role, company, one link (site or deck). No giant attachments on a cold email.

Hard rules

  • One specific personalization per email. No find-and-replace {{firstName}} mail merge. If you're drafting for several investors, write a distinct hook for each; share only the middle.
  • Truthful traction. Never inflate. Don't imply investors/customers you don't have.
  • Short. If it doesn't fit on a phone screen without scrolling, cut.
  • One ask. Multiple asks = no reply.
  • Plain text feel. No images, no heavy formatting, no tracking-pixel theater.

Follow-up sequence

Most replies come from follow-ups, not the first email. Draft a polite, value-adding sequence (see references/email-anatomy.md for templates):

  • Follow-up 1 (after ~4–5 business days): brief bump + one new piece of info (a fresh metric, a new customer, a milestone). Not "just checking in."
  • Follow-up 2 (after ~7 days): shorter still; restate the one ask, add a graceful out ("if it's not a fit, no worries — a pointer to who might be right would mean a lot").
  • Then stop. Two or three touches total. More is harassment and hurts your name. Honor any "not now / not a fit" immediately.

Output format

Deliver:

  • 2 subject-line options
  • The email body (ready to paste)
  • Follow-up 1 and Follow-up 2 drafts
  • A one-line personalization checklist: the specific true fact you used, and a reminder to re-verify it before sending.

Bilingual / China market (中文)

If the founder is raising in the China market or asks for Chinese output, use references/zh-talk-tracks.md and first read shared/references/china-market-playbook.md. Don't just translate the English — China's primary channel is WeChat (微信), not email, etiquette and forms of address differ, and a warm path matters even more. The zh file gives WeChat opener + email versions, follow-ups, and a personalization checklist in Chinese.

Refuse / push back when

  • The user wants one generic email to blast to a list → offer instead to write a reusable frame plus per-investor hooks, and point them to the volume note in the ethics file.
  • The traction described seems inflated or fabricated → ask for the real numbers.
  • There's a warm path available → suggest the warm-intro skill instead; a warm intro beats the best cold email.

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.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.