Cold Outbound Optimizer
ericosiu/ai-marketing-skills
Design, analyze, and optimize cold outbound email campaigns for Instantly.
Write and optimize B2B cold email outreach sequences that get replies, covering personalization, follow-up cadence, deliverability, and compliance.
$ npx skills add borghei/Claude-Skills --skill cold-email -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-Skills cold-email --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/marketing/cold-email .claude/skills/cold-email && rm -rf skills-srcUse ~/.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/
Install the "cold-email" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/cold-email into .claude/skills/cold-email/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cold-email", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/borghei/Claude-Skills/tree/main/marketing/cold-emailType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add borghei/Claude-Skills --skill cold-email -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills cold-email --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/marketing/cold-email .agents/skills/cold-email && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cold-email" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/cold-email into .agents/skills/cold-email/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cold-email", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill cold-email -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills cold-email --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/marketing/cold-email .cursor/skills/cold-email && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cold-email" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/cold-email into .cursor/skills/cold-email/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cold-email", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/borghei/Claude-Skills.git --path marketing/cold-email--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add borghei/Claude-Skills --skill cold-email -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-Skills cold-email --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/marketing/cold-email .gemini/skills/cold-email && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cold-email" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/cold-email into .gemini/skills/cold-email/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cold-email", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install borghei/Claude-Skills cold-emailInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add borghei/Claude-Skills --skill cold-email -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/marketing/cold-email .github/skills/cold-email && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cold-email" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/cold-email into .github/skills/cold-email/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cold-email", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill cold-email -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install borghei/Claude-Skills cold-email --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/marketing/cold-email .opencode/skills/cold-email && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cold-email" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/cold-email into .opencode/skills/cold-email/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cold-email", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
cold-emailWrite and optimize B2B cold email outreach sequences that get replies, covering personalization, follow-up cadence, deliverability, and compliance.
Cold Email is an agent skill from borghei/Claude-Skills. Write and optimize B2B cold email outreach sequences that get replies, covering personalization, follow-up cadence, deliverability, and compliance. Use when writing cold outreach, prospecting/SDR emails, or building outbound sequences.
Its SKILL.md is about 5.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `scripts/deliverability_checker.py`, `scripts/sequence_optimizer.py` and `scripts/subject_line_scorer.py`).
It sits in Sales & Support, covering Cold outreach. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.
8 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.
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.
Ships 3 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
pythonFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Cold Email loads about 5.7k tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 2,809 words of instructions outside code blocks.
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.
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.
The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 2,809 words, ~5,711 tokens.
.claude/skills/cold-email/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.Production-grade B2B cold email that sounds like it came from a person, not a sequence tool.
cold email, cold outreach, prospecting email, SDR email, sales email, first-touch email, follow-up sequence, email prospecting, outbound email, sales development, sequence building, email personalization, email deliverability, CAN-SPAM, GDPR, B2B outreach, email compliance, subject lines, reply rates, breakup email
Before generating the email, confirm these inputs. If any is unknown or vague, ASK — do not assume:
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
Step 1: Gather Context
Required information:
Step 2: Choose Framework
| Framework | Best When | Structure |
|---|---|---|
| Problem-First | Prospect has a visible pain point | Problem observation > Relevance > Ask |
| Trigger-Based | There is a specific event (funding, hiring, news) | Trigger reference > Connection to problem > Ask |
| Mutual Connection | Referral or shared network | Name drop > Context > Ask |
| Value-First | You have something genuinely useful to share | Insight/resource > Brief context > Ask |
| Direct Ask | Prospect is high-intent or very senior | Brief context > Direct question |
Step 3: Draft the Email
Structure:
Subject: [2-4 words, looks like an internal email]
[Opener: 1 sentence about their world — trigger, observation, or question]
[Relevance: 1-2 sentences connecting their situation to what you do]
[Proof: 1 sentence of credible evidence — specific number, named customer, result]
[Ask: 1 sentence with a single, specific, low-friction CTA]
[Sign-off]Step 4: Validate
Step 1: Write Email 1 (Using Workflow 1)
Step 2: Plan Follow-Up Angles
Each follow-up needs a distinct angle. Plan before writing:
| Day | Angle | What is New | |
|---|---|---|---|
| 1 | Day 1 | Problem-first | Initial outreach |
| 2 | Day 4 | New evidence | Case study, data point, or recent result |
| 3 | Day 9 | Different pain point | Alternative angle on their world |
| 4 | Day 16 | Industry insight | Something notable about their space |
| 5 | Day 25 | Direct question | Simple, clear ask without context |
| 6 | Day 35 | Breakup | Professional close, referral ask |
Step 3: Write Each Follow-Up
Rules for every follow-up:
Step 4: Write the Breakup Email
The breakup email closes the loop. It signals this is the last one, which paradoxically increases reply rate.
Template:
Subject: closing the loop
[Name],
Last note from me. If [specific problem] becomes a priority,
reply here and I'll pick it up.
If there's someone else at [Company] better suited for this
conversation, a name would help.
Either way — [genuine well-wish related to something specific].
[Sign-off]Step 1: Diagnose the Problem
| Symptom | Likely Cause | Fix |
|---|---|---|
| Low open rate (< 25%) | Subject lines | Test new subject line patterns |
| Opens but no replies (< 2% reply rate) | Email body | Rewrite with stronger relevance and lower-friction CTA |
| Replies but wrong outcome | CTA mismatch | Adjust the ask |
| High bounce rate (> 5%) | List quality | Verify email addresses before sending |
| Landing in spam | Deliverability | Check SPF/DKIM/DMARC, reduce send volume, warm domain |
Step 2: Rewrite the Underperforming Element
Focus on one element at a time. Do not rewrite the entire email when only the subject line is the problem.
Step 3: Test and Measure
The moment your email sounds like marketing copy, it is deleted.
Test: Would you send this to a smart colleague at another company? If not, rewrite.
Each sentence must do one of these jobs:
If a sentence does none of these, cut it.
Generic personalization is worse than none.
The personalization must bridge to the reason for reaching out.
The opener should be about their situation, problem, or context. Not about you or your product.
Do not ask them to book a call, watch a demo, read a case study, AND reply with their timeline. Pick one.
| Audience | Length | Tone | Subject Style | What Works |
|---|---|---|---|---|
| C-suite (CEO, CRO, CMO) | 3-4 sentences | Ultra-brief, peer-level, strategic | Short, vague, internal-looking | Big problem > relevant proof > one question |
| VP / Director | 5-7 sentences | Direct, metrics-conscious | Slightly more specific | Specific observation + clear business angle |
| Manager | 7-10 sentences | Practical, shows homework | Can be descriptive | Specific problem + practical value + easy CTA |
| Technical (Engineer, Architect) | 7-10 sentences | Precise, no fluff | Technical specificity | Exact problem > precise solution > low-friction ask |
| Founder / Solo | 5-7 sentences | Empathetic, peer-to-peer | Casual, human | Shared experience + relevant proof + conversational ask |
Rule: The higher up the org chart, the shorter your email needs to be.
The goal of a subject line is to get the email opened. Not to convey value, not to be clever. Just opened.
The best cold email subject lines look like internal emails: short, slightly vague, enough curiosity to click.
| Pattern | Example | Why It Works |
|---|---|---|
| Two or three words | "quick question" | Looks like a real email from a colleague |
| Specific trigger + question | "your TechCrunch piece" | Specific enough to not look like spam |
| Shared context | "re: Series B" | Feels like a follow-up, not cold |
| Observation | "your ATS setup" | Relevant, not salesy |
| Referral hook | "[mutual name] suggested I reach out" | Social proof front-loaded |
| Role-specific | "SDR team scaling" | Shows you know who they are |
| Send Day | Gap | Notes | |
|---|---|---|---|
| Email 1 | Day 1 | — | First touch |
| Email 2 | Day 4 | +3 days | New evidence angle |
| Email 3 | Day 9 | +5 days | Different pain point |
| Email 4 | Day 16 | +7 days | Industry insight |
| Email 5 | Day 25 | +9 days | Direct question |
| Breakup | Day 35 | +10 days | Close the loop |
Gaps increase over time. Persistent but not annoying.
| Angle Type | Description | Example |
|---|---|---|
| New evidence | Case study, data point, recent result | "Since my last note, we helped [Company] reduce [metric] by [%]" |
| Different pain | Alternative problem in their world | "Setting aside [topic A] — are you dealing with [topic B]?" |
| Industry insight | Something notable about their space | "Saw [industry trend]. Most teams are responding by [approach]" |
| Direct question | Simple ask without buildup | "[Name], quick one: who handles [function] at [Company]?" |
| Reverse ask | Request for referral | "If this isn't your area, who would you point me to?" |
| Social proof | Relevant peer doing it | "[Similar company] just went through this — here's what worked" |
Tier 1: Segment-Level (Minimum)
Tier 2: Company-Level (Standard)
Tier 3: Individual-Level (Premium)
| Source | What You Find | How to Use |
|---|---|---|
| LinkedIn profile | Role, tenure, content they share | Role-specific opener, reference their posts |
| Company blog | Priorities, culture, technology choices | Connect your solution to their stated priorities |
| Job postings | Growth areas, pain points, tech stack | "You're hiring for X, which usually means..." |
| Press/news | Funding, partnerships, launches | Trigger-based openers |
| GitHub/tech blogs | Technical decisions, stack choices | Technical relevance and credibility |
| Podcast/talks | Opinions, expertise areas | "Your point about X in [talk] resonated..." |
| Component | What | Why |
|---|---|---|
| Dedicated sending domain | mail.yourdomain.com or outreach.yourdomain.com | Protects primary domain reputation |
| SPF record | DNS TXT record authorizing sending servers | Proves you are authorized to send |
| DKIM signing | Cryptographic signature on emails | Proves emails were not modified in transit |
| DMARC policy | DNS record specifying SPF/DKIM enforcement | Tells receiving servers how to handle failures |
| Domain warmup | 4-6 weeks of gradually increasing volume | Builds sender reputation with ISPs |
| Week | Daily Volume | Notes |
|---|---|---|
| 1 | 10-20 | Send to engaged contacts only |
| 2 | 20-40 | Mix of warm and cold contacts |
| 3 | 40-70 | Begin cold outreach at low volume |
| 4 | 70-100 | Monitor bounce rates closely |
| 5-6 | 100-150 | Increase if bounce rate < 3% |
| 7+ | 150-200 max | Steady state for cold outreach |
Required for all commercial email to US recipients:
Required for email to EU/EEA residents:
Required for commercial electronic messages to Canadian recipients:
| Pattern | Why It Fails |
|---|---|
| "I hope this email finds you well" | Instant signal that this is templated mass outreach |
| "I wanted to reach out because..." | Three words of nothing before saying anything |
| Opening with "My name is X and I work at Y" | They can see your name. Start with something useful. |
| Feature dump in email 1 | Nobody cares about features when they do not trust you yet |
| HTML templates with logos and colors | Looks like marketing, gets spam-filtered |
| Fake Re:/Fwd: subject lines | Deceptive, destroys trust |
| "Just checking in" follow-ups | Adds no value, removes credibility |
| Social proof without context | "We work with 500 companies" means nothing without relevance |
| Long-form case study in email 1 | Save it for follow-up |
| Passive CTAs ("Let me know if you're interested") | Weak. Ask a direct question or propose a specific step. |
| Multiple CTAs in one email | Creates decision paralysis. One ask per email. |
| Sending from your primary domain | Risks your entire domain reputation |
Send from a real person, not a company alias — "sarah@mail.acme.com" outperforms "sales@acme.com" every time.
Read the email aloud before sending — If you hear yourself droning, cut. If it sounds like a brochure, rewrite.
Time your sends — Tuesday through Thursday, 8-10 AM in the prospect's timezone, produces the highest open rates for B2B.
Verify emails before campaigns — A 5% bounce rate damages your domain reputation. Verify every address.
Track reply rate, not open rate — Open tracking is unreliable (privacy features block tracking pixels). Reply rate is the metric that matters.
Build sequences, not individual emails — Most replies come from follow-ups, not the first email. Plan the full sequence before writing.
Document your playbook — Every winning email, subject line, and angle should be documented for the team. Build institutional knowledge.
Respect opt-outs immediately — Not just legally required, but professionally essential. Process within 24 hours.
Rotate sending domains — Use 2-3 sending domains to distribute volume and protect reputation.
Segment relentlessly — A generic template sent to 1,000 people will underperform a personalized email sent to 50 who match your ideal profile.
| Symptom | Likely Cause | Fix |
|---|---|---|
| Open rate below 15% | Subject lines too long, spammy, or generic | Test 2-4 word internal-email-style subjects. Run subject_line_scorer.py. |
| Opens but reply rate below 1% | Email body lacks relevance or CTA is too high-friction | Rewrite opener about their world. Use a question CTA, not a statement. |
| Emails landing in spam (2026) | Missing SPF/DKIM/DMARC or RFC 8058 one-click unsubscribe | Gmail/Yahoo/Microsoft now reject non-compliant bulk mail. Run deliverability_checker.py. |
| Bounce rate above 3% | Unverified email list or role-based addresses | Verify every address before sending. Remove catch-alls and role accounts. |
| Spam complaint rate above 0.10% | Irrelevant targeting or too-frequent sends | Gmail enforces 0.10% threshold as of 2026. Improve targeting and reduce volume per domain. |
| Replies but wrong outcome | CTA mismatch with funnel stage | Align CTA friction to prospect readiness. C-suite wants a question; managers accept a demo link. |
| Domain blacklisted | Sending from primary domain or too-high volume | Use dedicated sending subdomains. Warm new domains 4-6 weeks. Max 100 emails/day/address. |
In Scope:
Out of Scope:
Limitations:
scripts/subject_line_scorer.py)Scores cold email subject lines on deliverability, spam risk, and open-rate potential using deterministic heuristics.
python scripts/subject_line_scorer.py "quick question"
python scripts/subject_line_scorer.py --file subjects.txt --jsonscripts/deliverability_checker.py)Audits email content for spam triggers, HTML complexity, link density, and compliance against 2025-2026 Gmail/Yahoo/Microsoft requirements.
python scripts/deliverability_checker.py email.txt
python scripts/deliverability_checker.py email.txt --domain yourdomain.com --jsonscripts/sequence_optimizer.py)Analyzes cold email sequence performance data against industry benchmarks. Diagnoses open rate, reply rate, bounce rate, and cadence issues.
python scripts/sequence_optimizer.py sequence_data.json
python scripts/sequence_optimizer.py --sample --json© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 3 other files (scripts) in marketing/cold-email of borghei/Claude-Skills.
Open the folder on GitHubat commit 4a698e8
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cold Email this skillborghei/Claude-Skills | 881 | — | ~5.7k | Automated safety check: Pass | MIT | |
| Cold Outbound Optimizerericosiu/ai-marketing-skills | 3.6k | 1 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Prospectingcoreyhaines31/marketingskills | 54k | — | ~4.9k | Automated safety check: Pass | MIT | |
| Sales OsromangojiberryAI/gojiberryai-sales-os | 138 | — | ~2k | Automated safety check: Pass | MIT | |
| ProspectingCesarjoquin/Marketing-Skills | 200 | 1 repos | ~3.8k | Automated safety check: Pass | MIT | |
| Cold Outreach Personalizeraiskilloftheweek/claude-ai-skill-of-the-week | 146 | — | ~2.6k | Automated safety check: Pass | None |
ericosiu/ai-marketing-skills
Design, analyze, and optimize cold outbound email campaigns for Instantly.
coreyhaines31/marketingskills
When the user wants to find, qualify, and build a list of prospects to reach out to, across B2B SaaS, general B2B, or local small businesses.
romangojiberryAI/gojiberryai-sales-os
A complete outbound sales department in one skill. An agent skill from romangojiberryAI/gojiberryai-sales-os.
Cesarjoquin/Marketing-Skills
When the user wants to find, qualify, and build a list of prospects to reach out to — across B2B SaaS, general B2B, or local small businesses.
aiskilloftheweek/claude-ai-skill-of-the-week
Generates hyper-personalized cold outreach messages (email, LinkedIn DM, connection request) from raw prospect research.
gmapsscraper/google-maps-agent-skills
Extract verified business email addresses from Google Maps listings.
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
borghei/Claude-Skills
Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
borghei/Claude-Skills
OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.
Categories
Write and optimize B2B cold email outreach sequences that get replies, covering personalization, follow-up cadence, deliverability, and compliance. Cold Email is an agent skill from borghei/Claude-Skills. Write and optimize B2B cold email outreach sequences that get replies, covering personalization, follow-up cadence, deliverability, and compliance.
Cold Email fits situations like: writing cold outreach; prospecting/SDR emails; building outbound sequences.
Run `npx skills add borghei/Claude-Skills --skill cold-email -a claude-code`. Or copy the skill folder (marketing/cold-email in borghei/Claude-Skills) into .claude/skills/cold-email in your project. Claude Code loads it when a task matches its description.
Run `npx skills add borghei/Claude-Skills --skill cold-email -a codex`. Or copy the skill folder (marketing/cold-email in borghei/Claude-Skills) into .agents/skills/cold-email in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/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.
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 (python). Our summary lists: Python 3.
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.
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.
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.
About 5.7k tokens (SKILL.md is roughly 23k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Cold Email: Cold Outbound Optimizer (ericosiu/ai-marketing-skills, 3.6k stars), Prospecting (coreyhaines31/marketingskills, 54k stars), Sales Os (romangojiberryAI/gojiberryai-sales-os, 138 stars) and Prospecting (Cesarjoquin/Marketing-Skills, 200 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 881 GitHub stars. The repository holds 349 skills in this directory. The repository was last updated on October 7, 2026.
Source: borghei/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.