Agent skill

Referral Intro

by TheCraigHewitt in TheCraigHewitt/skills

When the user wants to ask for a warm introduction, build a referral program, or systematize their referral channel.

MITAuto-check passedSales & Support

Install Referral Intro

skills CLI
$ npx skills add TheCraigHewitt/skills --skill referral-intro -a claude-code

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

GitHub CLI
$ gh skill install TheCraigHewitt/skills referral-intro --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/referral-intro .claude/skills/referral-intro && 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
referral-intro
GitHub stars
159
Token cost
~6.7k tokens
SKILL.md length
3,313 words
Files
1
Skills in repo
65
Repo updated
First seen
Licence
MIT

At a glance

When the user wants to ask for a warm introduction, build a referral program, or systematize their referral channel.

  • Works in 2 steps: The Ask (To Your Referrer) → After the Intro is Made
  • Wants to ask for a warm introduction
  • SKILL.md covers Before Starting, Context Questions, Core Principles and Timing the Ask, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

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.

When your agent uses it

  • Wants to ask for a warm introduction
  • Build a referral program
  • Systematize their referral channel
  • The user says get me an intro

Example prompts

  • “get me an intro,”
  • “ask for a referral,”
  • “write a forwardable email,”
  • “/referral-intro”

Workflow steps

2 steps, taken from the step headings in SKILL.md.

  1. The Ask (To Your Referrer)
  2. After the Intro is Made

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

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.

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

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). 3,313 words, ~6,676 tokens.

Download SKILL.mdSave it as .claude/skills/referral-intro/SKILL.md (or your agent's skills folder).
name
referral-intro
description
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 outbound-sequence. For running the meeting after a referral intro is made, see discovery-call.
metadata.version
1.0.0

Referral & Warm Introductions

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.

Before Starting

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.

Context Questions

If sales context is missing or incomplete, ask:

  1. Who are you trying to reach? Specific company, title, or type of buyer.
  2. Who could introduce you? Current customers, partners, investors, peers, former colleagues.
  3. What value have you delivered to the potential referrer? Recent wins, results, or goodwill.
  4. What's the relationship strength? Close contact vs. loose acquaintance — this changes the ask format.
  5. Is this a one-off ask or are you building a repeatable referral process? The playbook changes significantly.

Core Principles

  1. Make it effortless for the referrer. Write the intro email for them. Draft the LinkedIn message. Do all the work — they just hit forward. The moment you create work for someone, the referral dies.
  2. Earn the right to ask. The best time to ask for a referral is right after delivering value — a successful onboarding, a big win, a renewed contract. The worst time is before you've proven anything.
  3. Be specific about who you want to meet. "Do you know anyone who might benefit?" gets nothing. "Do you know the VP of Sales at Acme Corp?" gets intros. Specificity makes it easy for the referrer's brain to pattern-match.
  4. Always close the loop. Tell the referrer what happened. Did the meeting happen? Did the deal close? People who see their referrals go into a black hole never refer again.
  5. Referrals are a channel, not an accident. Track them in your CRM. Measure conversion. Build team habits around asking. The best referral programs look like outbound programs with better win rates.
  6. Never offer cash incentives to individual referrers. Revenue share for formal partner programs is fine. But offering a customer $500 to intro you to their friend cheapens the relationship and signals that the intro isn't worth making on merit. The best referrals come from genuine belief in your product, not a bounty. If you need to pay people to recommend you, fix the product.
  7. In-person asks convert 2-3x higher than email asks. A referral request at dinner, at a QBR, or at a conference has eye contact, social reciprocity, and real-time commitment. Email asks are easy to ignore. Prioritize face-to-face whenever possible.

Timing the Ask

Best Moments to Ask
TimingWhy It WorksHow to Frame It
After a winThey'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 eventSocial 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 youReciprocity is active"Thanks for sending [Name] our way — that kind of introduction is the highest compliment."
At contract renewalThey'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 problemGratitude is highKeep it casual: "Glad we got that sorted. Hey, quick question — do you know [specific person/type]?"
When NOT to Ask
  • During onboarding (too early, no results yet)
  • When there's an open support issue or complaint
  • Right after a price increase
  • When the relationship is purely transactional with no rapport
  • More than once per quarter to the same person
  • Via email when you could ask in person next week

In-Person vs. Email Referral Asks

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.

In-Person Ask (QBR, Dinner, Event)

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:

  1. Don't lead with the ask. Wait until the conversation has hit a natural high point — they've just told you about a great result, you've laughed about something, the QBR slides showed strong numbers.
  2. Transition casually. "Hey, random question — do you know [Name] at [Company]?" or "This is great. I wish more [title]s knew about this. Who in your network should I be talking to?"
  3. If they say a name, lock it in immediately. "Amazing. Would you be cool if I drafted a quick intro note you can send? I'll email it to you tonight so you can just forward it."
  4. If they hesitate, give them a narrower prompt. "Even a second-degree connection would help. Anyone at [Company] or [Company]?"
  5. Send the forwardable email within 2 hours. The commitment is fresh. Wait a week and they'll forget they offered.
Email Ask (When In-Person Isn't Available)

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:

  • Be shorter. An email ask should be under 100 words above the forwardable blurb.
  • Give them an out. "No pressure either way" isn't just polite — it preserves the relationship for future asks.
  • Follow up once if they don't respond. Then stop. Pestering via email is worse than pestering in person.

The Forwardable Email Method

This is the highest-converting referral tactic. You write the intro email so the referrer just has to forward it.

Step 1: The Ask (To Your Referrer)
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]
Step 2: After the Intro is Made

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-Specific Referral Mechanics

LinkedIn is the second-best referral channel after in-person asks — but only if you use it correctly.

When to Use LinkedIn for Intros
  • You can see a mutual connection but don't have a strong enough relationship to email them directly
  • The referrer is more active on LinkedIn than email (common with executives who have gatekeepers)
  • You want to warm up the target before asking the referrer for a formal intro
How to Ask for an Intro via LinkedIn DM
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.
How to Warm Up a Target Using Mutual Connections

Before asking anyone for an intro, do this first:

  1. Check mutual connections. Filter by 1st-degree connections at the target's company or in their network.
  2. Engage with the target's content first. Like 2-3 posts. Leave one thoughtful comment. Do this over 1-2 weeks. Don't be weird about it — one comment, not ten.
  3. Then ask the mutual connection. "I've been engaging with [Target] on LinkedIn — we have overlapping interests in [topic]. Would you feel comfortable introducing us?"

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).

