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…
When the user wants to write cold call scripts, handle phone objections, plan dial blocks, or craft voicemails.
$ npx skills add TheCraigHewitt/skills --skill cold-call -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install TheCraigHewitt/skills cold-call --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "cold-call" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/cold-call into .claude/skills/cold-call/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cold-call", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/TheCraigHewitt/skills/tree/main/sales/cold-callType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add TheCraigHewitt/skills --skill cold-call -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install TheCraigHewitt/skills cold-call --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/sales/cold-call .agents/skills/cold-call && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cold-call" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/cold-call into .agents/skills/cold-call/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cold-call", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add TheCraigHewitt/skills --skill cold-call -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install TheCraigHewitt/skills cold-call --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/sales/cold-call .cursor/skills/cold-call && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cold-call" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/cold-call into .cursor/skills/cold-call/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cold-call", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/TheCraigHewitt/skills.git --path sales/cold-call--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add TheCraigHewitt/skills --skill cold-call -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install TheCraigHewitt/skills cold-call --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/sales/cold-call .gemini/skills/cold-call && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cold-call" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/cold-call into .gemini/skills/cold-call/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cold-call", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install TheCraigHewitt/skills cold-callInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add TheCraigHewitt/skills --skill cold-call -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/sales/cold-call .github/skills/cold-call && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cold-call" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/cold-call into .github/skills/cold-call/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cold-call", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add TheCraigHewitt/skills --skill cold-call -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install TheCraigHewitt/skills cold-call --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/sales/cold-call .opencode/skills/cold-call && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cold-call" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/cold-call into .opencode/skills/cold-call/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cold-call", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
cold-callWhen 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. 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.
5 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit fdbf39b. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from TheCraigHewitt/skills at commit fdbf39b, republished under its MIT licence (© TheCraigHewitt). 2,340 words, ~5,033 tokens.
.claude/skills/cold-call/SKILL.md (or your agent's skills folder).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.
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:
Know your numbers. If you don't measure it, you can't improve it.
| Metric | Benchmark | What It Means |
|---|---|---|
| Dials per hour | 12-18 (with research), 25-35 (blitz) | Under 12 = too much time between calls |
| Connect rate | 15-25% of dials | Under 10% = bad data or wrong call windows |
| Conversation rate | 40-60% of connects | Under 40% = opener needs work |
| Meeting rate | 3-5% of connects | Under 2% = pitch or qualifying problem |
| Show rate | 70-85% of meetings booked | Under 60% = confirmation process is broken |
| Voicemail callback rate | 1-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%+.
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.
| Persona | Best Windows | Why |
|---|---|---|
| C-suite (CEO, CRO, CFO) | 7:30-8:30am, 5:00-6:30pm | Before their calendar fills up, or after their team leaves |
| VP / Director | 8:00-9:30am, 4:00-5:30pm | Before morning meetings, during late-day catch-up |
| Manager / IC | 10:00-11:30am, 2:00-4:00pm | After 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.
You have about 8 seconds before they decide to stay or hang up. Choose your opener based on context.
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."
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.
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.
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.
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.
Gatekeepers aren't obstacles — they're people doing their job. Treat them with respect and you'll get through more often.
"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.
"Hi, I'm trying to reach {{prospect_name}} regarding
{{relevant topic}}. Can you point me in the right direction?"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."Under 30 seconds. One idea. One CTA. That's it.
"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}}.""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."The reflexive "not interested" is not a real objection. It's a defense mechanism. Don't argue. Don't fold. Acknowledge and redirect.
"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.""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}}?""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.
"No problem. When's a better time — later today or tomorrow
morning?"Always offer two specific times. "Call me back sometime" means never.
"Your info is on {{source — LinkedIn, website, database}}.
I know cold calls aren't fun — I'll be quick. {{pivot to
reason for calling}}.""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?""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.
When they say "you should talk to [someone else]" — this is an opportunity, not a deflection. Handle it wrong and you lose both contacts.
"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.
"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.
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."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:
Don't interrogate. Weave questions into conversation. If two answers confirm fit, book 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.
"It sounds like this is worth exploring. I've got Tuesday at
2pm or Thursday at 10am — which works better for you?""No commitment — just 15 minutes to see if there's a fit.
If not, I'll tell you and we'll part friends. Fair?"They actually called you back. This is a different game — you're no longer interrupting, you're responding. Shift your mindset.
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.
"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.
This happens on 20-30% of dials. Don't waste it.
"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.
"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.
Scripts matter less than how you deliver them. Key principles:
Cold calling works best in focused blocks. Don't sprinkle 5 calls between emails.
| Time | Activity |
|---|---|
| 8:00-8:30 | List prep, research, CRM review |
| 8:30-10:00 | Call block 1 (C-suite targets, East Coast) |
| 10:00-10:30 | Email follow-ups, voicemail-email pairs |
| 10:30-12:00 | Call block 2 (Directors/Managers, Central) |
| 12:00-1:00 | Lunch |
| 1:00-1:30 | CRM notes, pipeline review, callbacks |
| 1:30-3:00 | Call block 3 (West Coast, callbacks, re-dials) |
| 3:00-3:30 | Admin — CRM cleanup, next-day list prep |
| 3:30-5:00 | LinkedIn outreach, research for tomorrow |
Every call gets logged. No exceptions. If it's not in the CRM, it didn't happen.
Use consistent dispositions so your data is clean and reportable:
| Disposition | Definition | Next Action |
|---|---|---|
| Connected - Meeting Booked | Spoke to prospect, meeting scheduled | Send confirmation email + calendar invite |
| Connected - Callback Scheduled | Spoke to prospect, agreed to specific callback | Set task for callback date/time |
| Connected - Not Interested | Spoke to prospect, clear rejection | Note reason, revisit in 90 days |
| Connected - Nurture | Spoke to prospect, timing not right | Add to nurture sequence, set re-engage date |
| Connected - Referred | Spoke to prospect, referred to another contact | Create new contact, note referral source |
| Voicemail | Left a voicemail | Pair with email, schedule next attempt |
| No Answer - No VM | No answer, no voicemail left | Schedule next attempt |
| Gatekeeper - Blocked | Reached gatekeeper, didn't get through | Try different time, note gatekeeper name |
| Gatekeeper - Info Gathered | Reached gatekeeper, got useful intel | Update contact record, adjust approach |
| Wrong Number | Number is incorrect | Update record, research correct number |
| Left Company | Prospect no longer at this company | Research new contact + prospect's new company |
| Bad Data | Number disconnected or invalid | Remove from active list, flag data source |
Every Friday, spend 30 minutes reviewing your pipeline:
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.
© TheCraigHewitt, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in sales/cold-call of TheCraigHewitt/skills.
Open the folder on GitHubat commit fdbf39b
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cold Call this skillTheCraigHewitt/skills | 159 | — | ~5k | Automated safety check: Pass | MIT | |
| Account Researchexplorium-ai/gtm-skills | 185 | — | ~2.8k | Automated safety check: Pass | MIT | |
| Champion Move Outreachgooseworks-ai/goose-skills | 1.2k | 1 repos | ~6.6k | Automated safety check: Pass | MIT | |
| Deal Playbookjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.2k | Automated safety check: Notes | MIT | |
| Cold Outbound Optimizerericosiu/ai-marketing-skills | 3.6k | 1 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Prospectingcoreyhaines31/marketingskills | 54k | — | ~5k | Automated safety check: Pass | MIT |
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…
gooseworks-ai/goose-skills
End-to-end champion/buyer/user job change signal composite. An agent skill from gooseworks-ai/goose-skills.
jeremylongshore/tons-of-skills-marketplace
Write sales playbooks — outbound sequences, discovery call guides, objection handling scripts, and demo frameworks.
ericosiu/ai-marketing-skills
Design, analyze, and optimize cold outbound email campaigns for Instantly.
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.
romangojiberryAI/gojiberryai-sales-os
A complete outbound sales department in one skill. An agent skill from romangojiberryAI/gojiberryai-sales-os.
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.
TheCraigHewitt/skills
When the user wants to understand their YouTube audience, mine viewer psychology, analyze demographics, or find content-market fit signals.
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.
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.
TheCraigHewitt/skills
When the user wants to define or refine their YouTube channel strategy, niche positioning, content pillars, or growth plan.
TheCraigHewitt/skills
When the user wants to plan YouTube collaborations, write outreach to other creators, design cross-promotion strategies, or pitch guest appearances.
Categories
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.
Cold Call fits situations like: wants to write cold call scripts; handle phone objections; plan dial blocks; craft voicemails.
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.
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.
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.
SKILL.md names no scripts, command-line tools or credentials: Cold Call is instructions for the agent only.
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.
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.
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.
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.
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.
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.