agentleFS
pixelswithblisspixelswithbliss/claude-skills/skills/referrals/SKILL.md

referrals

Skill0 starsChanged 23 days agoMITView on GitHub

When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of mouth,' 'viral loop,' 'refer a friend,' 'partner program,' 'referral incentive,' 'how to get referrals,' 'customers referring customers,' 'affiliate payout,' 'get more reviews,' 'G2 reviews,' 'review campaign,' or 'respond to a bad review.' Use this whenever someone wants existing users or partners to bring in new customers. For launch-specific virality, see launch.

24 other projects use a version of this, 19 of them edited.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

Used with

Projects with it also use remotion-best-practices, ui-ux-pro-max and 4 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.
  • VercelSkill

    remotion-best-practices

    Best practices for Remotion - Video creation in React

    Also in 4 projects that use this

  • StrayDragonSkill

    ui-ux-pro-max

    UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.

    Also in 6 projects that use this

  • VercelSkill

    emil-design-eng

    This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.

    Also in 3 projects that use this

  • JetBrainsSkill

    brand-guidelines

    Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

    Also in 3 projects that use this

  • MicrosoftSkill

    grill-with-docs

    Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

    Also in 3 projects that use this

  • GoogleSkill

    grill-me

    A relentless interview to sharpen a plan or design.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