Never Use LinkedIn's Built-In "Request an Introduction" Feature

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.

Direct LinkedIn Outreach When You Share a Connection

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.

Templates by Source

Asking a Customer
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]
Asking a Partner
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]
Asking a Peer / Industry Contact
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]
Asking After They Referred Someone Else
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]

Following Up on Warm Intros

If the Target Doesn't Respond After the Intro

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.

If the Referrer Says No

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].

End-to-End Example: A Referral From Ask to Close

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.

Show full SKILL.md (1,230 more words)Show less

CRM Tracking for Referrals

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.

Custom Fields

Add these fields to your CRM (on the Deal or Opportunity object):

FieldTypeValues / Notes
Lead Source DetailPicklistInclude "Referral — Customer," "Referral — Partner," "Referral — Investor," "Referral — Peer"
Referrer NameLookup or TextLink to the contact who made the intro
Referral DateDateWhen the intro was made (not when the deal was created)
Referral StatusPicklist"Asked," "Intro Made," "Meeting Booked," "Meeting Held," "Opportunity Created," "Closed Won," "Closed Lost"
Loop Closed?CheckboxDid you update the referrer on the outcome?
Attribution Reports

Build these reports to understand referral channel performance:

  • Referral conversion funnel: What % of asks turn into intros? Intros into meetings? Meetings into deals?
  • Referral pipeline by source type: Which referrer types (customer, partner, peer) generate the most pipeline?
  • Deal size and velocity (referral vs. other sources): Referral deals are typically 15-25% larger and close 30-50% faster. Track this to justify investment in the channel.
  • Top referrers: Who are your best referral sources? These are your advocates — invest in the relationship.

Building a Referral Culture

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.

Make Referral Asks a Standard Operating Procedure
  • Add a referral ask step to your QBR template. Every QBR should include a slide on who you'd like to meet. Not optional. Not "if it feels right." Every time.
  • Add a referral ask to your renewal process. After the contract is signed, the CSM (or rep) asks for 1-2 specific intros. Script it so it doesn't feel awkward.
  • Add a referral ask to your post-onboarding check-in. The customer just went live, they're seeing value, the gratitude window is open.
Team Accountability
  • Track referral asks per rep, not just referral outcomes. If reps aren't asking, they won't get referrals. Measure the behavior, not just the result.
  • Share referral wins in team meetings. "James got a referral from Acme Corp this week — it's already an opportunity." This normalizes asking and creates positive peer pressure.
  • Referral leaderboard (optional but effective). Show who is asking, who is getting intros, and who is converting. Keep it visible. Don't attach comp to it — the visibility alone drives behavior.
What NOT to Do
  • Don't attach cash bonuses to individual referral asks. The incentive should be pipeline and commission on the resulting deal — not a bounty on the ask itself.
  • Don't make it a quarterly "referral blitz." Consistency beats intensity. A one-week push followed by 12 weeks of nothing trains customers to ignore you.
  • Don't create a complicated referral portal. Nobody is logging into your referral platform. Make it email-based, frictionless, and human.

Partner Referral Programs

Program Structure

If you're building a formal referral program (not just ad hoc asks):

ElementRecommendation
Incentive typeRevenue share (10-20% of first year) for formal partners. Never cash per intro for individual customers — it cheapens the relationship.
Payment triggerPay on closed deal, not on intro. Keeps quality high.
TrackingCRM custom fields (see above), unique referral links, or a simple shared spreadsheet for small programs
EnablementGive partners a one-pager, 3-bullet value prop, and ideal customer description
CommunicationMonthly update on referral status. Quarterly check-in call.
TieringIncrease referral fee for partners who send 3+ qualified deals per quarter
Enablement One-Pager for Partners

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 here

