New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Cold Email

by alirezarezvani in alirezarezvani/claude-skills

When the user wants to write, improve, or build a sequence of B2B cold outreach emails to prospects who haven't asked to hear from them.

MITAuto-check passedSales & Support

Install Cold Email

skills CLI
$ npx skills add alirezarezvani/claude-skills --skill cold-email -a claude-code

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

GitHub CLI
$ gh skill install alirezarezvani/claude-skills cold-email --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/alirezarezvani/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/marketing-skill/skills/cold-email .claude/skills/cold-email && 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
GitHub stars
28k
Used in
1 other repo
Token cost
~3.6k tokens
SKILL.md length
2,030 words
Files
5 (incl. scripts, references)
Skills in repo
342
Repo updated
First seen
Licence
MIT

At a glance

When the user wants to write, improve, or build a sequence of B2B cold outreach emails to prospects who haven't asked to hear from them.

  • Works in 8 steps: The Sender → The Prospect → The Ask → …
  • Build a sequence of B2B cold outreach emails to prospects who havent asked to hear from them
  • SKILL.md covers Before Starting, How This Skill Works, Core Writing Principles and Voice Calibration by Audience, plus 9 more sections
  • Runs Python scripts from its folder; calls python3

What it does

Cold Email is an agent skill from alirezarezvani/claude-skills. When the user wants to write, improve, or build a sequence of B2B cold outreach emails to prospects who haven't asked to hear from them. Use when the user mentions 'cold email,' 'cold outreach,' 'prospecting emails,' 'SDR emails,' 'sales emails,' 'first touch email,' 'follow-up sequence,' or 'email prospecting.' Also use when they share an email draft that sounds too sales-y and needs to be humanized. Distinct from email-sequence (lifecycle/nurture to opted-in subscribers) — this is unsolicited outreach to new…

Its SKILL.md is about 3.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts and reference files (for example `references/deliverability-guide.md`, `references/follow-up-playbook.md` and `references/frameworks.md`).

It sits in Sales & Support, covering Cold outreach and Email marketing. The repository describes itself as: 380 Claude Code skills & agent skills & plugins (30+ Agents, 70+ custom commands, 380+ skills, customizable references, scripts)for Claude Code, Codex, Gemini CLI, Cursor, and 8… The licence is MIT.

When your agent uses it

  • Build a sequence of B2B cold outreach emails to prospects who havent asked to hear from them
  • The user mentions cold email
  • Prospecting emails
  • First touch email

Example prompts

  • “t asked to hear from them. Use when the user mentions”
  • “cold outreach,”
  • “prospecting emails,”
  • “/cold-email”

Requirements

  • Python 3

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. The Sender
  2. The Prospect
  3. The Ask
  4. Write Like a Peer, Not a Vendor
  5. Every Sentence Earns Its Place
  6. Personalization Must Connect to the Problem
  7. Lead With Their World, Not Yours
  8. One Ask Per Email

What it can do on your machine

Read from SKILL.md and the folder at commit 19392f7. 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

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3

    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 loads about 3.6k tokens when it runs, and up to ~11k if it reads all its reference files. Until then it costs about 154 tokens; SKILL.md has 2,030 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~154
When it runs · the whole SKILL.md, loaded when a task matches
~3.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~11k

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); the scripts in this folder are not scanned.

SKILL.md

The full file from alirezarezvani/claude-skills at commit 19392f7, republished under its MIT licence (© alirezarezvani). 2,030 words, ~3,650 tokens.

Download SKILL.mdSave it as .claude/skills/cold-email/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
cold-email
description
When the user wants to write, improve, or build a sequence of B2B cold outreach emails to prospects who haven't asked to hear from them. Use when the user mentions 'cold email,' 'cold outreach,' 'prospecting emails,' 'SDR emails,' 'sales emails,' 'first touch email,' 'follow-up sequence,' or 'email prospecting.' Also use when they share an email draft that sounds too sales-y and needs to be humanized. Distinct from email-sequence (lifecycle/nurture to opted-in subscribers) — this is unsolicited outreach to new prospects. NOT for lifecycle emails, newsletters, or drip campaigns (use email-sequence).
license
MIT
metadata.version
1.0.0
metadata.author
Alireza Rezvani
metadata.category
marketing
metadata.updated
2026-03-06

Cold Email Outreach

You are an expert in B2B cold email outreach. Your goal is to help write, build, and iterate on cold email sequences that sound like they came from a thoughtful human — not a sales machine — and actually get replies.

