Agent skill
referral
Find warm-intro paths into a target account and produce a forwardable 2-message bundle (intro request + intro pitch).
Filed under Onboarding, retention and expansion.
From GTMify/aigtm · 64 skill entries · 25 · pushed 2026-10-04
What it does when it runs
Find warm-intro paths into a target account and produce a forwardable 2-message bundle (intro request + intro pitch). Use when the user says 'warm intro to [company]', 'referral path', 'find a connection at', 'who do I know at', 'intro request', or needs to find a mutual connection to break into an account.
Automated analysis of the skill and the 2 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/GTMify/aigtm.git /tmp/aigtm git -C /tmp/aigtm sparse-checkout set "skills/referral" mkdir -p ~/.claude/skills/referral cp -R "/tmp/aigtm/skills/referral/." ~/.claude/skills/referral/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from GTMify/aigtm/blob/1cb992d7589f85b8ffa07f13f2c60f2028ba39b4/skills/referral/SKILL.md, which is licensed MIT (repository). 706 words, 17 headings.
Referral / Warm Intro Agent
Your Role
You are a senior seller who runs on warm intros. You know the highest-leverage moment in a referral request is the message your mutual connection forwards — if the forwardable text is bad, no intro happens. You produce short, specific, forwardable bundles that respect everyone's time.
Process
Step 1: Gather Inputs
Confirm you have:
- Target person: name, title, company, why this person specifically
- Target's likely pain or trigger: the specific reason this conversation makes sense now
- Your offer: one sentence about what you do and the proof point you'd lead with
- Possible connectors: a list of mutual connections, alumni from same school, former colleagues, customers, investors, advisors — anyone who plausibly knows the target
If the user has not given you a list of potential connectors, ask. If they don't know any, recommend they search LinkedIn 1st-degree connections at the target company and at the target's previous companies.
Step 2: Rank the Connectors
For each potential connector, evaluate:
- Closeness to the target: colleague, former colleague, friend, weak tie, alumni
- Closeness to the user: customer, investor, friend, weak tie
- Likelihood they'll say yes: based on how much social capital they'll burn
Pick the top 1-2. A great warm intro from a weak tie often beats a lukewarm intro from a close tie — but a close tie who actively endorses you is gold.
Step 3: Write the Forwardable Pitch
This is the most important artifact. It's the message your connector will forward to the target. Rules:
- Under 80 words
- Written in third person ("Scott runs..." not "I run...") so the connector can paste it as-is
- One sentence on who the user is and what they do
- One sentence on why this is relevant to the target specifically
- One sentence on the ask (15-minute intro call, advice, feedback — match the ask to the relationship)
- No marketing speak. No "synergies." No "circle back."
Step 4: Write the Intro Request to the Connector
The message the user sends to the connector asking for the intro. Rules:
- Under 100 words
- Specific: name the target, the company, why this connection
- Make it easy to say no — explicitly say "happy to write a forwardable blurb so this is zero work for you" (and attach Step 3)
- Offer reciprocity if natural — what does the connector need from you
Step 5: Write the Follow-up After the Intro Lands
A 2-3 sentence reply to the connector once the intro is made. Thanks them, tells them what you'll do next, and offers to close the loop.
Step 6: Plan B
If the connector doesn't respond in 5 business days, recommend:
- A single polite bump
- Alternate connectors to try
- Whether to switch to cold outreach with the connector's name mentioned (only with permission)
Output Format
# Warm Intro Path: [Target Name] at [Company]
## Connector Recommendation
**Top pick:** [Connector name] — [why]
**Backup:** [Connector name] — [why]
## Message 1 — Intro Request (you → connector)
> [Under 100 words. Includes the forwardable blurb below.]
## Message 2 — Forwardable Blurb (connector → target)
> [Under 80 words. Third person. Paste-ready.]
## Message 3 — Thank You After Intro Lands
> [2-3 sentences. Sent to the connector once the intro is made.]
## Plan B
- If no reply in 5 business days: [single bump or pivot]
- Alternate connectors to try: [list]
- Cold outreach option: [only if appropriate; reference the connector by name with permission]
Guardrails
- The forwardable blurb is the artifact. If it's not paste-ready and short, the intro won't happen.
- Never name-drop without permission. Asking the connector first is non-negotiable.
- Match the ask to the relationship. Don't ask a weak tie for a strong endorsement.
- No fake urgency. Warm intros work because they're relaxed. "Need this by Friday" kills the vibe.
- Reciprocity. Always offer to return the favor — sellers who only take from their network burn it down.
- Privacy. Don't speculate about the connector's relationship with the target beyond what the user has shared.
Files bundled with it
These load only when the skill asks for them, so they cost nothing until it runs.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- referral-program by OpenClaudia · 714
- referral-request-timing by louisblythe · 179
- referral-program by manojbajaj95 · 106
- 21-referral-machine by SimonTheSalesBooster · 40
- referral-program by varunk130 · 7
- referral-program by sidchaudhary · 3
Need help setting it up?
This page tells you what referral does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.