Cold email personalizer
Skill buildwithreef/claude-skills/skills/cold-email-personalizer
Researches a prospect and writes short, personalized cold emails using proven frameworks (observation → implication → question, PAS), plus a three-touch follow-up sequence. Use when the user wants to write a cold email or outreach message, personalize outreach to a specific business, or says "write a cold email to this company" or "help me reach out to this prospect".From its SKILL.md
npx -y skills add buildwithreef/claude-skills --skill cold-email-personalizerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
4.5 KB, ~1.0k tokens by cl100k_base, as published. Nobody here has run it
Cold Email Personalizer
Personalization is not knowing their name. It's one observation about their business that's true, specific, and slightly uncomfortable to ignore — found in ten minutes, delivered in ninety words.
Step 1 — Research (10 minutes, hard cap)
Work through in order; stop when you have two strong observations:
- Their website: what they sell, to whom, what's obviously broken or missing (no pricing, dead blog, no mobile CTA, 2019 copyright).
- Their reviews (Google/Yelp): what customers praise (their real differentiator — often not what the site leads with) and what they complain about (a pain they feel weekly: "impossible to reach," "slow quotes").
- Growth signals: hiring pages, new location, running ads (check the site with an ad-library search), recent press.
- The owner: name findable? LinkedIn activity? Anything they've said publicly about the business?
An observation qualifies if the owner would read it and think "huh, they actually looked." "Love what you're doing!" fails; "your last 6 Google reviews all mention how hard it is to get a callback" passes.
Step 2 — Pick a framework (by what research found)
- Observation → implication → question (default): "Noticed [true thing] → which usually means [cost/risk in their terms] → is that something you're feeling?"
- PAS (when reviews handed you a bleeding pain): name the Problem in their customers' words, Agitate with what it costs, offer the Solve in one line.
- Poke the bear (confident senders, competitive markets): a question that challenges the status quo — "Who answers your phone when the crew's on a roof?"
- 1–2–3 (thin research): one observation, two sentences of concrete value, one question.
Step 3 — Write it under the rules
- Under 90 words. Count them.
- Subject: 2–4 words, lowercase, internal-memo energy — "missed calls", "your google reviews", "quick question re: quotes". Never clever, never salesy.
- Line 1 = the observation. Never "I hope this finds you well," never your name or company (the signature has that).
- One idea per email. One CTA, and it's an interest question — "Worth a look?" / "Open to seeing how that works?" — never "do you have 15 minutes Tuesday at 2?"
- No links in the first email (spam filters and suspicion). No attachments. Plain text, no images, no HTML buttons.
- Read-aloud test: if it doesn't sound like something you'd say across a counter, rewrite it.
- Never fake familiarity ("been following you for a while") and never open with an apology ("sorry to bother you").
Step 4 — The sequence (3 touches, then out)
- Day 1: the email.
- Day 4 — the bump: reply to your own thread, one line only: "Any thoughts on this?" or a second, smaller observation. No re-pitch, no "just following up on my previous email."
- Day 9 — the breakup: close the loop with a takeaway and zero guilt: "Guessing the timing's off — I'll leave it here. If [pain] ever makes the list, this is what I do." Breakups routinely out-reply the first email.
- No reply after three: stop. Recycle the list in a quarter with a new observation.
Step 5 — Deliver
**Research notes:** [3–5 bullets: observations found + which was used]
**Framework:** [name + why]
**Subject:** [subject]
[email body]
**Day 4 bump:** [one line]
**Day 9 breakup:** [2–3 lines]
**Why this works:** [2 bullets tying lines to research]
Deliverability floor (say it once, briefly)
Sending domain warmed up, SPF/DKIM/DMARC set, under ~30–50 cold sends/day per inbox, and a list they're legally allowed to email (B2B norms vary by country — flag, don't lecture). The best copy in a spam folder converts at zero.
What not to do
- Don't compliment-open ("Congrats on the new website!") — it's the most common spam tell in 2026.
- Don't mention your company name before the signature.
- Don't stack two CTAs or add a calendar link on touch one.
- Don't personalize with trivia (their college, the weather). Business observations only.
Built by Reef — AI systems for small business → https://buildwithreef.com
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.