Before Starting

Check for context first: If .claude/product-marketing-context.md exists, read it before asking questions.

Gather this context:

1. The Sender
  • Who are they at this company? (Role, seniority — affects how they write)
  • What do they sell and who buys it?
  • Do they have any real customer results or proof points they can reference?
  • Are they sending as an individual or as a company?
2. The Prospect
  • Who is the target? (Job title, company type, company size)
  • What problem does this person likely have that the sender can solve?
  • Is there a specific trigger or reason to reach out now? (funding, hiring, news, tech stack signal)
  • Do they have specific names and companies to personalize to, or is this a template for a segment?
3. The Ask
  • What's the goal of the first email? (Book a call? Get a reply? Get a referral?)
  • How aggressive is the timeline? (SDR with daily send volume vs founder doing targeted outreach)

How This Skill Works

Mode 1: Write the First Email

When they need a single first-touch email or a template for a segment.

  1. Understand the ICP, the problem, and the trigger
  2. Choose the right framework (see references/frameworks.md)
  3. Draft first email: subject line, opener, body, CTA
  4. Review against the principles below — cut anything that doesn't earn its place
  5. Deliver: email copy + 2-3 subject line variants + brief rationale
Mode 2: Build a Follow-Up Sequence

When they need a multi-email sequence (typically 4-6 emails).

  1. Start with the first email (Mode 1)
  2. Plan follow-up angles — each email needs a different angle, not just a nudge
  3. Set the gap cadence (Day 1, Day 4, Day 9, Day 16, Day 25)
  4. Write each follow-up with a standalone hook that doesn't require reading previous emails
  5. End with a breakup email that closes the loop professionally
  6. Deliver: full sequence with send gaps, subject lines, and brief on what each email does
Mode 3: Iterate from Performance Data

When they have an active sequence and want to improve it.

  1. Review their current sequence emails and performance (open rate, reply rate)
  2. Diagnose: is the problem subject lines (low open rate), email body (opens but no replies), or CTA (replies but wrong outcome)?
  3. Rewrite the underperforming element
  4. Deliver: revised emails + diagnosis + test recommendation

Core Writing Principles

1. Write Like a Peer, Not a Vendor

The moment your email sounds like marketing copy, it's over. Think about how you'd actually email a smart colleague at another company who you want to have a conversation with.

The test: Would a friend send this to another friend in business? If the answer is no — rewrite it.

  • ❌ "I'm reaching out because our platform helps companies like yours achieve unprecedented growth..."
  • ✅ "Noticed you're scaling your SDR team — timing question: are you doing outbound email in-house or using an agency?"
2. Every Sentence Earns Its Place

Cold email is the wrong place to be thorough. Every sentence should do one of these jobs: create curiosity, establish relevance, build credibility, or drive to the ask. If a sentence doesn't do one of those — cut it.

Read your draft aloud. The moment you hear yourself droning, stop and cut.

3. Personalization Must Connect to the Problem

Generic personalization is worse than none. "I saw you went to MIT" followed by a pitch has nothing to do with MIT. That's fake personalization.

Real personalization: "I saw you're hiring three SDRs — usually a signal that you're trying to scale cold outreach. That's exactly the challenge we help with."

The personalization must connect to the reason you're reaching out.

4. Lead With Their World, Not Yours

The opener should be about them — their situation, their problem, their context. Not about you or your product.

  • ❌ "We're a sales intelligence platform that..."
  • ✅ "Your recent TechCrunch piece mentioned you're entering the SMB market — that transition is notoriously hard to do with an enterprise-built playbook."
5. One Ask Per Email

Don't ask them to book a call, watch a demo, read a case study, AND reply with their timeline. Pick one ask. The more you ask for, the less likely any of it happens.

Voice Calibration by Audience

Adjust tone, length, and specificity based on who you're writing to:

AudienceLengthToneSubject Line StyleWhat Works
C-suite (CEO, CRO, CMO)3-4 sentencesUltra-brief, peer-level, strategicShort, vague, internal-lookingBig problem → relevant proof → one question
VP / Director5-7 sentencesDirect, metrics-consciousSlightly more specificSpecific observation + clear business angle
Mid-level (Manager, Analyst)7-10 sentencesPractical, shows you did homeworkCan be more descriptiveSpecific problem + practical value + easy CTA
Technical (Engineer, Architect)7-10 sentencesPrecise, no fluffTechnical specificityExact problem → precise solution → low-friction ask

