agentleFS
vindreshsinghvindreshsingh/engineering-skills/skills/marketing/referral-loop/SKILL.md

referral-loop

Skill0 starsChanged 5 months agoMITView on GitHub

Designs viral and referral mechanics that turn happy users into growth — invite flows, incentives, and share loops. Use for network products, community platforms, or when word-of-mouth should drive sign-ups.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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 referral-loop checklist alongside this process.

    line 15
  2. Distinctive:

    Never ask on sign-up screen before first value.

    line 39
  3. Distinctive:

    Prefer access and status over cash for dev audiences.

    line 66
  4. Distinctive:

    Ask to refer before first success

    line 101
  5. Distinctive:

    No referrer context on friend's landing page

    line 104

≈ “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

Referral Loop

The best channel is users inviting users — especially for connection products where value grows with network size. Referral fails when the invite is spammy or the incentive feels like a pyramid scheme.

Chains from [[growth-strategy]] (ICP, north-star metric) and [[community-engagement]] (engaged users refer more). Complements [[email-nurture]] (referral prompts in sequences) and [[social-distribution]] (share assets).

Use referral-loop checklist alongside this process.

When to Use

  • Network/product value increases with more users (developer-connection, communities)
  • NPS or satisfaction high but organic invites low
  • Launching invite-only or waitlist with referral priority
  • Adding "invite a friend" to activation flow

Skip when: product isn't shareable, no clear invite moment, or core experience broken (fix product first).

Process

1. Find the natural invite moment

Best triggers — user just got value:

MomentExample copy
First successful connection"Know someone who'd benefit?"
Profile complete"Invite a colleague to join you"
Weekly win"Share what you built"
Waitlist"Move up by inviting friends"

Never ask on sign-up screen before first value.

2. Design the loop

User gets value → Prompt to share → Easy share mechanism → Friend lands → Friend activates
       ↑___________________________________|
              (reward optional)

Components:

  • Share link — unique referral URL per user (?ref=username)
  • Share copy — pre-written message user can edit (X, LinkedIn, email, copy link)
  • Landing — friend sees referrer context ("Alex invited you")
  • Tracking — attribute sign-up to referrer
  • Reward (optional) — both sides benefit; keep ethical and simple

3. Incentive design (developer products)

TypeExampleRisk
AccessSkip waitlist, unlock featureLow — preferred
StatusBadge, early accessLow
Mutual benefitBoth get premium weekMedium — monitor abuse
Cash/gift cards$10 per referralHigh — fraud, wrong incentives

Prefer access and status over cash for dev audiences.

4. Anti-abuse

  • Cap rewards per month
  • Require referred user to activate (not just sign up) before reward
  • Block self-referrals and disposable emails
  • Manual review if spike detected

5. Launch and measure

MetricFormula
Invite rate% MAU who sent ≥1 invite
Viral coefficient (K)invites × conversion rate
Referral % of sign-upsreferred / total new
Referred user activationvs organic cohort

K > 0.15 is meaningful for early products; K > 1.0 is exceptional.

6. Promote the loop

  • In-app prompt at invite moment
  • Email Day 7 in [[email-nurture]] sequence
  • Community showcase of top referrers ([[community-engagement]])
  • Social template for [[social-distribution]]

Common Rationalizations

  • "Referral widget on homepage is enough" — Homepage visitors haven't experienced value yet.
  • "Cash will make it viral" — Attracts fraud; devs prefer access/status.
  • "No reward needed" — Small mutual benefit increases share rate 2x without feeling salesy.

Red Flags

  • Ask to refer before first success
  • Referral link broken or not tracked
  • Reward on sign-up only — bots inflate numbers
  • No referrer context on friend's landing page
  • Pyramid-style multi-level rewards

Verification

  • Invite moment identified (post-value, not pre-value)
  • Share link, copy, landing page, tracking designed
  • Incentive chosen with abuse caps
  • Activation required before reward pays out
  • Metrics dashboard or spreadsheet template ready
  • In-app + email promotion planned

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.