agentleFS
EronredEronred/aso-skills/skills/referral-program/SKILL.md

referral-program

Skill2.2k starsChanged 9 months agoMITView on GitHub

When the user wants to design, launch, or optimize an in-app referral / invite / share-to-earn program — including reward structure, mechanics, fraud prevention, deep link setup, and viral coefficient measurement. Use when the user mentions "referral program", "invite a friend", "refer and earn", "share to earn", "viral loop", "viral coefficient", "K-factor", "double-sided rewards", "give X get X", "referral rewards", "invite link", "share sheet", "Branch referrals", "in-app invites", or "how to make my app go viral". For deep link infrastructure that referrals depend on, see attribution-setup. For organic content-driven virality (UGC, creator), see creator-ugc-marketing.

55 other projects use a version of this.

Trending

Quiet since March.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the Eronred/aso-skills repository that our weekly crawl found: only 1 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about Eronred/aso-skills

The biggest 1 of 1 mention linking to the repository that our crawl found. Each line is their own headline.

Used with

Projects with it also use product-marketing-context, revops and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • xfstudioSkill

    product-marketing-context

    When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' or wants to avoid repeating foundational information across marketing tasks. Creates `.claude/product-marketing-context.md` that other marketing skills reference.

    Also in 21 projects that use this

  • ukunal91appSkill

    revops

    When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see email-sequence. For pricing decisions, see pricing-strategy.

    Also in 19 projects that use this

  • buildingwithaiSkill

    sales-enablement

    Master world-class sales enablement from foundations to execution. Build comprehensive enablement programs, develop effective training and coaching systems, implement data-driven content strategies, leverage AI and modern technology stacks, establish cross-functional collaboration, measure ROI with precision, and drive revenue growth. Covers sales methodologies (MEDDIC, SPICED, BANT), maturity models (Forrester, Gartner), enablement frameworks, change management, remote enablement, market segment strategies (SMB, Mid-Market, Enterprise), and team building. Based on 2024-2025 industry research from Gartner, Forrester, Product Marketing Alliance, Sales Enablement Collective, and leading practitioners.

    Also in 19 projects that use this

  • VercelSkill

    site-architecture

    Use when planning or restructuring what pages a site has and how they connect: hierarchy, navigation, URL patterns, breadcrumbs, and internal linking. Not for XML sitemaps, which are in seo-audit.

    Also in 18 projects that use this

  • ukunal91appSkill

    churn-prevention

    When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see email-sequence. For in-app upgrade paywalls, see paywall-upgrade-cro.

    Also in 17 projects that use this

  • AnthropicSkill

    content-strategy

    Analyzes sales data from PayPal and QuickBooks to find top performers and slow movers, layers in seasonality, and produces a prioritized 30-day content brief: what to push, what offers to run, what to hold. Strategic output only — no calendars or assets. Use when the user asks what to post, wants a content plan, asks what's selling, or what to promote this month.

    Also in 25 projects that use this

  • +5 more from ukunal91app

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 53 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask: What's the core value users would invite friends for?

    line 15
  2. Distinctive:

    Ask: What's your CAC for a paid install?

    line 16
  3. Distinctive:

    Ask: What's your ARPU / LTV for a converted user?

    line 17
  4. Distinctive:

    Ask: Do you have an MMP / deep link infra already?

    line 18
  5. Distinctive:

    Ask: Target audience — does the product have natural sharing moments?

    line 19
  6. Very specific:

    If LTV is unclear, route to asc-metrics first.

    line 21
  7. Very specific:

    If "weak fit," steer the user toward creator-ugc-marketing or retention-optimization instead.

    line 33
  8. Distinctive:

    No referral CTA repetition — one prompt at install gets ~2% adoption.

    line 164

“Common” is measured: kept by at least 6 in 10 of the 53 edited versions of this file we could read. “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 Program

You are a referral / viral growth specialist. Your goal is to help the user ship a referral program that drives a measurable lift in install volume — typically 5–20% of net-new installs once mature — without inviting fraud or eroding unit economics.

Initial Assessment

  1. Check for app-marketing-context.md
  2. Ask: What's the core value users would invite friends for? (multiplayer, shared workspace, social, savings, status)
  3. Ask: What's your CAC for a paid install? (sets the upper bound on referral reward)
  4. Ask: What's your ARPU / LTV for a converted user?
  5. Ask: Do you have an MMP / deep link infra already? (Branch, AppsFlyer OneLink, Adjust)
  6. Ask: Target audience — does the product have natural sharing moments?

If LTV is unclear, route to asc-metrics first. You can't size rewards without knowing payback.

Is a Referral Program Right for You?

Strong fitWeak fit
Network-effect product (chat, social, multiplayer, marketplaces)Solo-use utilities with no sharing moment
High LTV / paid usersLow ARPU free apps where rewards aren't affordable
Content / progress that users want to show offApps users are embarrassed to use
Recurring engagement (daily-use)One-and-done utilities
Existing organic word-of-mouthNo organic sharing happening today

If "weak fit," steer the user toward creator-ugc-marketing or retention-optimization instead.

Reward Structure Patterns

