From Claudient — SDR
- You are executing B2B outbound cold calls and need a structure that fits 60 seconds without triggering sales-call defensiveness. - You have a specific trigger or pain observation about a prospect (n
How this skill is triggered — by the user, by Claude, or both
Slash command
/claudient-sdr:cold-call-scriptThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- You are executing B2B outbound cold calls and need a structure that fits 60 seconds without triggering sales-call defensiveness.
Break the "sales call" script expectation with a genuine, low-pressure opener. Your goal is control rebalance — give them agency and reduce defensiveness.
Template:
Benchmark: If they say "yes, bad time," say: "Perfect — when's better this week?" and set a callback. No pushback. This builds credibility for step 5.
Declare your time boundary and make it easy for them to hang up. This paradoxically increases listen-through because they know the cost.
Template:
Benchmark: After this line, they are statistically more likely to engage than if you skip it. Never exceed 30 seconds on this permission frame.
Name their industry + their role + the specific problem you observe. Make it personal, observed, specific — not templated.
Template structure:
Concrete example:
Benchmark: Spend 10-12 seconds here; leave 3 seconds for them to process. Do not pitch a solution.
One sentence about a similar company result. No product name, no jargon, no percentages without context.
Template:
Concrete example:
Benchmark: 8-10 seconds. This is NOT a pitch — it's proof that the problem is solvable. No "I think you'd benefit from us."
Single, open-ended question about their situation. Stop talking. Let them own the next 25 seconds.
Template:
Concrete example:
Benchmark: This is the setup for a real conversation, not a close. Your job is to get them talking so you can identify if there is a real fit. The best calls end with them asking you a question back.
Leave a voicemail only if:
Template structure:
Concrete example: "Hi Sarah, this is Chris from [Company]. I'm calling because I noticed you just hired a new VP of Sales, and I've worked with three other [industry] teams through that transition. Quick question — when you're onboarding new sales leaders, is knowledge transfer a bottleneck? Feel free to text me back at [number] or just ignore this and I'll send you something via email. Talk soon."
Benchmark: 18-22 seconds total. No rambling. If they don't call back, your email has already landed and given them context for why you're reaching out.
If they miss a scheduled call, send within 5 minutes. Acknowledge + reset.
Template:
Concrete example: "Hi Sarah — I had us down for 2pm. Looks like we missed each other. How about Tuesday at 2pm or Wednesday at 10am instead? Either works."
Benchmark: 3 lines maximum. No re-pitch, no "wanted to touch base." They already know why you're meeting; they just forgot or had a conflict.
Your response: "Happy to — what would make you actually read it?"
Logic: They are not asking for a PDF. They are asking you to leave them alone. Force a real criterion.
Follow-up options (based on their answer):
Benchmark: 70% of "send me info" closes with a scheduled follow-up if you handle it this way.
Your response: "Fair — can I ask what you're currently using for [the specific problem I named]?"
Logic: They are not saying no to the outcome. They are saying no to talking to you. Get them talking about their current state.
Follow-up (after they answer):
Benchmark: 50% of "not interested" reopens if you stay curious about their current state instead of pitching.
Your response: "Totally understand. What would need to change for that to be a conversation?"
Logic: Budget objections are often timing objections. Understand the real constraint.
Follow-up (based on their answer):
Benchmark: 60% of "no budget" calls move to a follow-up conversation if you acknowledge the constraint and ask what would change it.
You are an SDR at a product team collaboration tool. Your list segment: mid-market tech companies (50–300 people) that just hired a VP of Engineering in the past 90 days. Your trigger: new VP engineering hire often means onboarding workflows are a pain point.
Dialer call connects.
Step 1 — Pattern Interrupt (5 sec): "Hey Marcus, did I catch you at a bad time?" (If yes → "Cool, when's better this week?" and hang up. Schedule callback. If no → continue.)
Step 2 — Earn Permission (5 sec): "Perfect. I'll take 30 seconds. If it's not relevant, you can hang up."
Step 3 — Establish Relevance (15 sec): "I work with tech teams, specifically VPs of Engineering, and I noticed you just got promoted into that role at [Company]. One thing we've seen across teams like yours is that the first 60 days of onboarding new engineers is almost always a knowledge-transfer bottleneck — a lot of your time goes to repeating context that's scattered across Slack, docs, and video walkthroughs."
Step 4 — Social Proof (10 sec): "We worked with a similar team at [past client], and they centralized all that onboarding context in one place. Reduced their new-engineer time-to-first-commit from 5 days to 2, which freed Marcus up to actually lead instead of be a walking wiki."
Step 5 — Open Question (25 sec): "How do you currently handle onboarding new engineers into your stack right now?" (Stop. Let them talk. They will either say "it's a mess" or "actually we have a system." Either way, they are now in conversation, not defense.)
You: "Happy to — what would make you actually read it?"
Them: "I'll review it this week."
You: "That usually doesn't happen with PDFs. How about this — I'll send you a 2-minute overview video instead, and we schedule 15 minutes next Tuesday to walk through it and see if it even makes sense for your team. Does 2pm or 4pm work?"
You: "Fair — can I ask what tool or process you're using right now for onboarding?"
Them: "We use Notion and a checklist."
You: "How's that working?"
Them: "It's okay, but we're always updating it and people miss steps."
You: "That's the exact friction we've fixed for other teams. Would a quick 20-minute call next week to show you how we'd solve that make sense?"
"Hi Marcus, this is [Your Name] from [Company]. I'm calling because you just took the VP of Engineering role at [Company], and I work with teams in that transition. One quick question — when you're onboarding new engineers, how much of your time goes to repeating context they could've found in docs? Feel free to text me back at [number], or I'll send you something over email and we can connect then. Talk soon."
"Hi Marcus — had us down for 2pm. Looks like we missed each other. How about Tuesday at 2pm or Wednesday at 10am instead? Either works."
Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
npx claudepluginhub claudient/claudient --plugin claudient-sdr