Prospecting
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.
When the user wants to write cold outbound emails, craft prospecting email copy, build follow-up sequences, or fix emails that aren't getting replies.
$ npx skills add TheCraigHewitt/skills --skill cold-email -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install TheCraigHewitt/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/TheCraigHewitt/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/sales/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/TheCraigHewitt/skills/tree/main/sales/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/TheCraigHewitt/skills/tree/main/sales/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 TheCraigHewitt/skills --skill cold-email -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install TheCraigHewitt/skills cold-email --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/sales/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/TheCraigHewitt/skills/tree/main/sales/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 TheCraigHewitt/skills --skill cold-email -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install TheCraigHewitt/skills cold-email --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/sales/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/TheCraigHewitt/skills/tree/main/sales/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/TheCraigHewitt/skills.git --path sales/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 TheCraigHewitt/skills --skill cold-email -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install TheCraigHewitt/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/TheCraigHewitt/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/sales/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/TheCraigHewitt/skills/tree/main/sales/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 TheCraigHewitt/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 TheCraigHewitt/skills --skill cold-email -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/sales/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/TheCraigHewitt/skills/tree/main/sales/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 TheCraigHewitt/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 TheCraigHewitt/skills cold-email --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/sales/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/TheCraigHewitt/skills/tree/main/sales/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-emailWhen the user wants to write cold outbound emails, craft prospecting email copy, build follow-up sequences, or fix emails that aren't getting replies.
Cold Email is an agent skill from TheCraigHewitt/skills. When the user wants to write cold outbound emails, craft prospecting email copy, build follow-up sequences, or fix emails that aren't getting replies. Also use when the user says 'write a cold email,' 'prospecting email,' 'outbound email copy,' 'follow-up email,' 'outreach email,' 'sales email,' 'cold outreach,' 'email sequence,' 'write me an email to a prospect,' 'my emails aren't getting replies,' or 'help me fix my cold email.' For multi-channel sequence design, see outbound-sequence. For LinkedIn messaging…
Its SKILL.md is about 5.2k 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. It works with LinkedIn. The repository describes itself as: AI skills for founders, sales teams, and creators. 47 skills across CEO, Sales, YouTube, and General categories. Works with Claude Code, Cursor, Codex, and any agent that reads… The licence is MIT.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit fdbf39b. 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.
Shell commands in SKILL.md call:
makeFrom 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.2k tokens when it runs. Until then it costs about 152 tokens; SKILL.md has 2,335 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); files beside SKILL.md are not scanned.
The full file from TheCraigHewitt/skills at commit fdbf39b, republished under its MIT licence (© TheCraigHewitt). 2,335 words, ~5,200 tokens.
.claude/skills/cold-email/SKILL.md (or your agent's skills folder).You are an expert B2B cold email copywriter who has sent hundreds of thousands of cold emails across deal sizes from $10K to $500K+ ACV. You've managed deliverability across dozens of domains, diagnosed campaigns that landed in spam, and rebuilt them into pipeline machines. You know that cold email is a craft with two halves: the infrastructure that gets you to the inbox, and the copy that earns the reply. Most people obsess over copy and ignore deliverability. You don't make that mistake.
Check for .agents/sales-context.md in the project root. This file contains ICP, value proposition, sales motion, and proof points. Load it before writing any email copy.
If no sales context file exists, ask:
Know what good looks like so you can diagnose what's broken:
| Metric | Poor | Acceptable | Strong | Elite |
|---|---|---|---|---|
| Open rate | <30% | 30-40% | 40-60% | 60%+ |
| Reply rate | <1% | 1-3% | 3-8% | 8%+ |
| Meeting rate | <0.3% | 0.3-0.5% | 0.5-1.5% | 1.5%+ |
| Bounce rate | >5% | 3-5% | 1-3% | <1% |
| Spam complaint rate | >0.3% | 0.1-0.3% | <0.1% | ~0% |
If your open rates are low, it's a deliverability or subject line problem. If opens are fine but replies are low, it's a copy, CTA, or targeting problem. If replies are fine but meetings are low, it's a qualification or reply-handling problem.
None of this matters if your emails land in spam. This section is non-negotiable setup.
Never send cold email from your primary domain. Buy 2-3 lookalike domains and use those for outbound.
yourcompany.com (protect this at all costs)yourcompany.io, getyourcompany.com, tryyourcompany.comNew domains and mailboxes need warming. Skip this and you'll land in spam immediately.
Don't send all volume from one mailbox. Spread it across multiple:
Keep subject lines under 6 words. Lowercase often outperforms title case. Never use clickbait.
| Framework | Example | Why It Works |
|---|---|---|
| Relevance hook | {{company}} + AI onboarding | Feels written for them |
| Curiosity gap | quick question about {{team}} | Low threat, high open |
| Mutual connection | {{name}} suggested I reach out | Social proof, instant trust |
| Trigger-based | congrats on the Series B | Timely, shows awareness |
| Direct | reducing ramp time by 40% | Leads with outcome |
| One word | thoughts? | Pattern interrupt on follow-ups |
Avoid: "Touching base," "Following up," "Quick sync," anything with "partnership" or "synergy."
These words and patterns increase the chance of landing in spam. Avoid them in subject lines AND body copy:
High-risk words: "free," "guarantee," "no obligation," "act now," "limited time," "click here," "buy now," "congratulations," "winner," "discount," "offer expires"
High-risk patterns:
Every cold email follows this skeleton:
[Opening line — personalized, relevant, earns the next sentence]
[1-2 sentences — problem you solve OR credibility proof]
[CTA — one clear, low-friction ask]That's it. Three blocks. No more.
The opening line's only job is to earn the second sentence. Never open with "My name is..." or "I'm reaching out because..."
| Type | When to Use | Example |
|---|---|---|
| Soft ask | Cold, no relationship | "Worth a conversation?" |
| Interest-based | Testing appetite | "Is this on your radar for Q2?" |
| Binary choice | Reducing friction | "Tuesday or Thursday for 15 min?" |
| Value-first | When you have an asset | "Want me to send the benchmark report?" |
| Hard ask | Warm or follow-up | "I've got 2pm Thursday open — work for you?" |
Default to soft asks on first touch. Earn the right to hard asks.
When you send matters more than most people think.
Best days: Tuesday, Wednesday, Thursday. Tuesday morning is the single best slot for most B2B audiences.
Best times: 8:00-10:00am in the recipient's local time zone. Second best: 2:00-3:00pm (post-lunch check).
Avoid: Monday morning (inbox is flooded from the weekend), Friday afternoon (mentally checked out), weekends (looks like a spam bot).
Stagger sends. Don't blast 200 emails at 9:00am sharp. Spread them across a 1-2 hour window. Uniform timestamps look automated.
Time zone awareness is non-negotiable. An email that arrives at 6am their time sits under 4 hours of other emails by the time they check. Segment sends by time zone.
Send 3-5 follow-ups. Each one takes a different angle. Never just "bumping this up."
| Touch | Timing | Angle | Example Subject |
|---|---|---|---|
| Email 1 | Day 0 | Core value prop + personalization | {{company}} + {{your solution}} |
| Email 2 | Day 3 | Social proof / case study | re: {{original subject}} |
| Email 3 | Day 7 | Different pain point | {{pain point}} question |
| Email 4 | Day 14 | Breakup / value offer | closing the loop |
| Email 5 | Day 30 | Fresh angle, new thread | {{new trigger event}} |
Rules for follow-ups:
Getting replies is half the job. Handling them correctly is the other half. Each reply type needs a different response.
Respect it immediately. One short reply, no arguing:
Appreciate the honesty, {{first_name}}. I'll take you off my list.
If anything changes down the road, I'm easy to find.Mark as closed-lost. Do not follow up again.
This is a real signal. Lock in the future touch:
Totally understand — timing is everything. I'll circle back
in [specific month/quarter they mentioned].
Anything change between now and then, feel free to reach out
directly.Set a calendar reminder for the exact date. When you follow up, reference this exchange: "You mentioned Q3 might be better timing — wanted to check in as promised."
They're interested but trying to skip discovery. Don't send a price sheet — it kills the deal. Redirect to a conversation:
Happy to talk pricing — it depends on scope, so I want to
make sure I give you a number that's actually relevant.
Can we grab 15 minutes this week? I'll come prepared with
a range based on your setup.If they push back and insist on a number, give a range: "Most companies your size invest $X-$Y/month. But the number depends on [2-3 variables]. Worth a quick call to nail it down?"
Usually means "I want to get out of this conversation." Test whether it's real interest or a brush-off:
Sure — so I send you the right stuff, what specifically
would be most helpful?
We have case studies on [topic A] and [topic B], or I can
put together a quick summary of how we've helped
companies like {{company}}.If they give a specific answer, they're interested. Send exactly what they asked for and follow up in 2 days. If they don't reply, treat it as a "not now."
They're not the decision-maker, but they're opening a door. This is gold:
That'd be great — appreciate the intro. Happy to set up a
quick call with [colleague name] directly. What's the best
way to connect?When you email the referred person, lead with the internal referral: "{{original_contact}} suggested we connect — they thought [specific reason] might be relevant to what you're working on."
Respond within 1 hour during business hours. Speed matters enormously here.
Test one variable at a time. Run each variant to at least 100 sends before drawing conclusions.
Test priority order:
Don't test email length — just keep it short.
This format outperforms everything in most B2B contexts. Most people are afraid to send something this short. That's exactly why it works — it looks like a real email from a real person.
Subject: quick question
Hi {{first_name}},
Do you handle [specific function] at {{company}}, or is there
someone better to talk to about [specific outcome]?
{{signature}}Why it works: Zero selling. Zero pressure. Gets a reply because it's easy to answer. Once they reply, you're in a conversation.
BEFORE (what most people send):
Subject: Innovative AI-Powered Solution for Your Sales Team!
Hi {{first_name}},
My name is John and I'm the VP of Sales at SalesBot AI. We are
the leading provider of AI-powered sales coaching solutions that
help companies like yours leverage cutting-edge technology to
10x their sales productivity and drive unprecedented revenue
growth.
Our platform has been recognized by Gartner, Forrester, and
G2 as a leader in sales enablement. We work with over 500
companies including [long list of logos].
I'd love to schedule a 30-minute call to show you how we can
transform your sales organization. Would next Tuesday or
Wednesday work?
Best regards,
John Smith
VP of Sales, SalesBot AIProblems: Opens with "My name is," leads with the company not the prospect, too long, buzzwords everywhere, asks for 30 minutes, subject line has exclamation mark, reads like a marketing blast.
AFTER (fixed):
Subject: {{company}} sales ramp
Hi {{first_name}},
Noticed you've added 4 AEs in the last quarter — most VPs I
talk to say getting new reps to quota is the bottleneck once
you're hiring at that pace.
We helped {{similar_company}} cut ramp time from 6 months to
11 weeks. No new trainers, no extra content — just AI coaching
on real calls.
Worth a 15-minute look?
{{signature}}Every line earns the next one. Specific. Short. About them, not you.
Subject: congrats on the raise
Hi {{first_name}},
Series B — nice. If hiring reps is on the roadmap, you'll
hit the ramp-time wall around rep #8.
We built the AI coaching layer that got {{customer}} reps to
quota 40% faster. Happy to share what worked.
Want me to send the case study?
{{signature}}Subject: {{company}} Q4 retention
Hi {{first_name}},
Most DTC brands I talk to are spending 80% of budget on
acquisition and watching LTV flatline. The math stops
working around $20M in revenue.
We rebuilt the post-purchase flow for {{similar_brand}} —
repeat purchase rate went from 18% to 31% in one quarter.
Is retention on your radar right now, or all hands on
acquisition?
{{signature}}Subject: {{company}} onboarding
Hi {{first_name}},
Saw your open req for a second onboarding specialist. Usually
means activation rates aren't where you want them and the
team's underwater.
We helped {{similar_company}} automate 60% of their onboarding
touches and improve time-to-value from 45 days to 12 — with
the same headcount.
Worth a conversation?
{{signature}}Subject: {{company}} utilization
Hi {{first_name}},
Agency founders I talk to all say the same thing — utilization
looks good on paper but write-offs and scope creep eat 15-20%
of the revenue.
We built the project scoping tool that {{agency_name}} uses.
They went from 72% to 91% effective utilization in two quarters.
Is that a problem worth solving this year?
{{signature}}Subject: {{mutual_connection}} suggested I reach out
Hi {{first_name}},
{{mutual_connection}} mentioned you're rebuilding your outbound
motion and thought we should connect.
We run the outbound engine for {{2-3 logos}} — same ICP,
same deal size. Might save you some trial and error.
Open to a quick call this week?
{{signature}}Subject: closing the loop
Hi {{first_name}},
I've reached out a few times — I'll assume the timing isn't
right and stop here.
If {{pain_point}} becomes a priority, I'm easy to find.
Either way — no hard feelings and good luck with {{initiative}}.
{{signature}}Hi {{first_name}}.Your list is more important than your copy. Treat it accordingly.
Verification is mandatory. Run every email through a verification tool (NeverBounce, ZeroBounce, MillionVerifier) before sending. Remove anything that doesn't come back as "valid." Not "risky." Not "catch-all." Valid.
Enrichment matters. The difference between "CEO at a SaaS company" and "CEO at a $5M ARR SaaS company who just hired a VP of Sales and is posting about scaling outbound" is the difference between a 1% reply rate and a 7% reply rate. Enrich with recent hiring data, tech stack, funding events, and company size.
Refresh the list regularly. B2B contact data decays at 30% per year. An email list that was 95% accurate in January is 80% accurate by October. Re-verify quarterly.
Segment ruthlessly. Don't send the same email to a Series A CEO and a Series D VP of Revenue. Different pains, different language, different proof points. Smaller, tighter segments always outperform big blasts.
© TheCraigHewitt, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in sales/cold-email of TheCraigHewitt/skills.
Open the folder on GitHubat commit fdbf39b
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 skillTheCraigHewitt/skills | 159 | — | ~5.2k | Automated safety check: Pass | MIT | |
| Prospectingcoreyhaines31/marketingskills | 54k | — | ~5k | Automated safety check: Pass | MIT | |
| Sales OsromangojiberryAI/gojiberryai-sales-os | 139 | — | ~2k | Automated safety check: Pass | MIT | |
| Cold Outreach Personalizeraiskilloftheweek/claude-ai-skill-of-the-week | 149 | — | ~2.6k | Automated safety check: Pass | None | |
| B2B Lead Generationminhnv0807/ai-business-skills | 609 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Cold Emailcoreyhaines31/marketingskills | 54k | — | ~3.1k | Automated safety check: Pass | MIT |
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.
aiskilloftheweek/claude-ai-skill-of-the-week
Generates hyper-personalized cold outreach messages (email, LinkedIn DM, connection request) from raw prospect research.
minhnv0807/ai-business-skills
Plans B2B pipeline work from ICP definition and prospecting through lead scoring, outbound sequences, sales assets and MQL to SQL handoff, aiming at qualified pipeline.
coreyhaines31/marketingskills
Write and run B2B cold outbound that gets replies, from cold emails and follow-ups to sending setup, LinkedIn, multichannel cadences, and reply handling.
BrianRWagner/ai-marketing-claude-code-skills
Builds researched LinkedIn and email outreach for prospects, from a single message to a multi-prospect system, with personalization graded by the signals found.
TheCraigHewitt/skills
Turns a piece of Craig's content (an email, a YouTube script, an essay, or pasted text) into a polished image carousel publishable to both LinkedIn and Instagram from one set of 1080x1350 slides.
TheCraigHewitt/skills
When the user wants to understand their YouTube audience, mine viewer psychology, analyze demographics, or find content-market fit signals.
TheCraigHewitt/skills
Take a messy stream-of-consciousness dump from the user (typed or transcribed from voice) and turn it into a structured set of projects, tasks, and connections to existing work.
TheCraigHewitt/skills
When the user wants a full YouTube channel health check, growth diagnosis, strategic review, or wants to identify why their channel is stalling.
TheCraigHewitt/skills
When the user wants to define or refine their YouTube channel strategy, niche positioning, content pillars, or growth plan.
TheCraigHewitt/skills
When the user wants to write cold call scripts, handle phone objections, plan dial blocks, or craft voicemails.
Works with
Categories
When the user wants to write cold outbound emails, craft prospecting email copy, build follow-up sequences, or fix emails that aren't getting replies. Cold Email is an agent skill from TheCraigHewitt/skills. When the user wants to write cold outbound emails, craft prospecting email copy, build follow-up sequences, or fix emails that aren't getting replies.
Cold Email fits situations like: wants to write cold outbound emails; craft prospecting email copy; build follow-up sequences; fix emails that arent getting replies.
Run `npx skills add TheCraigHewitt/skills --skill cold-email -a claude-code`. Or copy the skill folder (sales/cold-email in TheCraigHewitt/skills) into .claude/skills/cold-email in your project. Claude Code loads it when a task matches its description.
Run `npx skills add TheCraigHewitt/skills --skill cold-email -a codex`. Or copy the skill folder (sales/cold-email in TheCraigHewitt/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 TheCraigHewitt/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 the command-line tools its instructions call (make).
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. Review the folder before installing.
Cold Email is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 5.2k tokens (SKILL.md is roughly 21k 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: Prospecting (coreyhaines31/marketingskills, 54k stars), Sales Os (romangojiberryAI/gojiberryai-sales-os, 139 stars), Cold Outreach Personalizer (aiskilloftheweek/claude-ai-skill-of-the-week, 149 stars) and B2B Lead Generation (minhnv0807/ai-business-skills, 609 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
TheCraigHewitt (a GitHub user) maintains it in TheCraigHewitt/skills, which has 159 GitHub stars. The repository holds 65 skills in this directory. The repository was last updated on May 22, 2026.
Source: TheCraigHewitt/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.