agentleFS
Sign inStart free
prosyo-aiprosyo-ai/gtm-skill/skills/referral-ask/SKILL.md

referral-ask

Skill13 starsChanged 24 days agoMITView on GitHub

Use this skill when you want introductions and referrals from happy customers, partners or your network: \"ask for a referral\", \"get warm intros\", \"customer referral program\", \"write an introduction request\". Picks the right moment and the right people to ask, makes the ask specific (named companies or roles), writes a forwardable blurb so the introduction takes the referrer one minute, and follows up and thanks properly. Warm introductions convert far better than any cold channel.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this to turn goodwill into introductions.

    line 16
  2. Distinctive:

    Ask the referrer to check with their contact first, so the introduction is welcome.

    line 33
  3. Distinctive:

    Every referrer hears back about the outcome.

    line 55
  4. Distinctive:

    MUST use double opt-in introductions.

    line 60
  5. Distinctive:

    MUST disclose any referral reward and respect the referrer's company policies.

    line 61
  6. Distinctive:

    NEVER contact someone claiming a referral that has not happened.

    line 62
  7. Distinctive:

    NEVER ask a customer with an open problem for a referral.

    line 63

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Use this to turn goodwill into introductions. Most people are happy to refer; they just need a specific ask and an easy way to do it.

Inputs

  • Customers or contacts who are happy (recent results, good feedback, renewals).
  • Target accounts or roles you want to reach, and any known connections.
  • Recent wins to reference.

The play

1. Ask at the right moment

Right after a visible win: a result they shared, a renewal, a great review, a successful rollout, a thank-you message from them. Not during an open support issue.

2. Make the ask specific

"Do you know anyone who might need this?" gets "I'll think about it." Instead, name two or three companies or a precise role: "I noticed you're connected to Dev at Lumen and know the ops team at Fabrikam. Would either be open to a short intro?"

3. Use a double opt-in

Ask the referrer to check with their contact first, so the introduction is welcome. Offer to send a forwardable blurb.

4. Write the forwardable blurb

Three or four sentences the referrer can paste: who you are, what you did for them, why it might matter to the contact, and an easy next step. Written in the referrer's voice, short enough to forward from a phone.

Dev, thought of you: Sam at Acme helped us cut month-end close from 9 days to 4. Given your new entities at Lumen, might be worth 20 minutes. Happy to connect you if useful.

5. Follow up and thank

Reply to the introduction within hours, move the referrer to bcc, and tell them what happened afterwards. Thank them whatever the outcome; a handwritten note or a small, appropriate gesture works. Follow any rules their company has about gifts, and disclose referral rewards.

Templates

The ask

Hi Priya, really glad the 4-day close held through quarter end. One favour: you mentioned knowing the finance lead at Fabrikam. Would they be open to an intro? I've drafted a short note below you could forward if they are. No pressure at all if it's not a fit.

Thank-you after an intro

Priya, thank you for connecting me with Lena. We've got a call next week. I'll let you know how it goes, and I owe you one.

What good looks like

  • Asks name specific people or companies.
  • The referrer spends under a minute.
  • Every referrer hears back about the outcome.
  • The common mistake is a quarterly mass email asking all customers for "any referrals", which almost never produces introductions.

Rules

  • MUST use double opt-in introductions.
  • MUST disclose any referral reward and respect the referrer's company policies.
  • NEVER contact someone claiming a referral that has not happened.
  • NEVER ask a customer with an open problem for a referral.

Example prompts

  • "Priya just renewed and shared great results. Write a referral ask for two specific companies."
  • "Write a forwardable blurb for our customers to send to peers."
  • "Design a simple customer referral program for a B2B SaaS."

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free