Turn one signal into a cold email that earns a reply.
From a prospect and a specific angle, writes a short email or 3-touch sequence built on one idea, no filler.
Inside: The one-idea rule, an earned opener, a soft CTA, and a 3-touch sequence.
Install it in one line, or paste it in.
~/.claude/skills/ and runs automatically when it is relevant.Connect your context. Set it to your motion.
it reads the account, past touches, and open opportunity context so the email fits the relationship.
pulls the role, the tech in use, and recent signals so the opener is specific, not generic.
drops the finished touches straight into your cadence with the timing set.
This was built for B2B outbound into a named persona. Set these to your motion:
Write to any persona you like. The skill builds the email around your offer and your signal, not a template someone else outgrew.
| Set this | What it is | Default / Example |
|---|---|---|
| PERSONA | who you are writing to | VP SalesRevOps leadHead of Support |
| OFFER | the one problem you solve | "reps waste hours on manual follow-up" |
| SIGNAL | the reason to reach out now | hiringfundinga launcha role change |
| PROOF | one credible, non-braggy result | illustrative rangenot a hard promise |
| CTA_STYLE | how soft the ask is | "worth a look?" vs a time request |
| SEQUENCE_LEN | single touch or a series | 1 or 3 |
| CRM | your CRM connector | a CRM you already run |
| SEQUENCER | where the touches land | a sequencer you already run |
Everything the skill does, in full.
Takes a prospect and a specific angle, a trigger, a role, a stated priority, a piece of news, and writes a short cold email built around one idea. Relevant opener, one problem worth their attention, a soft ask that is easy to say yes to. Ask for a sequence and it returns three touches that build instead of repeat.
- 1One idea per email
Every email carries exactly one problem and one ask. If a second idea shows up, it moves to touch two or gets cut. Two ideas in one email means the reader picks neither.
- 2Relevant opener, earned not flattered
The first line names the signal, not the reader's greatness. No "love what you are building." A good opener proves you looked: the role they just took, the thing they just shipped, the priority they said out loud.
- 3The soft CTA
Close with an ask that costs the reader nothing to answer. Interest-first ("worth a quick look?") beats calendar-first on a cold first touch. Save the time request for when they lean in.
- 43-touch sequence that builds
When asked for a sequence, each touch adds a new angle: touch one is the signal and the problem, touch two is one proof point or a different lens, touch three is a short, graceful last try that leaves the door open. No "just bumping this to the top of your inbox."
- 5Length and voice guard
Under 90 words for a first touch. Short sentences. No jargon the reader would not use themselves. Read it aloud in your head; if it sounds like a brochure, it gets cut.
- One idea and one ask per email, always. A second idea moves or dies.
- The opener names a real, specific signal, never generic flattery.
- No proof point stated as a hard guarantee. Ranges are illustrative and labeled.
- No filler openers ("hope this finds you well") and no fake-urgency closers.
COLD EMAIL · VP Sales · signal: hired 4 AEs last month Subject: onboarding 4 at once Saw the team went from 6 reps to 10 in a month. Fast. The usual tax on that: new reps improvising follow-up until month three, and pipeline slipping while they learn the motion. We help teams cut that ramp so touch quality holds from week one. Worth a look, or is ramp already handled? --- Touch 2 (day 4) --- One thing that tends to move the needle for teams mid-hire: [angle]. Happy to send the one-pager, no call needed. --- Touch 3 (day 9) --- I will get out of your inbox. If ramp is a Q3 problem, I am here. If not, no hard feelings.
Where an operator takes this next.
A sharp email by hand is the floor. Here is where it goes next.
The point is not to generate more email. It is to make each one land on a reason the reader recognizes, then get it out the door without leaving your stack.
Feed the Untouched rows from a product-usage read, or a fresh funding signal, straight in, so every email opens on a real reason instead of a guessed one.
Connect Clay or an enrichment tool so the first line names the exact role, the tech in use, or the hire, with no manual LinkedIn digging per prospect.
Drop the finished touches into your sequencer or HubSpot with the day 0 / 4 / 9 spacing already set, so the draft becomes a live cadence in one step.
One skill is the on-ramp.
A single skill does one job. Chained into a playbook, or run as a full build, it becomes a system. Here is where this one plugs in.