Agent skill

Cold Email Writer

by Infrasity-Labs in Infrasity-Labs/dev-gtm-claude-skills

Write personalized cold outreach emails to hiring managers and founders — specific, human, not a pitch deck

MITAuto-check passedSales & Support

Install Cold Email Writer

skills CLI
$ npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill cold-email-writer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Infrasity-Labs/dev-gtm-claude-skills cold-email-writer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Infrasity-Labs/dev-gtm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/job-search/cold-email-writer .claude/skills/cold-email-writer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
cold-email-writer
GitHub stars
136
Used in
1 other repo
Token cost
~1.9k tokens
SKILL.md length
671 words
Files
1
Skills in repo
26
Repo updated
First seen
Licence
MIT

At a glance

Write personalized cold outreach emails to hiring managers and founders — specific, human, not a pitch deck

  • Works in 4 steps: Company angle — read their website, JD,… → Recipient name — LinkedIn, team page, or… → Relevant projects — match the… → …
  • Tasks that involve Cold outreach
  • SKILL.md covers When to Use This Skill, Core Principle, The Template Structure and Research Before Writing, plus 4 more sections
  • Calls just

What it does

Cold Email Writer is an agent skill from Infrasity-Labs/dev-gtm-claude-skills. Write personalized cold outreach emails to hiring managers and founders — specific, human, not a pitch deck

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Sales & Support, covering Cold outreach and Fundraising and pitch decks. The repository describes itself as: Open-source Claude skills for GEO, AI discoverability, and developer GTM workflows. Built for developer-focused companies that want their documentation to be found, parsed, and… The licence is MIT.

When your agent uses it

  • Tasks that involve Cold outreach
  • Tasks that involve Fundraising and pitch decks

Example prompts

  • “/cold-email-writer”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Company angle — read their website, JD, or About page. Find one specific thing worth mentioning.
  2. Recipient name — LinkedIn, team page, or AngelList. "Hi [Name]" beats "Hi Hiring Manager" every time.
  3. Relevant projects — match the candidate's most relevant work to the role domain.
  4. Stack overlap — mention it only if there's a genuine match.

What it can do on your machine

Read from SKILL.md and the folder at commit 02cfefb. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • just

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cold Email Writer loads about 1.9k tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 671 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~31
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Infrasity-Labs/dev-gtm-claude-skills at commit 02cfefb, republished under its MIT licence (© Infrasity-Labs). 671 words, ~1,869 tokens.

Download SKILL.mdSave it as .claude/skills/cold-email-writer/SKILL.md (or your agent's skills folder).
name
cold-email-writer
description
Write personalized cold outreach emails to hiring managers and founders — specific, human, not a pitch deck

Cold Email Writer

When to Use This Skill

Use this skill when the user wants to:

  • Write a cold outreach email to a hiring manager, founder, or recruiter
  • Reach out about a job opening they weren't referred to
  • Introduce themselves to a company they want to work at
  • Mentions: "cold email", "reach out", "intro email", "outreach", "contact hiring manager"

Core Principle

Cold emails fail because they sound like cover letters. The goal is to sound like a smart person who genuinely noticed something specific about the company — not a candidate broadcasting their credentials.

The email should feel like: A colleague mentioning something interesting they read, not a sales pitch.

The Template Structure

Subject
Quick intro — [First Name Last Name]

Simple. No clickbait. No role title. Just a name.

Opening — The Hook (2-3 sentences)

Start with what genuinely pulled the candidate in. Must be specific to this company — not a generic compliment.

I just came across [Company] and ended up spending more time on it than I expected.
[One specific thing that caught their attention — a stat, a product decision, a market insight from the JD or website]

What makes a good hook:

  • A specific number or stat from the company's materials ("only 5% of the market is online")
  • A product decision that shows you understand the domain ("you're building from scratch alongside underwriters, not just distribution")
  • A technical insight from the JD ("improving the data infrastructure for LLM usage, not just the model layer")

What makes a bad hook:

  • Generic: "I love what you're building"
  • Vague: "Your mission resonates with me"
  • Flattering: "You're one of the most exciting companies in the space"
Location Disclosure (if international)

If the candidate is in a different country from the company, disclose it early and casually:

Before you read further, I should mention I'm based in [country]. But if we both
feel there's a strong fit, I'd be open to figuring things out.
Experience Gap (if applicable)

If the role lists more years than the candidate has, acknowledge it briefly and redirect:

The role mentions [X] years of experience — I'm at [Y], but the work I've
shipped is production-facing and I'd rather you judge that directly.
The Body — Who They Are (3-5 sentences)

Current role → relevant past → one or two projects. Keep it contextual, not a list.

A bit about me: I currently work at [Company], [one line on what the company does],
where I [what they actually do there — not a job title]. Before that I worked
with teams in [region], mostly around [relevant domain].

On the side I've been building [Project] ([link if applicable]) — [one line: what
it is and one proof point like "got to paying clients" or "20K downloads"].