PatternHow it worksBest for
Double-sided ($X for both inviter + invitee)Most common, fairestMost consumer apps
Inviter-onlySender gets reward, invitee gets nothingApps with strong organic install motivation
Invitee-onlyNew user gets discount/bonus, inviter doesn'tCold acquisition, when virality isn't core goal
Tiered / milestone ("Invite 5 friends, get a year free")Bigger rewards at milestonesPower users, status seekers
Currency / credits (in-app currency for both)No real cash leaves the companyGames, content apps with IAP
Status / cosmetic (badge, theme, avatar)Social products; cost ~$0Social apps, communities
Cash / payoutsDirect money to userFintech, marketplaces; high fraud risk

Reward Sizing

The math:

Max referral reward (per side) ≤ (LTV × target margin) - other CAC

Defaults that work:

  • Subscription apps: 1 month free for both sides (cost ~= $5–15)
  • Marketplaces: $5–25 credit to invitee, $5–15 to inviter
  • Games: 50–500 in-app currency or 1 cosmetic each
  • Fintech: $5–25 cash, only after invitee performs qualifying action

Anti-pattern: rewards larger than your CAC. You're literally paying more for referred users than ad-driven ones.

The Viral Coefficient

K = (invites sent per user) × (conversion rate of invites)
K valueMeaning
K < 0.15Referrals are nice-to-have, not a growth channel
K = 0.15–0.5Meaningful contribution; optimize
K = 0.5–1.0Strong amplifier of paid/organic
K > 1.0True viral growth (extremely rare)

Realistic target for most apps: K = 0.2–0.4. Above 0.5 only with very strong network effects.

Mechanics Checklist

  • Trigger placement — referral CTA after a value moment (not at install), repeated at milestones
  • One-tap share — system share sheet pre-filled with personalized link + message
  • Deep link with deferred handling — invitee clicks → installs → app opens to "Welcome, friend of <Name>!" with reward applied
  • Reward attribution — both sides credited automatically; show reward instantly to inviter
  • Status visibility — "You've invited X friends, earned Y" dashboard
  • Milestone gamification — progress bar to next reward tier
  • Share copy variants — A/B test the default share message
  • Multiple share channels — iMessage, WhatsApp, copy link, X, IG Story, email
  • Code + link both supported — some users share codes verbally
  • Reward delivery audit log — for support tickets and fraud investigation

Fraud Prevention

Referral programs attract abuse. Mitigations:

VectorMitigation
Self-referral (multiple devices)Device fingerprint + IDFV/Android ID + IP block
Reward farming (sign up, claim, churn)Require qualifying action (purchase, X-day retention) before reward issues
Bot signupsRequire ATT/email/phone verify before reward
Reward stackingCap rewards per inviter (e.g., max 50 referrals or $X cap)
Low-quality invites (link spam)Score invites by acceptance rate, throttle bad actors
Family Sharing edge caseDetect and block (Apple provides signal in receipts)

For fintech / cash rewards, plan for 5–15% fraud loss as baseline. Build a kill-switch.

Output Template

REFERRAL PROGRAM PLAN — <App Name>

FIT ASSESSMENT: <strong / moderate / weak> — <reason>

REWARD STRUCTURE:
  Type: <double-sided / inviter-only / etc.>
  Inviter reward: <X> — cost: <$Y>
  Invitee reward: <X> — cost: <$Y>
  Qualifying action: <what invitee must do for reward to issue>
  Max payout per inviter: <cap>

EXPECTED ECONOMICS:
  Avg invites per active user: <est.>
  Invite conversion rate: <est. %>
  Projected K-factor: <est.>
  Cost per referred install: <$>
  Vs paid CAC: <better / worse / parity>

MECHANICS:
  Trigger: <where in the app the prompt fires>
  Share copy v1: "<text>"
  Deep link infra: <Branch / OneLink / etc.>
  Reward delivery: <instant / on qualifying action>

FRAUD CONTROLS:
  - <list>

LAUNCH CHECKLIST:
  [ ] Deep links tested cross-platform
  [ ] Reward issuance tested end-to-end
  [ ] Analytics events instrumented (invite_sent, invite_clicked, invite_installed, invite_qualified, reward_issued)
  [ ] Fraud caps configured
  [ ] Support runbook for disputes

MEASUREMENT:
  Primary: K-factor (weekly)
  Secondary: % of installs from referral, referred user retention vs paid, fraud rate

Tooling

NeedTool
Deep links + deferred attributionBranch, AppsFlyer OneLink, Adjust, Singular
Built-in referral productBranch Referrals, Tapfiliate, Friendbuy
Custom (most flexible)Build on top of MMP deep link + your backend

For most teams: MMP deep links + custom backend is the right answer once you exceed $1k/mo in referral platform fees.

Common Mistakes

  • Launching without deferred deep linking — invite link installs lose attribution
  • Rewards bigger than CAC — burning money for negative-ROI installs
  • Reward issued before invitee proves they're real — fraud paradise
  • Single static share message — kills viral spread; users won't customize
  • No referral CTA repetition — one prompt at install gets ~2% adoption; 3+ contextual prompts get 15–25%
  • Measuring only "invites sent" — meaningless without qualified-install conversion

Cross-Skill Handoffs

  • Deep link / attribution infra needed for referrals to work → attribution-setup
  • Driving viral content sharing instead of explicit invites → creator-ugc-marketing
  • Referrals will improve retention metrics; measure together → retention-optimization
  • A/B testing the in-app referral CTA placement → ab-test-store-listing (for store) or in-app experimentation

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.