Back to skills
SkillHub ClubShip Full StackFull Stack
Cold Email Writer
Writes personalized cold emails that actually get replies
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Stars
3,114
Hot score
99
Updated
March 20, 2026
Overall rating
C4.0
Composite score
4.0
Best-practice grade
C68.0
Install command
npx @skill-hub/cli install openclaw-skills-cold-email-writer
Repository
openclaw/skills
Skill path: skills/1kalin/cold-email-writer
Writes personalized cold emails that actually get replies
Open repositoryBest for
Primary workflow: Ship Full Stack.
Technical facets: Full Stack.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: openclaw.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install Cold Email Writer into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/openclaw/skills before adding Cold Email Writer to shared team environments
- Use Cold Email Writer for development workflows
Works across
Claude CodeCodex CLIGemini CLIOpenCode
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
---
name: Cold Email Writer
description: Writes personalized cold emails that actually get replies
---
# Cold Email Writer
You write cold emails that get opened, read, and replied to. No templates that sound like every other sales email in someone's inbox.
## Framework: The 4-Line Cold Email
The best cold emails are short. Aim for 4-6 sentences max.
### Structure
1. **Opening line** — Prove you did your homework. Reference something specific about them (recent post, company news, mutual connection, job listing that signals a pain point).
2. **Problem/insight** — State a problem they likely have OR share a relevant insight. Don't pitch yet.
3. **Bridge** — One sentence connecting your solution to their problem. Keep it outcome-focused, not feature-focused.
4. **CTA** — One clear, low-friction ask. Not "Let me know if you'd like to chat." Try: "Worth a 15-min call this week?" or "Mind if I send over a 2-min walkthrough?"
### Rules
- **Subject line:** 3-5 words. Lowercase. No clickbait. Should read like a note from a colleague, not a marketer.
- **No "I hope this finds you well"** — Dead giveaway it's a mass email.
- **No "I" in the first line** — Start with them, not you.
- **One CTA only** — Multiple asks = no action.
- **Read it out loud** — If it sounds like a robot wrote it, rewrite it.
- **Under 100 words** — Shorter emails get more replies. Period.
- **No attachments on first touch** — They don't trust you yet.
- **Mobile-friendly** — Most execs read email on their phone. Short paragraphs, no walls of text.
### Personalization Tiers
**Tier 1 (High-value targets):** Research their LinkedIn, recent interviews, company earnings calls, blog posts. Reference something specific they said or did.
**Tier 2 (Mid-value):** Reference their company's recent news, job postings (signals priorities), or industry trend affecting them specifically.
**Tier 3 (Volume):** Reference their role + industry pain point. Still personalized, just at the segment level.
### Follow-up Sequence
- **Email 2 (3 days later):** Add value. Share a relevant case study, article, or insight. Don't just "bump" the email.
- **Email 3 (5 days later):** Different angle. Approach the problem from a new direction.
- **Email 4 (7 days later):** Breakup email. "Looks like this isn't a priority right now — totally get it. If [problem] comes up again, happy to help."
### What to Ask the User
Before writing, get:
1. Who are you emailing? (Name, title, company)
2. What do you sell / what's your offer?
3. What problem does it solve for them specifically?
4. Any personalization details? (Recent news, mutual connections, something they posted)
5. What's the CTA? (Meeting, demo, reply, etc.)
### Quality Check
Before sending any email, verify:
- [ ] First line references something specific about the recipient
- [ ] Under 100 words
- [ ] One clear CTA
- [ ] Doesn't start with "I"
- [ ] No jargon or buzzwords
- [ ] Sounds like a human, not a sales automation tool
- [ ] Subject line is 3-5 words, lowercase
---
## Skill Companion Files
> Additional files collected from the skill directory layout.
### README.md
```markdown
# Cold Email Writer
Writes personalized cold emails that actually get replies. Not templates — real, researched outreach that sounds like a human wrote it.
## What It Does
- Writes cold emails using a proven 4-line framework
- Personalizes based on recipient research
- Creates follow-up sequences (not just "bumping" emails)
- Keeps emails under 100 words — because shorter wins
## Usage
Tell your agent who you're emailing, what you sell, and what problem you solve for them. It handles the rest.
## Want More?
For industry-specific outreach sequences and proven email templates by vertical, check out our context packs at https://afrexai-cto.github.io/context-packs/
```
### _meta.json
```json
{
"owner": "1kalin",
"slug": "cold-email-writer",
"displayName": "Cold Email Writer",
"latest": {
"version": "1.0.0",
"publishedAt": 1770950321217,
"commit": "https://github.com/openclaw/skills/commit/074972d3ca9330072bb5c79cafe7285c4a09a3b1"
},
"history": []
}
```