Rules:

  • Mention work as context, not as proof of greatness
  • No achievement listings ("I increased X by Y%") — let the project speak
  • If current company is remote with a European/international team, say so explicitly
  • Keep project mentions to one or two max — the most relevant ones only
The Connection (1-2 sentences)

Bridge between their background and the specific role. Should feel like an observation, not a claim.

I think you're looking for [what the role actually wants] — that's the kind of
work I've been doing, and honestly I feel like I'd be a strong fit.

Or more specific:

My stack maps naturally to yours — [specific tech overlap]. But more than the
stack, it's the [domain/problem] that I'm genuinely interested in.
More about me: [portfolio URL]

One line. No elaboration.

Closing

End with low-pressure, confident energy. Not desperate, not corporate.

I'm currently at [Company] and open to what's next. I think my experience lends
nicely to what you're building — so I think we'd both get something out of a
conversation.

[First Name]
[email]

Avoid:

  • "I look forward to hearing from you"
  • "Please find attached my resume"
  • "I would love the opportunity to..."
  • "I am excited to potentially join..."
Show full SKILL.md (270 more words)Show less

Research Before Writing

Before writing the email, gather:

  1. Company angle — read their website, JD, or About page. Find one specific thing worth mentioning.
  2. Recipient name — LinkedIn, team page, or AngelList. "Hi [Name]" beats "Hi Hiring Manager" every time.
  3. Relevant projects — match the candidate's most relevant work to the role domain.
  4. Stack overlap — mention it only if there's a genuine match.

If the user provides a JD but no company website, ask for it or fetch it before writing.