11 rules. 7 are common, 3 are distinctive, and 1 is very specific to this project.

  • 7

    Common

    Most of the 20 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older …

    line 15
  2. Common:

    Do customers naturally talk about it?

    line 33
  3. Distinctive:

    Before building a reward-driven program, check whether virality can be built into the product — often cheaper and more durable than paid …

    line 43
  4. Distinctive:

    Place the product on the Viral Potential Spectrum:

    line 45
  5. Distinctive:

    If the product is on the natural end, consider product-embedded viral mechanisms (Powered By badges, exposure loops, social sharing, …

    line 49
  6. Common:

    After achieving a milestone

    line 97
  7. Common:

    After renewing or upgrading

    line 99
  8. Common:

    Ask at better moments

    line 131
  9. Common:

    Test different incentive types

    line 133
  10. Common:

    Ensure referrer's endorsement is visible

    line 139
  11. Common:

    After milestone: "You achieved [X]—know others who'd want this?"

    line 235

“Common” is measured: kept by at least 6 in 10 of the 20 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 & Affiliate Programs

You are an expert in viral growth and referral marketing. Your goal is to help design and optimize programs that turn customers into growth engines.

Before Starting

Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Gather this context (ask if not provided):

1. Program Type

  • Customer referral program, affiliate program, or both?
  • B2B or B2C?
  • What's the average customer LTV?
  • What's your current CAC from other channels?

2. Current State

  • Existing referral/affiliate program?
  • Current referral rate (% who refer)?
  • What incentives have you tried?

3. Product Fit

  • Is your product shareable?
  • Does it have network effects?
  • Do customers naturally talk about it?

4. Resources

  • Tools/platforms you use or consider?
  • Budget for referral incentives?

Should You Engineer Virality First?

Before building a reward-driven program, check whether virality can be built into the product — often cheaper and more durable than paid referrals. But don't force virality where it doesn't naturally fit.

Place the product on the Viral Potential Spectrum:

  • Natural (build for it): collaboration tools, communication tools, user-facing outputs — every use exposes the product to non-users.
  • Limited (don't force it): backend, competitive-advantage, internal-only, and infrastructure products. Invest in referral programs, content, and partnerships instead.

If the product is on the natural end, consider product-embedded viral mechanisms (Powered By badges, exposure loops, social sharing, embeds, watermarks) before or alongside a reward program.

For the spectrum diagnostic, the 7 viral mechanisms, value-presentation and timing best practices, and affiliate power-law mechanics: See references/viral-mechanisms.md


Referral vs. Affiliate

Customer Referral Programs

Best for:

  • Existing customers recommending to their network
  • Products with natural word-of-mouth
  • Lower-ticket or self-serve products

Characteristics:

  • Referrer is an existing customer
  • One-time or limited rewards
  • Higher trust, lower volume

Affiliate Programs

For partner recruitment/activation, cohort economics, executable terms, reconciliation, and measured incremental growth, load the operating playbook. This expands the existing affiliate branch instead of creating an overlapping skill.

Best for:

  • Reaching audiences you don't have access to
  • Content creators, influencers, bloggers
  • Higher-ticket products that justify commissions

Characteristics:

  • Affiliates may not be customers
  • Ongoing commission relationship
  • Higher volume, variable trust

Referral Program Design

The Referral Loop

Trigger Moment → Share Action → Convert Referred → Reward → (Loop)

Step 1: Identify Trigger Moments

High-intent moments:

  • Right after first "aha" moment
  • After achieving a milestone
  • After exceptional support
  • After renewing or upgrading

Step 2: Design Share Mechanism

Ranked by effectiveness:

  1. In-product sharing (highest conversion)
  2. Personalized link
  3. Email invitation
  4. Social sharing
  5. Referral code (works offline)

Step 3: Choose Incentive Structure

Single-sided rewards (referrer only): Simpler, works for high-value products

Double-sided rewards (both parties): Higher conversion, win-win framing

Tiered rewards: Gamifies referral process, increases engagement

Present the reward with the bigger-feeling number — "lead with the larger number" (say "$10 off," not "40% off," on a low-priced product). Reward at the aha moment or milestone, not signup. Reduce friction: one-click share, pre-written messages.

For examples and incentive sizing: See references/program-examples.md

For product-embedded virality, value-presentation rules, and affiliate power-law mechanics: See references/viral-mechanisms.md


Program Optimization

Improving Referral Rate

If few customers are referring:

  • Ask at better moments
  • Simplify sharing process
  • Test different incentive types
  • Make referral prominent in product

If referrals aren't converting:

  • Improve landing experience for referred users
  • Strengthen incentive for new users
  • Ensure referrer's endorsement is visible

A/B Tests to Run

Incentive tests: Amount, type, single vs. double-sided, timing

Messaging tests: Program description, CTA copy, landing page copy

Placement tests: Where and when the referral prompt appears

Common Problems & Fixes

ProblemFix
Low awarenessAdd prominent in-app prompts
Low share rateSimplify to one click
Low conversionOptimize referred user experience
Fraud/abuseAdd verification, limits
One-time referrersAdd tiered/gamified rewards

Measuring Success

Key Metrics

Program health:

  • Active referrers (referred someone in last 30 days)
  • Referral conversion rate
  • Rewards earned/paid

Business impact:

  • % of new customers from referrals
  • CAC via referral vs. other channels
  • LTV of referred customers
  • Referral program ROI

Typical Findings

  • Referred customers have 16-25% higher LTV
  • Referred customers have 18-37% lower churn
  • Referred customers refer others at 2-3x rate

Launch Checklist

Before Launch

  • Define program goals and success metrics
  • Design incentive structure
  • Build or configure referral tool
  • Create referral landing page
  • Set up tracking and attribution
  • Define fraud prevention rules
  • Create terms and conditions
  • Test complete referral flow

Launch

  • Announce to existing customers
  • Add in-app referral prompts
  • Update website with program details
  • Brief support team

Post-Launch (First 30 Days)

  • Review conversion funnel
  • Identify top referrers
  • Gather feedback
  • Fix friction points
  • Send reminder emails to non-referrers

Email Sequences

Referral Program Launch

Subject: You can now earn [reward] for sharing [Product]

We just launched our referral program!

Share [Product] with friends and earn [reward] for each signup.
They get [their reward] too.

[Unique referral link]

1. Share your link
2. Friend signs up
3. You both get [reward]

Referral Nurture Sequence

  • Day 7: Remind about referral program
  • Day 30: "Know anyone who'd benefit?"
  • Day 60: Success story + referral prompt
  • After milestone: "You achieved [X]—know others who'd want this?"

Affiliate Programs

For detailed affiliate program design, commission structures, recruitment, and tools: See references/affiliate-programs.md

For affiliate power-law mechanics (buyout clauses ~12× monthly commission, the 20/80 super-promoter rule, launch-affiliate tactics): See references/viral-mechanisms.md


Review Programs

Reviews are the other half of customer advocacy. For review-request programs, responding to reviews, reputation triage, and reusing testimonials with permission (G2, Capterra, Trustpilot, Google, app stores), see references/review-programs.md. Platform rules differ, so check references/review-platform-rules.md before proposing incentives or automation.

Task-Specific Questions

  1. What type of program (referral, affiliate, or both)?
  2. What's your customer LTV and current CAC?
  3. Existing program or starting from scratch?
  4. What tools/platforms are you considering?
  5. What's your budget for rewards/commissions?
  6. Is your product naturally shareable?

Tool Integrations

For implementation, see the tools registry. Key tools for referral programs:

ToolBest ForGuide
RewardfulStripe-native affiliate programsrewardful.md
ToltSaaS affiliate programstolt.md
Mention MeEnterprise referral programsmention-me.md
Dub.coLink tracking and attributiondub-co.md
StripePayment processing (for commission tracking)stripe.md
IntrowChannel partner programs with tiers, deal registration, QBRsintrow.md
PartnerStackEnterprise partner and affiliate programspartnerstack.md

Related Skills

  • launch: For launching referral program effectively
  • emails: For referral nurture campaigns
  • marketing-psychology: For understanding referral motivation
  • analytics: For tracking referral attribution

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.