Closing the Loop

After every referral, update the referrer:

StageWhat 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.

Common Mistakes

  • Asking too broadly. "Know anyone who could use our product?" is impossible to answer. Be specific about the person, company, or at least the type.
  • Not writing the forwardable email. Asking for a referral without doing the work is asking someone to write marketing copy for you. They won't.
  • Asking too early. If you haven't delivered value yet, you haven't earned the ask. Wait.
  • Never closing the loop. The referrer wants to know what happened. If you ghost them, they'll never refer again.
  • Treating referrals as one-off. Build it into your process — after every QBR, after every renewal, after every successful project milestone.
  • Defaulting to email when you have face time. If you're seeing the customer next week at a dinner or QBR, wait and ask in person. It's worth the delay.
  • Offering cash incentives to customers. Partner programs with revenue share are fine. Paying a customer $500 per intro makes the relationship transactional and the intro feel bought. People refer because they believe in your product, not because you're paying them to.
  • Not tracking referrals in the CRM. If you can't tell your VP of Sales how many referral-sourced deals you closed last quarter, referrals aren't a channel — they're a coincidence.
  • Sending the intro via LinkedIn's built-in feature. It's buried, rarely checked, and most people don't know it exists. DM or email, always.
  • Asking via LinkedIn DM when you have their email. LinkedIn DMs get lost in connection requests and InMail spam. Use LinkedIn for warming up, use email for the actual ask.

Strong Takes

  • The best referrers are your happiest customers, not your closest friends. A customer who saw 40% improvement and wants to tell people is more valuable than a college buddy doing you a favor. The first creates urgency; the second creates obligation.
  • Referral programs with complex tiers and portals are a waste of money. Make it easy to refer, close the loop. That's it. Every dollar on a referral portal should go to customer success instead.
  • If a customer won't refer you, that's diagnostic information. Either they're not seeing enough value (fix the product), they're not the right person (find a champion), or they don't know who you're looking for (be more specific).
  • Never batch referral asks. Sending the same request to 20 customers on the same day is outbound masquerading as referrals. Each ask should be personalized, timely, and tied to a specific moment of value delivery.
  • discovery-call — The natural next step after a referral intro lands a meeting. Prep differently for referred prospects — they start with higher trust.
  • lead-research — Research the target before asking for the intro. Knowing their situation makes the forwardable blurb specific and compelling.
  • outbound-sequence — Layer referral asks into multi-channel sequences
  • linkedin-outreach — Use LinkedIn mutual connections as a warm path. The LinkedIn mechanics in this skill complement linkedin-outreach.
  • cold-email — Fall back to cold email when no warm path exists
  • event-networking — Events create natural referral opportunities. In-person asks at dinners and conferences are the highest-converting referral channel.
  • call-debrief — Debrief after the referral meeting to capture next steps and update the referrer.

© 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/referral-intro of TheCraigHewitt/skills.

Open the folder on GitHubat commit fdbf39b

Compare with similar skills

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.

Referral Intro compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Referral Intro this skillTheCraigHewitt/skills159—~6.7kAutomated safety check: PassMIT
Account Researchexplorium-ai/gtm-skills185—~2.8kAutomated safety check: PassMIT
Prospectingcoreyhaines31/marketingskills54k—~5kAutomated safety check: PassMIT
Sales OsromangojiberryAI/gojiberryai-sales-os139—~2kAutomated safety check: PassMIT
Cold Outreach Personalizeraiskilloftheweek/claude-ai-skill-of-the-week149—~2.6kAutomated safety check: PassNone
B2B Lead Generationminhnv0807/ai-business-skills609—~1.2kAutomated 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 3 days ago
    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 2 days ago
    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
  • Cold Outreach Personalizer

    aiskilloftheweek/claude-ai-skill-of-the-week

    Generates hyper-personalized cold outreach messages (email, LinkedIn DM, connection request) from raw prospect research.

    149 GitHub stars~2.6k tokensUpdated 4 mo ago
    Sales & SupportAuto-check passed
  • B2B Lead Generation

    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.

    609 GitHub stars~1.2k tokensUpdated 29 days ago
    Sales & SupportAuto-check passed
  • Cold Email

    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.

    54k GitHub stars~3.1k tokensUpdated 2 days 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
  • Cold Call

    TheCraigHewitt/skills

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

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

Works with

Categories

Questions about Referral Intro

What does Referral Intro do?

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.

When should I use Referral Intro?

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.

How do I install Referral Intro in Claude Code?

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.

How do I install Referral Intro in Codex?

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.

Can I use Referral Intro 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 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.

What does Referral Intro need to run?

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

Does Referral Intro 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 Referral Intro 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 Referral Intro use?

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.

How many tokens does Referral Intro use?

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.

What are the alternatives to Referral Intro?

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.

Who maintains Referral Intro?

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.