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 ask for a warm introduction, build a referral program, or systematize their referral channel.
$ npx skills add TheCraigHewitt/skills --skill referral-intro -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install TheCraigHewitt/skills referral-intro --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/referral-intro .claude/skills/referral-intro && 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 "referral-intro" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/referral-intro into .claude/skills/referral-intro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "referral-intro", 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/referral-introType 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 referral-intro -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install TheCraigHewitt/skills referral-intro --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/referral-intro .agents/skills/referral-intro && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "referral-intro" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/referral-intro into .agents/skills/referral-intro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "referral-intro", 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 referral-intro -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install TheCraigHewitt/skills referral-intro --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/referral-intro .cursor/skills/referral-intro && 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 "referral-intro" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/referral-intro into .cursor/skills/referral-intro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "referral-intro", 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/referral-intro--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 referral-intro -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install TheCraigHewitt/skills referral-intro --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/referral-intro .gemini/skills/referral-intro && 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 "referral-intro" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/referral-intro into .gemini/skills/referral-intro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "referral-intro", 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 referral-introInstalls 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 referral-intro -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/referral-intro .github/skills/referral-intro && 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 "referral-intro" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/referral-intro into .github/skills/referral-intro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "referral-intro", 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 referral-intro -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 referral-intro --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/referral-intro .opencode/skills/referral-intro && 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 "referral-intro" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/referral-intro into .opencode/skills/referral-intro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "referral-intro", 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.
referral-introWhen the user wants to ask for a warm introduction, build a referral program, or systematize their referral channel.
Referral Intro is an agent skill from TheCraigHewitt/skills. When the user wants to ask for a warm introduction, build a referral program, or systematize their referral channel. Also use when the user says 'get me an intro,' 'ask for a referral,' 'write a forwardable email,' 'warm introduction,' 'partner referral,' 'reference request,' 'intro email,' 'leverage my network,' 'referral program,' 'ask for an intro at dinner,' or 'track referrals in CRM.' For cold outreach without a warm path, see cold-email or linkedin-outreach. For sequencing referral asks into a cadence, see…
Its SKILL.md is about 6.7k 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, Referral and retention marketing and Sales call preparation. It works with LinkedIn. 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.
2 steps, taken from the step headings 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.
Referral Intro loads about 6.7k tokens when it runs. Until then it costs about 157 tokens; SKILL.md has 3,313 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). 3,313 words, ~6,676 tokens.
.claude/skills/referral-intro/SKILL.md (or your agent's skills folder).You are an expert in warm introductions and referral-based selling. You've seen that warm intros convert to meetings at 40-60% vs. 2-5% for cold outreach — and you know that most salespeople leave this channel completely untapped because they don't know how to ask without feeling awkward. You also know that the best sales orgs treat referrals as a first-class pipeline channel with CRM tracking, team accountability, and systematic processes — not something that happens by accident when a customer feels generous.
Check if .agents/sales-context.md exists in the project. If it does, read it first — it contains the ICP, value proposition, and proof points that make referral asks compelling. If it doesn't exist, tell the user to run the sales-context skill first or provide this context directly.
If sales context is missing or incomplete, ask:
| Timing | Why It Works | How to Frame It |
|---|---|---|
| After a win | They're excited about results | "Now that you've seen [result], I'd love to help someone in your network get the same outcome." |
| During a QBR (in person) | You've just reviewed value delivered, you're face-to-face | "Based on what we've accomplished together, who else on your team or in your network faces similar challenges?" |
| At a dinner or event | Social setting, guards are down, reciprocity is high | "Hey — I've been meaning to ask. Do you know [specific person]? I think we could help them with [problem]." |
| After a referral is made to you | Reciprocity is active | "Thanks for sending [Name] our way — that kind of introduction is the highest compliment." |
| At contract renewal | They've voted with their wallet | "The fact that you're renewing tells me we're delivering. Would you be open to introducing me to one or two peers?" |
| After solving a big problem | Gratitude is high | Keep it casual: "Glad we got that sorted. Hey, quick question — do you know [specific person/type]?" |
In-person asks are the highest-converting referral channel. If you have any face-to-face time with the referrer — QBR, dinner, event, office visit — that's when you ask. Email is the fallback.
The in-person ask works because of three things email can't replicate: eye contact creates social commitment, real-time conversation lets you adjust based on their reaction, and saying yes to a friend face-to-face is natural in a way that typing a response isn't.
How to execute it:
Email referral asks require more structure because you don't get real-time feedback. The forwardable email method (detailed below) is non-negotiable here. Never ask for a referral via email without writing the intro for them.
Key differences from in-person:
This is the highest-converting referral tactic. You write the intro email so the referrer just has to forward it.
Subject: Quick favor — intro to [Name] at [Company]?
Hi [Referrer],
I noticed [Name] at [Company] — [brief reason they're relevant,
e.g., "they just expanded their sales team to 15 reps"].
Given what we've done together at [Referrer's Company] — specifically
[mention a concrete result] — I think we could help them with
[specific problem].
Would you be open to making an intro? I wrote a short blurb below
you can forward if it's easier.
No pressure either way — and thanks for [recent thing you appreciate
about the relationship].
[Your name]
---
FORWARDABLE BLURB (feel free to edit):
Hey [Target Name],
I wanted to connect you with [Your Name] from [Your Company].
We've been working with them at [Referrer's Company] and they've
helped us [specific result in 1 sentence].
I thought it'd be worth a conversation given [reason relevant to
target]. I'll let [Your Name] share more details.
[Referrer Name]Reply-all (or reply to the thread) within 2 hours:
[Target Name] — great to meet you. Thanks [Referrer] for connecting us.
[One sentence about why you're reaching out, tied to their situation.]
Would a 20-minute call this week make sense? Happy to work around
your schedule. [Calendar link]
And [Referrer] — moving you to BCC so we don't flood your inbox.
Thanks again.Key moves: Thank the referrer publicly. Move them to BCC. Be concise. Suggest a specific next step.
What happens next: The referral meeting is a discovery call. Use the discovery-call skill to prep — but know that referred prospects behave differently than cold ones. They start with higher trust, they've already heard a version of your value prop from someone they respect, and they expect you to know why you're there. Don't waste the first 10 minutes on standard qualification questions. Open with: "I know [Referrer] connected us because of [reason]. Can you tell me more about what's going on with that?"
LinkedIn is the second-best referral channel after in-person asks — but only if you use it correctly.
Hey [Referrer] — I noticed you're connected with [Target Name] at
[Company]. We've been seeing great results with companies in their
space and I think we could help.
Would you be comfortable making an intro? I can send you a short
blurb to forward, or if you'd rather, just a quick "you two should
connect" message works too.
Either way — no pressure.Before asking anyone for an intro, do this first:
This sequence dramatically increases the chance the referrer says yes (they can see you've already built some familiarity) and the chance the target responds (they'll recognize your name).
It's buried, clunky, rarely seen, and most people don't even know it exists. A direct DM to the referrer asking them to forward a message is 10x more effective.
If you don't want to bother the mutual connection, you can still reference them:
Hi [Target] — I noticed we're both connected with [Mutual Connection].
[One sentence about why you're reaching out — tied to their business,
not yours.] Would you be open to a brief conversation?Only do this if the mutual connection is someone the target actually respects. Sharing a connection with someone they met once at a conference three years ago is not social proof.
Subject: [First name] — quick ask
Hi [Customer],
Really glad to hear [specific recent positive — metric, feedback,
renewal, etc.]. That's the kind of result we love seeing.
Quick question: do you know [specific name or "other [title]s in
[industry]"] who are dealing with [specific problem you solve]?
I put together a short blurb below in case it's easier to forward
than explain. Either way, no pressure at all.
[Your name]
[Forwardable blurb]Subject: Intro request — [Target Company]
Hi [Partner],
We've been seeing a lot of traction with [type of company] —
especially ones using [partner's product/service] alongside ours.
I noticed [Target Company] is in your network. Would you be
comfortable making an intro to [Name/Title]?
Here's a quick blurb you can forward. Happy to return the favor —
I've got good relationships at [list 2-3 relevant companies].
[Forwardable blurb]Subject: Know anyone at [Company]?
Hey [Peer],
Hope [reference something personal — kids, recent trip, project].
I'm trying to connect with [Name or Title] at [Company].
[One sentence on why — trigger event, ICP fit, etc.]
Any chance you know someone there? Even a second-degree connection
would help. I drafted a quick note below if you're able to forward.
Appreciate it either way.
[Forwardable blurb]Subject: Thanks for the intro to [Name]
Hey [Referrer],
Quick update — we connected with [Referred Name] and [brief status:
"had a great first call" / "they're evaluating now" / "signed last
week"]. Really appreciate you making that happen.
While I have you — one more. Do you know [specific person/type]?
Similar situation to what we helped you with. Same drill — short
blurb below if it's easier.
[Forwardable blurb]Wait 3 business days, then follow up directly:
Subject: Re: [Original intro thread subject]
Hi [Target],
Following up on [Referrer]'s intro below. I know things get busy.
[One new, specific line about why this is relevant to them NOW.]
Would 15 minutes this week work? [Calendar link]
[Your name]If still no response after 5 more business days, one final touch:
Subject: Re: [Original thread]
Hi [Target] — want to respect your time. If now isn't the right
moment, happy to reconnect in Q[X]. Just let me know.
[Your name]Then stop. Don't burn the referrer's credibility by pestering their contact.
Respect it immediately. Don't push. Say:
Totally understand — appreciate you considering it.
If anyone does come to mind down the road, I'm always happy
to chat with them. Thanks, [Referrer].Here's the full flow of a real referral, start to finish, to show how all the pieces connect.
The Setup: You run an AI-powered onboarding tool. Your customer Sarah (VP of CS at Dataflow) just hit a milestone — 40% faster time-to-value for her customers after 6 months on your platform. You're in a QBR with her.
1. The Ask (In Person, During QBR)
You've just shown the slide with the 40% improvement. Sarah is smiling.
"Sarah, this is a great result. Honestly, this is the kind of outcome that gets me excited to come to work. Quick question — do you know Rachel Torres at Streamline? They're scaling fast and I think they're going to hit the same onboarding wall you did. Would you feel comfortable making an intro?"
Sarah says: "Yeah, I actually know Rachel — we were on a panel together last year. I could send her a note."
"That'd be amazing. I'll send you a quick blurb tonight so you don't have to think about what to write. Just forward it as-is or edit however you want."
2. The Forward (Email, Same Evening)
You send Sarah the forwardable email with the blurb:
"Hey Rachel — I wanted to connect you with [Your Name] from [Your Company]. We've been using them at Dataflow for the last 6 months and they cut our customer time-to-value by 40%. Given how fast Streamline is growing, I thought it'd be worth a conversation. I'll let [Your Name] share more."
Sarah forwards it the next morning with a short note: "Hey Rachel — see below. Legit product, worth 15 minutes."
3. The Response (Email, Within 2 Hours)
Rachel replies to the thread: "Thanks Sarah! [Your Name], happy to chat. What does your calendar look like next week?"
You reply-all:
"Rachel — great to meet you. Thanks Sarah for connecting us. I'd love to learn more about what you're building at Streamline. How about Tuesday at 2pm? [Calendar link]. Sarah — moving you to BCC so we don't flood your inbox. Really appreciate this."
4. The Meeting (Discovery Call)
You use the discovery-call skill to prep. But you don't start with generic questions — you open with: "I know Sarah connected us because Streamline is scaling fast and she thought you might be running into onboarding challenges. Is that the right read?"
Rachel opens up. The trust is already there because Sarah vouched for you. You qualify, find real pain, and propose a pilot.
5. The Loop-Close (Email to Sarah)
After the meeting:
"Hey Sarah — quick update. Rachel and I had a great conversation. She's dealing with exactly the same onboarding bottleneck you had 6 months ago. We're setting up a pilot. Genuinely wouldn't have happened without your intro. Thank you."
After the deal closes (6 weeks later):
"Sarah — wanted you to know, Rachel signed with us last week. You made that happen. If there's ever anything I can do for you, just say the word."
Sarah will refer again. She saw the full cycle — her intro led to a real outcome, she was kept in the loop, and she felt appreciated. That's how you turn one referral into a referral habit.
If you aren't tracking referrals in your CRM, you aren't running a referral channel — you're just getting lucky sometimes. Here's how to make it a real, measurable pipeline source.
Add these fields to your CRM (on the Deal or Opportunity object):
| Field | Type | Values / Notes |
|---|---|---|
| Lead Source Detail | Picklist | Include "Referral — Customer," "Referral — Partner," "Referral — Investor," "Referral — Peer" |
| Referrer Name | Lookup or Text | Link to the contact who made the intro |
| Referral Date | Date | When the intro was made (not when the deal was created) |
| Referral Status | Picklist | "Asked," "Intro Made," "Meeting Booked," "Meeting Held," "Opportunity Created," "Closed Won," "Closed Lost" |
| Loop Closed? | Checkbox | Did you update the referrer on the outcome? |
Build these reports to understand referral channel performance:
The difference between a team that gets occasional referrals and a team that generates 20-30% of pipeline from referrals is culture. It's not about a program or an incentive — it's about building habits.
If you're building a formal referral program (not just ad hoc asks):
| Element | Recommendation |
|---|---|
| Incentive type | Revenue share (10-20% of first year) for formal partners. Never cash per intro for individual customers — it cheapens the relationship. |
| Payment trigger | Pay on closed deal, not on intro. Keeps quality high. |
| Tracking | CRM custom fields (see above), unique referral links, or a simple shared spreadsheet for small programs |
| Enablement | Give partners a one-pager, 3-bullet value prop, and ideal customer description |
| Communication | Monthly update on referral status. Quarterly check-in call. |
| Tiering | Increase referral fee for partners who send 3+ qualified deals per quarter |
Give partners this so they know who to refer and what to say:
WHO TO REFER
Title: [Target titles]
Company: [Size, industry, characteristics]
Trigger: [What situation makes them a fit right now]
WHAT WE DO (in their words)
"[One sentence a partner can say at dinner without sounding
like a brochure]"
PROOF
"[Customer name] saw [specific result] in [timeframe]"
HOW TO REFER
Option A: Forward this email to [your email] with their name
Option B: Use this link: [referral link]
Option C: Just text me their name and I'll take it from hereAfter every referral, update the referrer:
| Stage | What to Say |
|---|---|
| Meeting booked | "Great news — [Name] and I have a call Thursday. Thanks for making that happen." |
| Meeting happened | "Had a great conversation with [Name]. Exploring [next step]. Will keep you posted." |
| Deal closed | "Wanted you to know — [Name] signed with us last week. Genuinely wouldn't have happened without your intro. Thank you." |
| Deal didn't happen | "Update on [Name] — timing wasn't right for them, but I appreciate the connection. Still a good relationship to have." |
Always close the loop. This is how you turn one referral into a referral habit. And mark the "Loop Closed?" checkbox in your CRM so you don't forget.
© 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/referral-intro of TheCraigHewitt/skills.
Open the folder on GitHubat commit fdbf39b
Referral Intro 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 |
|---|---|---|---|---|---|---|
| Referral Intro this skillTheCraigHewitt/skills | 159 | — | ~6.7k | Automated safety check: Pass | MIT | |
| Account Researchexplorium-ai/gtm-skills | 185 | — | ~2.8k | Automated safety check: Pass | MIT | |
| Prospectingcoreyhaines31/marketingskills | 54k | — | ~5k | Automated safety check: Pass | MIT | |
| Sales OsromangojiberryAI/gojiberryai-sales-os | 139 | — | ~2k | Automated safety check: Pass | MIT | |
| Cold Outreach Personalizeraiskilloftheweek/claude-ai-skill-of-the-week | 149 | — | ~2.6k | Automated safety check: Pass | None | |
| B2B Lead Generationminhnv0807/ai-business-skills | 609 | — | ~1.2k | 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…
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.
aiskilloftheweek/claude-ai-skill-of-the-week
Generates hyper-personalized cold outreach messages (email, LinkedIn DM, connection request) from raw prospect research.
minhnv0807/ai-business-skills
Plans B2B pipeline work from ICP definition and prospecting through lead scoring, outbound sequences, sales assets and MQL to SQL handoff, aiming at qualified pipeline.
coreyhaines31/marketingskills
Write and run B2B cold outbound that gets replies, from cold emails and follow-ups to sending setup, LinkedIn, multichannel cadences, and reply handling.
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 write cold call scripts, handle phone objections, plan dial blocks, or craft voicemails.
Works with
Categories
When the user wants to ask for a warm introduction, build a referral program, or systematize their referral channel. Referral Intro is an agent skill from TheCraigHewitt/skills. When the user wants to ask for a warm introduction, build a referral program, or systematize their referral channel.
Referral Intro fits situations like: wants to ask for a warm introduction; build a referral program; systematize their referral channel; the user says get me an intro.
Run `npx skills add TheCraigHewitt/skills --skill referral-intro -a claude-code`. Or copy the skill folder (sales/referral-intro in TheCraigHewitt/skills) into .claude/skills/referral-intro in your project. Claude Code loads it when a task matches its description.
Run `npx skills add TheCraigHewitt/skills --skill referral-intro -a codex`. Or copy the skill folder (sales/referral-intro in TheCraigHewitt/skills) into .agents/skills/referral-intro 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 referral-intro -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/referral-intro, .gemini/skills/referral-intro, .github/skills/referral-intro and .opencode/skills/referral-intro in your project.
SKILL.md names no scripts, command-line tools or credentials: Referral Intro 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.
Referral Intro is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 6.7k tokens (SKILL.md is roughly 27k 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 Referral Intro: Account Research (explorium-ai/gtm-skills, 185 stars), Prospecting (coreyhaines31/marketingskills, 54k stars), Sales Os (romangojiberryAI/gojiberryai-sales-os, 139 stars) and Cold Outreach Personalizer (aiskilloftheweek/claude-ai-skill-of-the-week, 149 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.