The higher up the org chart, the shorter your email needs to be. A CEO gets 100+ emails per day. Three sentences and a clear question is a gift, not a slight.

Subject Lines: The Anti-Marketing Approach

The goal of a subject line is to get the email opened — not to convey value, not to be clever, not to impress anyone. Just open it.

The best cold email subject lines look like internal emails. They're short, slightly vague, and create just enough curiosity to click.

What Works
PatternExampleWhy It Works
Two or three wordsquick questionLooks like an actual email from a colleague
Specific trigger + questionyour TechCrunch pieceSpecific enough to not look like spam
Shared contextre: Series BFeels like a follow-up, not cold
Observationyour ATS setupSpecific, relevant, not salesy
Referral hook[mutual name] suggested I reach outSocial proof front-loaded
What Kills Opens
  • ALL CAPS anything
  • Emojis in subject lines (polarizing, often spam-filtered)
  • Fake Re: or Fwd: (people have learned this trick — it damages trust)
  • Asking a question in the subject line (e.g., "Are you struggling with X?") — sounds like an ad
  • Mentioning your company name ("Acme Corp: helping you achieve...")
  • Numbers that feel like blog headlines ("5 ways to improve your...")

Follow-Up Strategy

Most deals happen in follow-ups. Most follow-ups are useless. The difference is whether the follow-up adds value or just creates noise.

Cadence
EmailSend DayGap
Email 1Day 1—
Email 2Day 4+3 days
Email 3Day 9+5 days
Email 4Day 16+7 days
Email 5Day 25+9 days
BreakupDay 35+10 days

Gaps increase over time. You're persistent but not annoying.

Follow-Up Rules

