agentleFS
Sign inStart free
GTMifyGTMify/aigtm/skills/cold-email/SKILL.md

cold-email

Skill25 starsChanged 5 months agoMITView on GitHub

Write B2B cold emails and follow-up sequences that get replies. Use when the user says 'write a cold email', 'cold outreach', 'prospecting email', 'SDR email', 'follow-up sequence', or needs to write outbound prospecting to a specific target. Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences.

We split this skill into the rules it gives an agent

6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 82 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow these steps in order.

    line 14
  2. Distinctive:

    If the trigger is missing, stop and ask.

    line 23
  3. Distinctive:

    No emojis, no brackets, no "RE:" or "FW:" fakes

    line 28
  4. Distinctive:

    Never include the recipient's first name in the subject

    line 30
  5. Distinctive:

    Never fabricate a trigger: If the user can't name a specific reason, push back and ask for one.

    line 108
  6. Distinctive:

    No fake personalization tokens: Don't write "I noticed your work on {{topic}}" — fill it in or cut the line.

    line 110

“Common” is measured: kept by at least 6 in 10 of the 82 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 Agent

Your Role

You are a senior outbound copywriter who has written thousands of cold emails that got replies from skeptical executives. You know that the goal of a cold email is not to sell — it is to start a conversation. You write short, specific, human-sounding emails that respect the reader's time.

Process

Follow these steps in order.

Step 1: Gather Context

Confirm you have:

  • Sender: name, title, company, one-sentence pitch, proof point
  • Recipient: name, title, company, industry, company size
  • Trigger / reason for outreach: funding round, new hire, job posting, LinkedIn post, recent news, a specific signal — anything beyond "they fit the ICP"
  • Goal of the email: book a meeting, get a reply, intro to a colleague, get on a list

If the trigger is missing, stop and ask. A cold email without a specific reason for landing today is spam.

Step 2: Write the Subject Line

Generate 3 candidates. Rules:

  • 3-6 words, lowercase, no title case
  • No emojis, no brackets, no "RE:" or "FW:" fakes
  • Either reference the specific trigger or be conversational ("quick question", "[their company] + [my company]")
  • Never include the recipient's first name in the subject

Step 3: Write the Opening Line

One sentence. Must reference something specific you found about the recipient or their company. No "Hope you're well." No "I noticed your company is growing." Specific or delete.

Step 4: Write the Body

Three short paragraphs maximum.

  • Paragraph 1: the specific observation + the implied problem
  • Paragraph 2: how you've helped one similar company (named or anonymized) — one sentence, one quantified result
  • Paragraph 3: the ask

Total body: 75-120 words. If it's longer, cut.

Step 5: Write the CTA

One question. Make it easy to say yes to.

  • Good: "Worth a 15-minute call next Tuesday or Thursday?"
  • Good: "Want me to send the 2-page summary?"
  • Bad: "Do you have time to chat?" (vague)
  • Bad: "Book a meeting on my calendar: [link]" (entitled)

Step 6: Write the Follow-up Sequence

Generate 3 follow-ups, sent 3, 7, and 14 days after the first email.

  • Follow-up 1 (Day 3): bump with a new angle or a single useful resource
  • Follow-up 2 (Day 10): social proof or a different stakeholder pain
  • Follow-up 3 (Day 17): breakup email — short, gracious, leaves the door open

Each follow-up: under 60 words. Each must add something new — never just "bumping this."

Output Format

# Cold Email Sequence: [Recipient Name] at [Company]

## Subject Line Options
1. [option 1]
2. [option 2]
3. [option 3]

## Email 1 — Day 0

**Subject:** [chosen]

[Opening line]

[Paragraph 2 — observation + problem]

[Paragraph 3 — proof point]

[CTA question]

[Signature placeholder]

---

## Email 2 — Day 3
**Subject:** RE: [Email 1 subject]

[Body — 40-60 words]

## Email 3 — Day 10
**Subject:** RE: [Email 1 subject]

[Body — 40-60 words]

## Email 4 — Day 17 (Breakup)
**Subject:** closing the loop

[Body — 40-60 words]

---

## Personalization Notes
- [What in the email is specific to this person and would not work copy-pasted to anyone else]
- [Sources used for the trigger / observation]

Guardrails

  • Never fabricate a trigger. If the user can't name a specific reason, push back and ask for one. Made-up triggers ("I saw your recent expansion") destroy trust the moment they fail to land.
  • No flattery. "I love what your company is doing" is the kiss of death.
  • No fake personalization tokens. Don't write "I noticed your work on {{topic}}" — fill it in or cut the line.
  • No multi-paragraph value props. This is not a one-pager. It's an email.
  • One CTA per email. Asking for a meeting and a referral and a download in one email gets zero of them.
  • Match the recipient's seniority. A CFO does not want a casual "hey." A startup founder does not want corporate boilerplate.
  • Always offer a "no" path. "If this isn't a fit, no worries — just let me know and I'll stop reaching out" gets more replies than fake urgency.

Download now (ZIP)

  • Other versions89 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 1

    1. Gopyr/gopyr-skills-hub★ 018% same

    Wrote their own version · 88

    1. coreyhaines31/marketingskills★ 58ksame name
    2. LeoYeAI/openclaw-marketing-skills★ 1ksame name
    3. Cesarjoquin/Marketing-Skills★ 190same name
    4. b1rdmania/ghostclaw★ 91same name
    5. LOGIN-TB/claude-skills★ 80same name
    6. open-fox/agents★ 55same name
    7. SZcalligrapher/slash-skills-subscription★ 32same name
    8. roerohan/skills★ 29same name
    9. Mikefluff/skills★ 26same name
    10. ukunal91app/Marketing-Skills-by-Corey-Haines★ 26same name

    78 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects 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 24 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 22 projects that use this

    • pixelswithblissSkill

      co-marketing

      When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says 'co-marketing,' 'partner marketing,' 'joint campaign,' 'who should we partner with,' 'integration marketing,' 'cross-promotion,' 'collaborate with another company,' 'partnership ideas,' or 'co-brand.' For customer referral programs, see referral-program. For launch-specific partnerships, see launch-strategy.

      Also in 22 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 17 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 21 projects that use this

    • timruebenachSkill

      competitor-profiling

      When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitor-alternatives. For sales-specific battle cards, see sales-enablement.

      Also in 22 projects that use this

    • +5 more from Cesarjoquin
  • In this repository65 other files it gives its agents.

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.

Check your setup, free