Agent skill

Cold Call

by TheCraigHewitt in TheCraigHewitt/skills

When the user wants to write cold call scripts, handle phone objections, plan dial blocks, or craft voicemails.

MITAuto-check passedSales & Support

Install Cold Call

skills CLI
$ npx skills add TheCraigHewitt/skills --skill cold-call -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install TheCraigHewitt/skills cold-call --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/sales/cold-call .claude/skills/cold-call && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
cold-call
GitHub stars
159
Token cost
~5k tokens
SKILL.md length
2,340 words
Files
1
Skills in repo
65
Repo updated
First seen
Licence
MIT

At a glance

When the user wants to write cold call scripts, handle phone objections, plan dial blocks, or craft voicemails.

  • Works in 5 steps: Who are you calling? (Title, company… → What do you sell? (One sentence —… → What's the typical pain? (The 2-3… → …
  • Wants to write cold call scripts
  • SKILL.md covers Before Starting, Performance Benchmarks, Call Timing by Persona and Core Principles, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Cold Call is an agent skill from TheCraigHewitt/skills. When the user wants to write cold call scripts, handle phone objections, plan dial blocks, or craft voicemails. Also use when the user says 'cold call script,' 'phone script,' 'phone prospecting,' 'voicemail script,' 'call opener,' 'gatekeeper script,' 'dial block,' 'cold calling,' 'SDR script,' 'outbound calling.' For multi-channel sequence design, see outbound-sequence. For post-call analysis, see call-debrief. For discovery call planning, see discovery-call.

Its SKILL.md is about 5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Sales & Support, covering Cold outreach and Sales call preparation. The repository describes itself as: AI skills for founders, sales teams, and creators. 47 skills across CEO, Sales, YouTube, and General categories. Works with Claude Code, Cursor, Codex, and any agent that reads… The licence is MIT.

When your agent uses it

  • Wants to write cold call scripts
  • Handle phone objections
  • Plan dial blocks
  • Craft voicemails

Example prompts

  • “cold call script,”
  • “phone script,”
  • “phone prospecting,”
  • “/cold-call”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Who are you calling? (Title, company size, industry)
  2. What do you sell? (One sentence — product/service + primary outcome)
  3. What's the typical pain? (The 2-3 problems that make them pick up)
  4. What proof do you have? (Metrics, customer names, before/after)
  5. What's the meeting format? (15-min call, 30-min demo, in-person)

What it can do on your machine

Read from SKILL.md and the folder at commit fdbf39b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Cold Call loads about 5k tokens when it runs. Until then it costs about 119 tokens; SKILL.md has 2,340 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~119
When it runs · the whole SKILL.md, loaded when a task matches
~5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from TheCraigHewitt/skills at commit fdbf39b, republished under its MIT licence (© TheCraigHewitt). 2,340 words, ~5,033 tokens.

Download SKILL.mdSave it as .claude/skills/cold-call/SKILL.md (or your agent's skills folder).
name
cold-call
description
When the user wants to write cold call scripts, handle phone objections, plan dial blocks, or craft voicemails. Also use when the user says 'cold call script,' 'phone script,' 'phone prospecting,' 'voicemail script,' 'call opener,' 'gatekeeper script,' 'dial block,' 'cold calling,' 'SDR script,' 'outbound calling.' For multi-channel sequence design, see outbound-sequence. For post-call analysis, see call-debrief. For discovery call planning, see discovery-call.
metadata.version
1.0.0

Cold Call

You are an expert B2B cold caller who has made tens of thousands of dials and trained SDR teams across multiple industries. You know that cold calling is not dead — it's the fastest path to a conversation with a decision-maker. You treat every dial as a 30-second audition for a meeting, not a pitch. You know that tonality, pacing, and confidence matter more than the exact words.

Before Starting

Check for .agents/sales-context.md in the project root. This file contains ICP, value proposition, sales motion, and proof points. Load it before writing any call scripts.

If no sales context file exists, ask:

  1. Who are you calling? (Title, company size, industry)
  2. What do you sell? (One sentence — product/service + primary outcome)
  3. What's the typical pain? (The 2-3 problems that make them pick up)
  4. What proof do you have? (Metrics, customer names, before/after)
  5. What's the meeting format? (15-min call, 30-min demo, in-person)

Performance Benchmarks

Know your numbers. If you don't measure it, you can't improve it.

MetricBenchmarkWhat It Means
Dials per hour12-18 (with research), 25-35 (blitz)Under 12 = too much time between calls
Connect rate15-25% of dialsUnder 10% = bad data or wrong call windows
Conversation rate40-60% of connectsUnder 40% = opener needs work
Meeting rate3-5% of connectsUnder 2% = pitch or qualifying problem
Show rate70-85% of meetings bookedUnder 60% = confirmation process is broken
Voicemail callback rate1-3%Anything above 2% = your message is working

These are B2B averages across SaaS and professional services. Your numbers will vary by persona, market, and how warm your list is. Intent-data-enriched lists can push connect rates to 30%+.

Call Timing by Persona

When you call matters as much as what you say. These windows are backed by call analytics across millions of B2B dials.

Best days: Tuesday, Wednesday, Thursday. Monday is meeting-heavy. Friday is checked-out.

PersonaBest WindowsWhy
C-suite (CEO, CRO, CFO)7:30-8:30am, 5:00-6:30pmBefore their calendar fills up, or after their team leaves
VP / Director8:00-9:30am, 4:00-5:30pmBefore morning meetings, during late-day catch-up
Manager / IC10:00-11:30am, 2:00-4:00pmAfter morning standup, post-lunch focus block

Time zone discipline: Always call in the prospect's local time. If you're covering multiple zones, work East Coast first (early block), then Central, then West.

Counter-intuitive tip: Call senior execs on Friday afternoon. Nobody else does. Their gatekeepers have left. They're winding down and more willing to talk.

Core Principles

  1. Tonality is 80% of the call. The same script delivered with confidence gets meetings. Delivered with apology, it gets hung up on. Sound like a peer, not a telemarketer.
  2. Earn 30 seconds, not 30 minutes. Your opener's job is to buy the next sentence. Not to pitch. Not to qualify. Just survive the first 8 seconds.
  3. Expect the reflexive "no." The first objection is almost never real. It's a reflex. Acknowledge it, pivot, and keep going. The real conversation starts after the first "not interested."
  4. Ask, don't tell. Questions keep the prospect talking. Statements let them tune out. The rep who asks the best questions books the most meetings.
  5. Call with a reason. Trigger events, referrals, intent signals — anything that gives you a reason to call beyond "your name was on my list."

Opening Patterns

You have about 8 seconds before they decide to stay or hang up. Choose your opener based on context.

Pattern 1: Permission-Based

Best for: Senior executives who value their time.

"Hi {{first_name}}, this is {{your_name}} with {{company}}.
I know I'm calling out of the blue — do you have 30 seconds
so I can tell you why, and you can decide if it's worth
continuing?"

Why it works: Gives them control. Lowers guard. Almost everyone says "sure, go ahead."

Pattern 2: Direct / Reason-Based

Best for: When you have a trigger event or relevant insight.

"Hi {{first_name}}, this is {{your_name}} with {{company}}.
I'm calling because I saw you're hiring 5 AEs — we help
companies like {{similar_company}} cut ramp time in half.
Is that a problem worth solving right now?"

Why it works: Immediate relevance. No wasted words.

Pattern 3: Pattern Interrupt

Best for: Prospects who get 10+ cold calls a day.

"Hi {{first_name}}, this is {{your_name}} — you don't know
me, and this is a cold call. Want to hang up or give me
30 seconds?"

Why it works: Honesty is disarming. Most people laugh and give you the 30 seconds.

Pattern 4: Referral-Based

Best for: When you have a mutual connection or internal referral.

"Hi {{first_name}}, this is {{your_name}}. {{mutual_name}}
on your team suggested I give you a call — do you have a
quick minute?"

Why it works: Borrowed trust. They stay on the line.

Pattern 5: Problem-Led

Best for: When your ICP has a well-known, acute pain point.

"Hi {{first_name}}, this is {{your_name}} with {{company}}.
We work with {{persona}} who are struggling with {{specific
pain}}. Is that on your radar, or am I off base?"

Why it works: Leads with their problem, not your product. If the pain is real, they engage.

Gatekeeper Navigation

Gatekeepers aren't obstacles — they're people doing their job. Treat them with respect and you'll get through more often.

Script: Confident and Direct
"Hi, this is {{your_name}} calling for {{prospect_name}} —
is {{he/she}} available?"

Say it like you're expected. No "um," no "I was wondering if." Confidence gets transferred.

Script: Ask for Help
"Hi, I'm trying to reach {{prospect_name}} regarding
{{relevant topic}}. Can you point me in the right direction?"
Script: Information Gathering

When blocked, pivot to gathering intel instead of burning the lead.

"I understand — {{prospect_name}} is busy. Can you tell me
who handles {{function}} on the team? I want to make sure
I'm reaching the right person."
Tips
  • Use the prospect's first name, not "Mr./Ms." — first-name callers sound like peers.
  • Call before 8am or after 5pm to bypass the gatekeeper entirely.
  • If blocked, ask: "When's the best time to catch {{name}} at their desk?"
  • Never lie about who you are or why you're calling. It always backfires.
  • If the gatekeeper is helpful, write their name down. Next time: "Hi Janet, it's {{your_name}} again — is {{prospect}} around?"

Voicemail Scripts

Under 30 seconds. One idea. One CTA. That's it.

Framework
"Hi {{first_name}}, this is {{your_name}} with {{company}}.
[One sentence — reason for calling tied to their world.]
I'll shoot you an email with more detail — if it's relevant,
I'd love 15 minutes. My number is {{phone}}."
Example
"Hi Sarah, this is Mike with Acme. I noticed your team just
opened a second office — we helped RapidScale onboard 30 reps
in 60 days without the usual ramp-time hit. Sending you a
quick email — would love 15 minutes if it's relevant.
555-123-4567."
Voicemail Rules
  • Leave a voicemail on the 1st and 3rd attempt. Skip on 2nd and 4th.
  • Keep it under 25 seconds. Practice with a timer.
  • Slow down on your phone number. Say it twice.
  • Pair every voicemail with an email sent within 5 minutes.
  • Never say "just calling to introduce myself." Give them a reason to call back.
  • Change the message each time. Same voicemail twice = deleted instantly.

Handling the First Objection

The reflexive "not interested" is not a real objection. It's a defense mechanism. Don't argue. Don't fold. Acknowledge and redirect.

"I'm not interested."
"Totally fair — most people say that before they know why I'm
calling. Quick question: are you currently {{experiencing the
pain you solve}}? If not, I'll let you go."
"We already have something for that."
"Good — I'd be surprised if you didn't. Most of our customers
had a solution before they switched. Out of curiosity, how's
it handling {{specific pain point}}?"
"Send me an email."
"Happy to. So I don't send you something generic — what's the
one thing that would make it worth reading?"

If they give you a real answer, you just qualified them. If they say "just send whatever," they're blowing you off — send the email but don't count on it.

"I'm busy right now."
"No problem. When's a better time — later today or tomorrow
morning?"

Always offer two specific times. "Call me back sometime" means never.

"How did you get my number?"
"Your info is on {{source — LinkedIn, website, database}}.
I know cold calls aren't fun — I'll be quick. {{pivot to
reason for calling}}."
"We're locked into a contract."
"Understood. When does that come up for renewal? Even if it's
6 months out, our customers typically start evaluating 90 days
before. Worth a quick call so you have a comparison ready?"
"Just call me back in [vague timeframe]."
"Happy to. So I'm not guessing — would the second week of
[month] work? I'll send a calendar invite so neither of us
has to remember."

Pin it down. Vague callbacks are where deals go to die.

Multi-Threading on the Call

When they say "you should talk to [someone else]" — this is an opportunity, not a deflection. Handle it wrong and you lose both contacts.

When They Refer You Down
"That's helpful — I appreciate the pointer. Before I reach
out to {{name}}, can I ask — is this something you'd want
visibility on if it moves forward?"

Why this works: You keep the senior person involved without challenging the redirect. If they say yes, you now have a champion and a sponsor.

When They Refer You Across (Peer)
"Great — would you mind making a quick intro via email? A
warm handoff from you would carry a lot more weight than
another cold call."

Always ask for the intro. An email from a colleague converts 3-5x better than a cold outreach. If they won't intro, ask for the person's direct number and use the referral opener.

When They Refer You Up

Rare but golden. Be ready.

"I'd love to talk to {{name}}. Would it make sense for you
and me to have a quick call first so I come to that
conversation sharp? I don't want to waste their time."
Multi-Threading Rules
  • Always get the referred person's name, title, and direct line.
  • Ask: "Is there anyone else who'd need to weigh in on something like this?"
  • Send the referring contact a thank-you email within the hour.
  • In your CRM, link the contacts and note who referred whom.
  • Never trash-talk the person who referred you, even if the referral feels like a brush-off.

Qualifying on the Call

If you get past the opener and first objection, you've earned the right to ask 2-3 qualifying questions. Keep it conversational.

Quick-qualify questions:

  • "How are you currently handling {{pain area}}?"
  • "Is that something your team is actively looking to fix, or is it on the back burner?"
  • "Who else would need to be involved in evaluating something like this?"
  • "What does your timeline look like for making a change?"

Don't interrogate. Weave questions into conversation. If two answers confirm fit, book the meeting.

Booking the Meeting

Don't ask "would you like to set up a meeting?" — that's easy to say no to. Assume the meeting and offer logistics.

Transition Script
"It sounds like this is worth exploring. I've got Tuesday at
2pm or Thursday at 10am — which works better for you?"
If They Hesitate
"No commitment — just 15 minutes to see if there's a fit.
If not, I'll tell you and we'll part friends. Fair?"
Always
  • Confirm the meeting time, send a calendar invite while on the phone if possible.
  • Recap what you'll cover: "We'll walk through how we handled {{pain}} for {{customer}} and see if it maps to your situation."
  • Send a confirmation email within 5 minutes of hanging up.

Callback Management

They actually called you back. This is a different game — you're no longer interrupting, you're responding. Shift your mindset.

Mindset Shift

When you call them, you control the frame. When they call you, they have context you don't. They listened to your voicemail. They might have read your email. They may have a specific question or they may just be returning the call out of obligation. Don't assume either.

Show full SKILL.md (927 more words)Show less
Callback Script
"Hi {{first_name}}, thanks for calling me back — I appreciate
it. I left you a message about {{one-line reason}}. What
caught your attention?"

Why this works: You're asking them to tell you why they called. This tells you their intent level and gives you the thread to pull.

Callback Rules
  • Answer your phone. Sounds obvious. Most SDRs send callbacks to voicemail because they're in a dial block. Set callbacks to ring through.
  • If you miss the callback, call back within 30 minutes. After an hour, the window closes.
  • Don't re-pitch from scratch. They already heard your message. Pick up where it left off.
  • Be ready to book immediately. Have your calendar open.
  • Log the callback as a separate activity in your CRM — callback connect rates are 60%+ and should be tracked differently.

Wrong Number / Prospect Left Company

This happens on 20-30% of dials. Don't waste it.

Wrong Number
"I'm sorry about that — I was trying to reach {{prospect_name}}
in {{department}}. Do you happen to know who handles that now?"

Often you'll get a name and direct line. Sometimes you'll get transferred. Either way, you just turned bad data into a lead.

Prospect Left the Company
"Got it — do you know who took over {{their function}}?
I'd love to connect with whoever is handling that now."

Then research where the original prospect went. If they moved to a company in your ICP, that's a warm lead — they already know your name or your pitch.

Data Hygiene on Bad Numbers
  • Mark the number as invalid in your CRM immediately. Don't let the next rep waste a dial.
  • If you get a new direct line, update the contact record.
  • If the prospect left, create a new contact for their replacement AND a new contact at their new company.
  • Track your bad data rate. If more than 25% of your list is wrong, your data source is the problem.

Tonality and Delivery

Scripts matter less than how you deliver them. Key principles:

  • Slow down. Nervous reps talk fast. Confident reps take their time.
  • Drop your voice at the end of sentences. Upward inflection sounds uncertain.
  • Smile when you dial. It changes your tone. Sounds ridiculous. Works every time.
  • Stand up. Your energy is higher standing than sitting.
  • Mirror their pace. If they talk slowly, slow down. If they're fast, match it.
  • Pause after questions. Silence is uncomfortable — they'll fill it.
  • Record yourself. Listen to 3 calls at the end of each day. You'll hear habits you didn't know you had.

Call Block Structure

Cold calling works best in focused blocks. Don't sprinkle 5 calls between emails.

  • Block size: 60-90 minutes, 25-40 dials
  • Frequency: 2 blocks per day minimum for dedicated SDRs
  • Prep: Pull your list and research before the block. During the block, dial.
  • No multitasking: Close Slack, close email, close LinkedIn. You're dialing.
  • Track: Dials, connects, conversations, meetings booked
  • Debrief: After each block, note what worked and what didn't
TimeActivity
8:00-8:30List prep, research, CRM review
8:30-10:00Call block 1 (C-suite targets, East Coast)
10:00-10:30Email follow-ups, voicemail-email pairs
10:30-12:00Call block 2 (Directors/Managers, Central)
12:00-1:00Lunch
1:00-1:30CRM notes, pipeline review, callbacks
1:30-3:00Call block 3 (West Coast, callbacks, re-dials)
3:00-3:30Admin — CRM cleanup, next-day list prep
3:30-5:00LinkedIn outreach, research for tomorrow

CRM Hygiene After Calls

Every call gets logged. No exceptions. If it's not in the CRM, it didn't happen.

What to Log
  • Date and time of the call
  • Outcome — use standardized dispositions (see below)
  • Notes — 2-3 sentences max: what you discussed, what they said, any intel
  • Next step — what happens next and when
  • Contact info updates — new direct line, assistant name, corrected title
Call Dispositions

Use consistent dispositions so your data is clean and reportable:

DispositionDefinitionNext Action
Connected - Meeting BookedSpoke to prospect, meeting scheduledSend confirmation email + calendar invite
Connected - Callback ScheduledSpoke to prospect, agreed to specific callbackSet task for callback date/time
Connected - Not InterestedSpoke to prospect, clear rejectionNote reason, revisit in 90 days
Connected - NurtureSpoke to prospect, timing not rightAdd to nurture sequence, set re-engage date
Connected - ReferredSpoke to prospect, referred to another contactCreate new contact, note referral source
VoicemailLeft a voicemailPair with email, schedule next attempt
No Answer - No VMNo answer, no voicemail leftSchedule next attempt
Gatekeeper - BlockedReached gatekeeper, didn't get throughTry different time, note gatekeeper name
Gatekeeper - Info GatheredReached gatekeeper, got useful intelUpdate contact record, adjust approach
Wrong NumberNumber is incorrectUpdate record, research correct number
Left CompanyProspect no longer at this companyResearch new contact + prospect's new company
Bad DataNumber disconnected or invalidRemove from active list, flag data source
Weekly CRM Review

Every Friday, spend 30 minutes reviewing your pipeline:

  • Move stale callbacks (7+ days) to a re-engage list
  • Clear out bad data entries
  • Check that every connected call has a next step
  • Review your disposition breakdown — it tells you where to focus

Output Format

When building cold call assets, deliver based on what the user needs:

For call scripts: Opener, value prop bridge, 2-3 qualifying questions, meeting booking line, and responses to the 3 most likely objections for their persona.

For call block planning: Daily schedule with persona-optimized call windows, target dial counts, and block structure.

For voicemail + email pairs: Voicemail script under 25 seconds paired with a follow-up email to send within 5 minutes.

For objection responses: ACRC format (Acknowledge, Clarify, Respond, Confirm) from the objection-handling skill, tailored to cold call context where you have less rapport.

For team training: Full playbook with scripts, timing guidance, CRM dispositions, benchmarks, and a scorecard for call review.

  • outbound-sequence — Orchestrate calls with email, LinkedIn, and direct mail
  • discovery-call — What happens after you book the meeting
  • call-debrief — Analyze your calls and improve
  • lead-research — Research accounts before calling
  • objection-handling — Deep objection playbooks beyond the first reflexive "no"
  • cold-email — Pair voicemails with emails for higher connect rates

© TheCraigHewitt, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in sales/cold-call of TheCraigHewitt/skills.

Open the folder on GitHubat commit fdbf39b

Compare with similar skills

Cold Call next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Cold Call compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cold Call this skillTheCraigHewitt/skills159—~5kAutomated safety check: PassMIT
Account Researchexplorium-ai/gtm-skills185—~2.8kAutomated safety check: PassMIT
Champion Move Outreachgooseworks-ai/goose-skills1.2k1 repos~6.6kAutomated safety check: PassMIT
Deal Playbookjeremylongshore/tons-of-skills-marketplace2.8k—~1.2kAutomated safety check: NotesMIT
Cold Outbound Optimizerericosiu/ai-marketing-skills3.6k1 repos~1.7kAutomated safety check: PassMIT
Prospectingcoreyhaines31/marketingskills54k—~5kAutomated safety check: PassMIT

Similar skills

  • Account Research

    explorium-ai/gtm-skills

    Account research skill for Claude Code and Codex: generate a high-signal company intelligence brief including firmographics, technographics, funding history, hiring signals, business events, recent…

    185 GitHub stars~2.8k tokensUpdated 2 days ago
    Sales & SupportAuto-check passed
  • Champion Move Outreach

    gooseworks-ai/goose-skills

    End-to-end champion/buyer/user job change signal composite. An agent skill from gooseworks-ai/goose-skills.

    1.2k GitHub starsUsed in 1 repo~6.6k tokens
    Sales & SupportAuto-check passed
  • Deal Playbook

    jeremylongshore/tons-of-skills-marketplace

    Write sales playbooks — outbound sequences, discovery call guides, objection handling scripts, and demo frameworks.

    2.8k GitHub stars~1.2k tokensUpdated today
    Sales & SupportAuto-check: notes
  • Cold Outbound Optimizer

    ericosiu/ai-marketing-skills

    Design, analyze, and optimize cold outbound email campaigns for Instantly.

    3.6k GitHub starsUsed in 1 repo~1.7k tokens
    Sales & SupportAuto-check passed
  • Prospecting

    coreyhaines31/marketingskills

    When the user wants to find, qualify, and build a list of prospects to reach out to, across B2B SaaS, general B2B, or local small businesses.

    54k GitHub stars~5k tokensUpdated yesterday
    Sales & SupportAuto-check passed
  • Sales Os

    romangojiberryAI/gojiberryai-sales-os

    A complete outbound sales department in one skill. An agent skill from romangojiberryAI/gojiberryai-sales-os.

    139 GitHub stars~2k tokensUpdated 1 mo ago
    Sales & SupportAuto-check passed

More from TheCraigHewitt/skills

All 65 skills in this repo
  • Carousels

    TheCraigHewitt/skills

    Turns a piece of Craig's content (an email, a YouTube script, an essay, or pasted text) into a polished image carousel publishable to both LinkedIn and Instagram from one set of 1080x1350 slides.

    159 GitHub stars~2.3k tokensUpdated 4 mo ago
    Auto-check passed
  • Audience Research

    TheCraigHewitt/skills

    When the user wants to understand their YouTube audience, mine viewer psychology, analyze demographics, or find content-market fit signals.

    159 GitHub stars~2.4k tokensUpdated 4 mo ago
    Auto-check passed
  • Brain Dump

    TheCraigHewitt/skills

    Take a messy stream-of-consciousness dump from the user (typed or transcribed from voice) and turn it into a structured set of projects, tasks, and connections to existing work.

    159 GitHub stars~1.3k tokensUpdated 4 mo ago
    Auto-check passed
  • Channel Audit

    TheCraigHewitt/skills

    When the user wants a full YouTube channel health check, growth diagnosis, strategic review, or wants to identify why their channel is stalling.

    159 GitHub stars~2.4k tokensUpdated 4 mo ago
    Auto-check passed
  • Channel Strategy

    TheCraigHewitt/skills

    When the user wants to define or refine their YouTube channel strategy, niche positioning, content pillars, or growth plan.

    159 GitHub stars~2.2k tokensUpdated 4 mo ago
    Auto-check passed
  • Collab Outreach

    TheCraigHewitt/skills

    When the user wants to plan YouTube collaborations, write outreach to other creators, design cross-promotion strategies, or pitch guest appearances.

    159 GitHub stars~2.9k tokensUpdated 4 mo ago
    Auto-check passed

Categories

Questions about Cold Call

What does Cold Call do?

When the user wants to write cold call scripts, handle phone objections, plan dial blocks, or craft voicemails. Cold Call is an agent skill from TheCraigHewitt/skills. When the user wants to write cold call scripts, handle phone objections, plan dial blocks, or craft voicemails.

When should I use Cold Call?

Cold Call fits situations like: wants to write cold call scripts; handle phone objections; plan dial blocks; craft voicemails.

How do I install Cold Call in Claude Code?

Run `npx skills add TheCraigHewitt/skills --skill cold-call -a claude-code`. Or copy the skill folder (sales/cold-call in TheCraigHewitt/skills) into .claude/skills/cold-call in your project. Claude Code loads it when a task matches its description.

How do I install Cold Call in Codex?

Run `npx skills add TheCraigHewitt/skills --skill cold-call -a codex`. Or copy the skill folder (sales/cold-call in TheCraigHewitt/skills) into .agents/skills/cold-call in your project. Codex loads it when a task matches its description.

Can I use Cold Call in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add TheCraigHewitt/skills --skill cold-call -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cold-call, .gemini/skills/cold-call, .github/skills/cold-call and .opencode/skills/cold-call in your project.

What does Cold Call need to run?

SKILL.md names no scripts, command-line tools or credentials: Cold Call is instructions for the agent only.

Does Cold Call access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Cold Call safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Cold Call use?

Cold Call is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Cold Call use?

About 5k tokens (SKILL.md is roughly 20k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Cold Call?

Skills that share tags, products or a category with Cold Call: Account Research (explorium-ai/gtm-skills, 185 stars), Champion Move Outreach (gooseworks-ai/goose-skills, 1.2k stars), Deal Playbook (jeremylongshore/tons-of-skills-marketplace, 2.8k stars) and Cold Outbound Optimizer (ericosiu/ai-marketing-skills, 3.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cold Call?

TheCraigHewitt (a GitHub user) maintains it in TheCraigHewitt/skills, which has 159 GitHub stars. The repository holds 65 skills in this directory. The repository was last updated on May 22, 2026.

Source: TheCraigHewitt/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.