Each follow-up must have a new angle. Rotate through:

  • New piece of evidence (case study, data point, recent result)
  • New angle on the problem (a different pain point in their world)
  • Related insight (something you noticed about their industry, tech stack, or news)
  • Direct question (just ask plainly — sometimes clarity cuts through)
  • Reverse ask (ask for referral to the right person if you can't reach them)

Never "just check in." "Just following up to see if you had a chance to read my last email" is a waste of both your time and theirs. If you have nothing new to add, don't send the email.

Don't reference all previous emails. Each follow-up should stand alone. The prospect doesn't remember your earlier emails. Don't make them scroll.

Show full SKILL.md (798 more words)Show less
The Breakup Email

The last email in a sequence should close the loop professionally. It signals this is the last one — which paradoxically increases reply rate because people don't like loose ends.

Example breakup:

"I'll stop cluttering your inbox after this one. If [problem] ever becomes a priority, happy to reconnect — just reply here and I'll pick it up.

If there's someone else at [Company] I should speak with, a name would go a long way.

Either way — good luck with [whatever's relevant]."

See references/follow-up-playbook.md for full cadence templates and angle rotation guide.

What to Avoid

These are not suggestions — they're patterns that mark you as a non-human and kill reply rates:

❌ AvoidWhy It Fails
"I hope this email finds you well"Instant tell that this is templated. Cut it.
"I wanted to reach out because..."3-word delay before actually saying anything
Feature dump in email 1Nobody cares about features when they don't trust you yet
HTML templates with logos and colorsLooks like marketing, gets spam-filtered
Fake Re:/Fwd: subject linesFeels deceptive — kills trust before the first word
"Just checking in" follow-upsAdds no value, removes credibility
Opening with "My name is X and I work at Y"They can see your name. Start with something interesting.
Social proof that doesn't connect to their problem"We work with 500 companies" means nothing without context
Long-form case study in email 1Save it for follow-up when they've shown interest
Passive CTAs ("Let me know if you're interested")Weak. Ask a direct question or propose a specific next step.

Deliverability Basics

A great email sent from a flagged domain never lands. Basics you need to have in place:

  • Dedicated sending domain — don't send cold email from your primary domain. Use mail.yourdomain.com or outreach.yourdomain.com.
  • SPF, DKIM, DMARC — all three must be configured and passing. Use mail-tester.com to verify.
  • Domain warmup — new domains need 4-6 weeks of warmup (start with 20/day, ramp up over time).
  • Plain text emails — or minimal HTML. Heavy HTML triggers spam filters.
  • Unsubscribe mechanism — required legally (CAN-SPAM, GDPR). Include a simple opt-out.
  • Sending limits — stay under 100-200 emails/day per domain until established reputation.
  • Bounce rate — above 5% hurts deliverability. Verify email lists before sending.

See references/deliverability-guide.md for domain warmup schedule, SPF/DKIM setup, and spam trigger word list.

Proactive Triggers

Surface these without being asked:

  • Email opens with "My name is" or "I'm reaching out because" → rewrite the opener. These are dead-on-arrival openers. Flag and offer an alternative that leads with their world.
  • First email is longer than 150 words → almost certainly too long. Flag word count and offer to trim.
  • No personalization beyond first name → templated feel will hurt reply rates. Ask if there's a trigger or signal they can work with.
  • Follow-up says "just checking in" or "circling back" → useless follow-up. Ask what new angle or value they can bring to that touchpoint.
  • HTML email template → recommend plain text. Plain text emails have higher deliverability and look less like marketing blasts.
  • CTA asks for 30-45 minute meeting in email 1 → too high-friction for cold outreach. Recommend a lower-commitment ask (a 15-minute call, or just a question to gauge interest first).

Tools

ToolInvocationOutput
Sequence analyzerpython3 scripts/email_sequence_analyzer.py sequence.json (no arg = embedded demo; - reads stdin)Per-email 0-100 score across word count, reading level, personalization, CTA clarity, spam triggers, subject lines

Run it on every drafted sequence before delivering: any email scoring below 70 gets rewritten against the flagged dimensions (spam triggers and CTA clarity first), then re-scored.

Output Artifacts

When you ask for...You get...
Write a cold emailFirst-touch email + 3 subject line variants + brief rationale for structure choices
Build a sequence5-6 email sequence with send gaps, subject lines per email, and angle summary for each follow-up — scored with email_sequence_analyzer.py before delivery
Critique my emailLine-by-line assessment + rewrite + explanation of each change
Write follow-ups onlyFollow-up emails 2-6 with unique angles per email + breakup email
Analyze sequence performanceemail_sequence_analyzer.py score report + diagnosis of where the sequence breaks (subject/body/CTA) + specific rewrite recommendations

Communication

All output follows the structured communication standard:

  • Bottom line first — answer before explanation
  • What + Why + How — every finding has all three
  • Actions have owners and deadlines — no "we should consider"
  • Confidence tagging — 🟢 verified / 🟡 medium / 🔴 assumed
  • email-sequence: For lifecycle and nurture emails to opted-in subscribers. Use email-sequence for onboarding flows, re-engagement campaigns, and automated drips. NOT for cold outreach — that's cold-email.
  • copywriting: For marketing page copy. Principles overlap, but cold email has different constraints — shorter, no CTAs like buttons, must feel personal.
  • content-strategy: For creating the content assets (case studies, guides) you reference in cold email follow-ups. Good follow-up sequences often link to content.
  • marketing-strategy-pmm: For positioning and ICP definition. If you don't know who you're targeting and why, cold email is the wrong tool to figure that out.

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

Files

SKILL.md and 4 other files (scripts, references) in marketing-skill/skills/cold-email of alirezarezvani/claude-skills.

  • SKILL.md
  • references/deliverability-guide.md
  • references/follow-up-playbook.md
  • references/frameworks.md
  • scripts/email_sequence_analyzer.py

Open the folder on GitHubat commit 19392f7

Used in 1 other repository

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

Compare with similar skills

Cold Email 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 compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cold Email this skillalirezarezvani/claude-skills28k1 repos~3.6kAutomated safety check: PassMIT
Cold EmailLeoYeAI/openclaw-marketing-skills1k4 repos~1.8kAutomated safety check: PassCustom licence
Predictable Revenuewondelai/skills2.4k—~3.1kAutomated safety check: PassMIT
Cold Email Templates 34swan-gtm/gtm-skills165—~581Automated safety check: PassMIT
Send Cold Emailmajiayu000/claude-skill-registry6661 repos~1.2kAutomated safety check: PassMIT
Outreach Specialistognjengt/founder-skills427—~3.2kAutomated safety check: PassMIT

Similar skills

  • Cold Email

    LeoYeAI/openclaw-marketing-skills

    Write B2B cold emails and follow-up sequences that get replies.

    1k GitHub starsUsed in 4 repos~1.8k tokens
    Sales & SupportAuto-check passed

  • Predictable Revenue

    wondelai/skills

    Build a scalable outbound B2B sales machine with specialized roles (SDR, AE, CSM).

    2.4k GitHub stars~3.1k tokensUpdated 28 days ago
    Sales & SupportAuto-check passed

  • Cold Email Templates 34

    swan-gtm/gtm-skills

    A skill your agent uses when building email campaigns, looking for proven cold email templates, or expanding an outreach playbook.

    165 GitHub stars~581 tokensUpdated yesterday
    Sales & SupportAuto-check passed

  • Send Cold Email

    majiayu000/claude-skill-registry

    Send cold email and run outbound email campaigns from an agent with Sendsets.

    666 GitHub starsUsed in 1 repo~1.2k tokens
    Sales & SupportAuto-check passed

  • Outreach Specialist

    ognjengt/founder-skills

    Crafts high-converting outreach messages and email sequences for cold outreach, LinkedIn DMs, and follow-ups.

    427 GitHub stars~3.2k tokensUpdated 4 mo ago
    Sales & SupportAuto-check passed

  • Money Outreach

    iamzifei/show-me-the-money

    Automated outreach and sales pipeline — cold email sequences, partnership outreach, lead generation, and prospect management.

    1k GitHub stars~3k tokensUpdated 1 mo ago
    Sales & SupportAuto-check passed

More from alirezarezvani/claude-skills

All 342 skills in this repo

  • Agile Product Owner

    alirezarezvani/claude-skills

    Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.

    28k GitHub starsUsed in 3 repos~3.2k tokens
    Auto-check passed

  • Product Strategist

    alirezarezvani/claude-skills

    OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.

    28k GitHub starsUsed in 2 repos~1.8k tokens
    Auto-check passed

  • App Store Optimization

    alirezarezvani/claude-skills

    App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store.

    28k GitHub starsUsed in 1 repo~4.2k tokens
    Auto-check passed

  • AWS Solution Architect

    alirezarezvani/claude-skills

    Design AWS architectures for startups using serverless patterns and IaC templates.

    28k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

  • Campaign Analytics

    alirezarezvani/claude-skills

    Calculates attribution, funnel and ROI figures for marketing campaigns with three Python scripts that need only the standard library.

    28k GitHub starsUsed in 1 repo~2.1k tokens
    Auto-check passed

  • Code to PRD

    alirezarezvani/claude-skills

    Reverse-engineers a frontend, backend or fullstack codebase into a product requirements document with per-page docs, an enum dictionary and an API inventory.

    28k GitHub starsUsed in 1 repo~4.9k tokens
    Auto-check passed

Categories

Questions about Cold Email

What does Cold Email do?

When the user wants to write, improve, or build a sequence of B2B cold outreach emails to prospects who haven't asked to hear from them. Cold Email is an agent skill from alirezarezvani/claude-skills. When the user wants to write, improve, or build a sequence of B2B cold outreach emails to prospects who haven't asked to hear from them.

When should I use Cold Email?

Cold Email fits situations like: build a sequence of B2B cold outreach emails to prospects who havent asked to hear from them; the user mentions cold email; prospecting emails; first touch email.

How do I install Cold Email in Claude Code?

Run `npx skills add alirezarezvani/claude-skills --skill cold-email -a claude-code`. Or copy the skill folder (marketing-skill/skills/cold-email in alirezarezvani/claude-skills) into .claude/skills/cold-email in your project. Claude Code loads it when a task matches its description.

How do I install Cold Email in Codex?

Run `npx skills add alirezarezvani/claude-skills --skill cold-email -a codex`. Or copy the skill folder (marketing-skill/skills/cold-email in alirezarezvani/claude-skills) into .agents/skills/cold-email in your project. Codex loads it when a task matches its description.

Can I use Cold Email 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 alirezarezvani/claude-skills --skill cold-email -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, .gemini/skills/cold-email, .github/skills/cold-email and .opencode/skills/cold-email in your project.

What does Cold Email need to run?

Going by SKILL.md and its folder, Cold Email needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Cold Email 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 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Cold Email use?

Cold Email is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cold Email use?

About 3.6k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 6.9k tokens, read only when the agent opens those files.

What are the alternatives to Cold Email?

Skills that share tags, products or a category with Cold Email: Cold Email (LeoYeAI/openclaw-marketing-skills, 1k stars), Predictable Revenue (wondelai/skills, 2.4k stars), Cold Email Templates 34 (swan-gtm/gtm-skills, 165 stars) and Send Cold Email (majiayu000/claude-skill-registry, 666 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cold Email?

alirezarezvani (a GitHub user) maintains it in alirezarezvani/claude-skills, which has 27,829 GitHub stars. The repository holds 342 skills in this directory. The repository was last updated on August 30, 2026.

Source: alirezarezvani/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.