Length Guidelines

  • Ideal: 200–300 words
  • Maximum: 400 words
  • Minimum: 150 words (don't strip out substance for brevity)

Longer is fine if every sentence earns its place. Cut anything that could apply to any company.

Output Format

Always wrap the final email in a plain code block for clean copy-paste:

Subject: Quick intro — [Name]

Hi [Name],

[Email body]

[First Name]
[email]

Common Mistakes to Avoid

Too confident: ❌ "I would be an exceptional addition to your team" ❌ "My background uniquely positions me for this role" ✅ "I feel like I'd be a strong fit" — states a belief, doesn't claim certainty

Too humble: ❌ "I know I may not have all the experience you're looking for, but..." ❌ "I'm just reaching out on the off chance..." ✅ Acknowledge gaps directly and move on — don't apologize

Too long: ❌ Three paragraphs listing every achievement ✅ One paragraph on background, one on the connection

Too generic: ❌ Opening with "I am writing to express my interest in..." ✅ Opening with what specifically pulled them to this company

No research: ❌ "I love your product and mission" ✅ "The 5% stat — only 5% of a $25B market online — doesn't feel like a feature gap, it feels like an entire industry that hasn't digitised"

Example Email

Subject: Quick intro — Sarah Chen

Hi Marcus,

I just came across Meridian and spent more time on your site than I planned.
What pulled me in was the framing around your data infrastructure — you're not
just building an LLM layer on top of existing records, you're rethinking how
clinical data flows through the system in the first place. That's a harder
problem and a more interesting one.

I'm based in India, flagging that upfront. Happy to figure out the rest if
there's a real fit.

I currently work at Lune, a London-based climate intelligence company, where I
build event-driven data pipelines and agentic AI workflows for emissions
compliance — regulated, data-intensive systems where reliability isn't optional.
I also built Memos, a RAG system from scratch: hybrid retrieval, reranking,
ChromaDB, FastAPI. And InframetAI, an SDK for LLM cost and latency
observability that came out of seeing what breaks when the data layer isn't
designed around how models actually work.

I think you're looking for engineers who've actually built AI systems end to
end, not just wrapped APIs. That's the work I've been doing.

More about me: yourportfolio.com/about

I'm currently at Lune and open to what's next. I think my experience maps
closely to what you're building — so I think we'd both get something out of
a conversation.

Sarah
sarah@email.com

© Infrasity-Labs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in job-search/cold-email-writer of Infrasity-Labs/dev-gtm-claude-skills.

Open the folder on GitHubat commit 02cfefb

Used in 1 other repository

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in Infrasity-Labs/dev-gtm-claude-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Cold Email Writer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cold Email Writer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cold Email Writer this skillInfrasity-Labs/dev-gtm-claude-skills1361 repos~1.9kAutomated safety check: PassMIT
Business ProposalsEliasOulkadi/shokunin114—~2.7kAutomated safety check: PassMIT
Prospect Panel SimulatorOneWave-AI/claude-skills336—~1.2kAutomated safety check: PassMIT
Apify Buying Signal Detectionapify/awesome-skills266—~5.1kAutomated safety check: NotesApache-2.0
Investor Outreachaffaan-m/ECC277k6 repos~664Automated safety check: PassMIT
Vc Outreachpedronauck/skills634—~480Automated safety check: PassNone

Similar skills

  • Business Proposals

    EliasOulkadi/shokunin

    Generate sales outreach sequences, proposals, SOWs, investor pitch decks, and RFP responses.

    114 GitHub stars~2.7k tokensUpdated 6 days ago
    Sales & SupportAuto-check passed
  • Prospect Panel Simulator

    OneWave-AI/claude-skills

    Simulate a panel of your real prospects and buyers to pressure-test sales and marketing before it goes out — cold emails, pitch decks, landing pages, pricing pages, demo scripts, proposals.

    336 GitHub stars~1.2k tokensUpdated 9 days ago
    Sales & SupportAuto-check passed
  • Apify Buying Signal Detection

    apify/awesome-skills

    Official

    Set up a recurring buying-signal detection pipeline that finds companies showing buying intent across three signal types — job postings (hiring for the persona), fundraising events (recent raises)…

    266 GitHub stars~5.1k tokensUpdated 18 days ago
    Business, Finance & HRAuto-check: notes
  • Investor Outreach

    affaan-m/ECC

    Draft cold emails, warm intro blurbs, follow-ups, update emails, and investor communications for fundraising.

    277k GitHub starsUsed in 6 repos~664 tokens
    Business, Finance & HRAuto-check passed
  • Vc Outreach

    pedronauck/skills

    Build investor lists, warm intros and cold emails; prepare meetings, manage a raise pipeline, and run diligence through close.

    634 GitHub stars~480 tokensUpdated 26 days ago
    Business, Finance & HRAuto-check passed
  • Investor Outreach

    c0x12c/ai-toolkit

    Draft cold emails, warm intro blurbs, follow-ups, and investor communications.

    106 GitHub stars~864 tokensUpdated 3 mo ago
    Sales & SupportAuto-check passed

More from Infrasity-Labs/dev-gtm-claude-skills

All 26 skills in this repo
  • Brief Outline Generator

    Infrasity-Labs/dev-gtm-claude-skills

    Generates a fully structured SEO content outline (not a finished brief) and exports it as a formatted .docx Word document.

    136 GitHub stars~4k tokensUpdated 3 mo ago
    Auto-check passed
  • Content Brief

    Infrasity-Labs/dev-gtm-claude-skills

    Generates a fully structured SEO content brief for a target keyword and optionally pushes it to a Notion database.

    136 GitHub stars~2.8k tokensUpdated 3 mo ago
    Auto-check passed
  • API Docs Quality Report

    Infrasity-Labs/dev-gtm-claude-skills

    Audits any API documentation site by crawling every endpoint page and scoring each one across 5 checks: description quality, OpenAPI spec presence, body param descriptions, response codes, and…

    136 GitHub stars~2.5k tokensUpdated 3 mo ago
    Auto-check passed
  • Docs Auditor

    Infrasity-Labs/dev-gtm-claude-skills

    Audits any developer documentation site across 33 checks in 7 categories and produces a scored report (out of 100) with Pass / Warn / Fail status per check.

    136 GitHub stars~3k tokensUpdated 3 mo ago
    Auto-check passed
  • Growth Report

    Infrasity-Labs/dev-gtm-claude-skills

    Generates a 3-month SEO performance HTML report for any domain using DataForSEO data.

    136 GitHub stars~4k tokensUpdated 3 mo ago
    Auto-check passed
  • Inbox

    Infrasity-Labs/dev-gtm-claude-skills

    Email triage system that handles both one-time setup and recurring triage in a single skill.

    136 GitHub stars~4.8k tokensUpdated 3 mo ago
    Auto-check passed

Questions about Cold Email Writer

What does Cold Email Writer do?

Write personalized cold outreach emails to hiring managers and founders — specific, human, not a pitch deck. Cold Email Writer is an agent skill from Infrasity-Labs/dev-gtm-claude-skills.

When should I use Cold Email Writer?

Cold Email Writer fits situations like: tasks that involve Cold outreach; tasks that involve Fundraising and pitch decks.

How do I install Cold Email Writer in Claude Code?

Run `npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill cold-email-writer -a claude-code`. Or copy the skill folder (job-search/cold-email-writer in Infrasity-Labs/dev-gtm-claude-skills) into .claude/skills/cold-email-writer in your project. Claude Code loads it when a task matches its description.

How do I install Cold Email Writer in Codex?

Run `npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill cold-email-writer -a codex`. Or copy the skill folder (job-search/cold-email-writer in Infrasity-Labs/dev-gtm-claude-skills) into .agents/skills/cold-email-writer in your project. Codex loads it when a task matches its description.

Can I use Cold Email Writer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill cold-email-writer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cold-email-writer, .gemini/skills/cold-email-writer, .github/skills/cold-email-writer and .opencode/skills/cold-email-writer in your project.

What does Cold Email Writer need to run?

Going by SKILL.md and its folder, Cold Email Writer needs the command-line tools its instructions call (just).

Does Cold Email Writer access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Cold Email Writer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Cold Email Writer use?

Cold Email Writer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cold Email Writer use?

About 1.9k tokens (SKILL.md is roughly 7.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Cold Email Writer?

Skills that share tags, products or a category with Cold Email Writer: Business Proposals (EliasOulkadi/shokunin, 114 stars), Prospect Panel Simulator (OneWave-AI/claude-skills, 336 stars), Apify Buying Signal Detection (apify/awesome-skills, 266 stars) and Investor Outreach (affaan-m/ECC, 277k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cold Email Writer?

Infrasity-Labs (a GitHub user) maintains it in Infrasity-Labs/dev-gtm-claude-skills, which has 136 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on June 28, 2026.

Source: Infrasity-Labs/dev-gtm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.