Turn a cold dial into a conversation.
A permission-based opener plus ready turns for the four objections you actually hit on the phone.
Inside: The opener, the pattern interrupt, and agree-then-redirect objection turns.
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 and any prior touches so the opener references a real reason to call.
pulls the role and current stack so the "we already use X" turn names the right incumbent.
lets you save the openers and turns as snippets for the persona you dial most.
This was built for B2B phone outbound into a named persona. Set these to your motion:
Dial any persona you like. The skill builds the turns around your offer and the objection you actually lose on, not a generic gauntlet.
| Set this | What it is | Default / Example |
|---|---|---|
| PERSONA | who picks up | AERevOps leadSupport manager |
| OFFER | the one problem you solve | stated in the prospect's words |
| PERMISSION_LINE | how you ask for 30 seconds | "did I catch you at an okay time?" |
| INCUMBENT | the tool they likely already use | a category toolnamed if known |
| TONE | how direct you run | plain and calmnever pushy |
| CRM | your CRM connector | a CRM you already run |
| DIALER | where you save snippets | a dialer or call tool you run |
Everything the skill does, in full.
Writes a short, permission-based opener that respects the fact you interrupted someone, plus the four turns you actually hit on the phone: the reflex brush-off, the no-time push, the "send me something," and the incumbent wall. Each turn keeps the call alive without fighting the prospect.
- 1Permission-based opener
Open by naming that you are a cold call, then ask for a small, honest slice of time. "I know I am interrupting, can I take 30 seconds and you tell me if it is worth more?" Candor lowers the reflex to hang up. No fake familiarity, no "how are you today."
- 2The pattern-interrupt, not the pitch
The opener earns the next 30 seconds by being specific and short, not by pitching. One reason you called this person, in one sentence, ending in a question that hands them control.
- 3Objection turns (the four you actually hit)
- Not interested: agree first, then ask one honest question. "Totally fair, most people say that before they have a reason to care. Can I give you the one reason I called and you decide?"
- No time: shrink the ask, offer the exit. "I believe you. Ten seconds now, or a better time to call back?"
- Just send me info: trade the send for one question, so the info is relevant. "Happy to. So I do not spam you, what is the one thing worth me including?"
- We already use X: validate the incumbent, find the gap. "Most people I call do. I am not calling to rip it out. Usually the gap is [angle], is that true for you too?"
- 4The graceful exit
Every turn has a version that ends the call cleanly if the answer is a real no. A fast, respectful exit protects the number and your reputation. No badgering.
- The opener asks permission and admits it is a cold call. No fake rapport.
- Every objection turn agrees before it redirects. Never argue the prospect down.
- The "we already use X" turn names a gap, not a knock on the incumbent.
- Every turn has a clean exit. No third attempt after a real no.
COLD CALL · RevOps lead · offer: cut manual pipeline hygiene Opener: "Hi [name], you don't know me, this is a cold call. Can I take 30 seconds to tell you why I called, then you tell me if it is worth more? ... I called because RevOps teams your size usually lose a day a week to manual CRM cleanup before forecast. Is that a real thing for you, or have you solved it?" Objection turns: - Not interested -> "Fair. Most people say that first. One reason I called, then you decide?" - No time -> "Believe you. Ten seconds now, or better to call back Thursday?" - Send me info -> "Happy to. What is the one thing worth including so it is not noise?" - Already use X -> "Most people do. Not calling to replace it. The gap is usually [angle]. True for you?"
Where an operator takes this next.
The read is step one. Here's where an operator takes it once the manual version proves out.
You built the read once; now it runs itself.
Save the opener and the four objection turns as snippets in your dialer so reps pull them mid-call instead of paging through a doc.
Connect an enrichment tool so the "already use X" turn names the real tool on record for that account, not a guess.
Feed Gong call recordings back through weekly so the objection turns update based on what's actually landing, not what sounded good on paper.
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.