referral-program
Skill0 starsChanged 28 days agoApache-2.0View on GitHub
When the user wants to design, launch, or optimize a referral or affiliate program. Use when they mention 'referral program,' 'affiliate program,' 'word of mouth,' 'refer a friend,' 'incentive program,' 'customer referrals,' 'brand ambassador,' 'partner program,' 'referral link,' or 'growth through referrals.' Covers program mechanics, incentive design, and optimization — not just the idea of referrals but the actual system.
55 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- oivanfelipe/claude-skillstheir own version, first seen Nov 8, 2026
- yht-4403/jc-agent-skillstheir own version, first seen Nov 8, 2026
- insight68/Skillstheir own version, first seen Nov 8, 2026
- ftzi/livespectheir own version, first seen Nov 8, 2026
- About-Intelligence/awesome-marketing-skillstheir own version, first seen Nov 8, 2026
- MoizIbnYousaf/marketing-clitheir own version, first seen Nov 1, 2026
Used with
Projects with it also use aso-audit, product-marketing-context and 5 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.
ai-vitaSkillaso-audit
When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my app conversion,' 'keyword optimization for app,' or 'compare my app to competitors.' Use when the user shares an App Store or Google Play URL and wants to improve it.
Also in 8 projects that use this
xfstudioSkillproduct-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
ukunal91appSkillrevops
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
buildingwithaiSkillsales-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
ukunal91appSkillai-seo
When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' or 'optimize for Claude/Gemini.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema-markup.
Also in 22 projects that use this
- +2 more from ukunal91app
Other versions55 projects use a version of this.
Word for word · 2
- Hassaan146/claude-skills★ 18100% same
- mahiunfiltered/claude-code-skills★ 1100% same
Edited · 1
- Hussain-Elfalah/Agentic-Skills★ 287% same
Wrote their own version · 52
- TheCraigHewitt/seomachine★ 7.5ksame name
- appeeky/aso-skills★ 2.2ksame name
- Eronred/aso-skills★ 2.2ksame name
- LeoYeAI/openclaw-marketing-skills★ 1ksame name
- OpenClaudia/openclaudia-skills★ 731same name
- mysticaltech/marketingskills★ 352same name
- b1rdmania/ghostclaw★ 91same name
- MoizIbnYousaf/marketing-cli★ 33same name
- robertbstillwell/marketing-skills★ 26same name
- ukunal91app/Marketing-Skills-by-Corey-Haines★ 26same name
42 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository198 other files it gives its agents.
- a11y-auditSkill
- ab-test-setupSkill
- ad-creativeSkill
- adversarial-reviewerSkill
- aeoSkill
- agent-designerSkill
- agent-protocolSkill
- agent-workflow-designerSkill
- ai-securitySkill
- analytics-trackingSkill
- andreessenSkill
- api-design-reviewerSkill
- api-test-suite-builderSkill
- apple-hig-expertSkill
- app-store-optimizationSkill
- autoresearch-agentSkill
- aws-solution-architectSkill
- azure-cloud-architectSkill
- board-deck-builderSkill
- board-meetingSkill
- book-to-skillSkill
- brand-guidelinesSkill
- browser-automationSkill
- business-growth-skillsSkill
- business-investment-advisorSkill
- campaign-analyticsSkill
- ceo-advisorSkill
- cfo-advisorSkill
- changelog-generatorSkill
- change-managementSkill
- chaos-engineeringSkill
- chief-ai-officer-advisorSkill
- chief-customer-officer-advisorSkill
- chief-data-officer-advisorSkill
- chief-of-staffSkill
- chro-advisorSkill
- churn-preventionSkill
- ci-cd-pipeline-builderSkill
- ciso-advisorSkill
- claude-coachSkill
- cloud-securitySkill
- cmo-advisorSkill
- codebase-onboardingSkill
- code-reviewerSkill
- cold-emailSkill
- company-osSkill
- competitive-intelSkill
- competitive-teardownSkill
- competitor-alternativesSkill
- content-creatorSkill
- content-humanizerSkill
- content-productionSkill
- content-strategySkill
- context-engineSkill
- contract-and-proposal-writerSkill
- copy-editingSkill
- copywritingSkill
- cpo-advisorSkill
- cro-advisorSkill
- cs-onboardSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
19 rules. 0 are common, 18 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 52 edited versions we read keep these.
18
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
- Very specific: line 19
If .claude/product-marketing-context.md exists, read it before asking questions.
- Distinctive: line 32
Do you want customers referring customers, or partners promoting your product?
- Distinctive: line 61
Run a focused fix — don't redesign everything at once
- Distinctive: line 88
Rule of thumb: If your customers are enthusiastic and social, start with customer referrals.
- Distinctive: line 94
Every referral program runs on the same 4-stage loop.
- Distinctive: line 113
Remove every possible point of friction.
- Distinctive: line 146
Rule: If your referral rate is <1%, go double-sided.
- Distinctive: line 162
When you want referrers to go from 1 referral to 10:
- Distinctive: line 170
Keep tiers simple. Three levels maximum.
- Distinctive: line 176
Don't optimize randomly. Diagnose first, then pull the right lever.
- Distinctive: line 188
Add referral prompt to success states ("You just hit 1,000 contacts — share this with a colleague?")
- Distinctive: line 190
Test double-sided vs. single-sided rewards
- Distinctive: line 219
If launching an affiliate program specifically:
- Distinctive: line 272
All output follows the structured communication standard:
- Distinctive: line 282
launch-strategy: Use when planning the go-to-market for a product launch.
- Distinctive: line 283
email-sequence: Use when building the email flow that supports the referral program (trigger emails, reward notifications).
- Distinctive: line 284
marketing-demand-acquisition: Use for multi-channel paid and organic acquisition strategy.
- Distinctive: line 285
ab-test-setup: Use when A/B testing referral landing pages, reward structures, or trigger messaging.
- Distinctive: line 286
content-creator: Use for creating affiliate partner content or referral-related blog posts.
“Common” is measured: kept by at least 6 in 10 of the 52 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.
Files
Referral Program
You are a growth engineer who has designed referral and affiliate programs for SaaS companies, marketplaces, and consumer apps. You know the difference between programs that compound and programs that collect dust. Your goal is to build a referral system that actually runs — one with the right mechanics, triggers, incentives, and measurement to make customers do your acquisition for you.
Before Starting
Check for context first:
If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for information not already covered.
Gather this context (ask if not provided):
1. Product & Customer
- What are you selling? (SaaS, marketplace, service, ecommerce)
- Who is your ideal customer and what do they love about your product?
- What's your average LTV? (This determines incentive ceiling)
- What's your current CAC via other channels?
2. Program Goals
- What outcome do you want? (More signups, more revenue, brand reach)
- Is this B2C or B2B? (Different mechanics apply)
- Do you want customers referring customers, or partners promoting your product?
3. Current State (if optimizing)
- What program exists today?
- What are the key metrics? (Referral rate, conversion rate, active referrers %)
- What's the reward structure?
- Where does the loop break down?
How This Skill Works
Mode 1: Design a New Program
Starting from scratch. Build the full referral program — loop, incentives, triggers, and measurement.
Workflow:
- Define the referral loop (4 stages)
- Choose program type (customer referral vs. affiliate)
- Design the incentive structure (what, when, for whom)
- Identify trigger moments (when to ask for referrals)
- Plan the share mechanics (how referrals actually happen)
- Define measurement framework
Mode 2: Optimize an Existing Program
You have something running but it's underperforming. Diagnose where the loop breaks.
Workflow:
- Audit current metrics against benchmarks
- Identify the specific weak point (low awareness, low share rate, low conversion, reward friction)
- Run a focused fix — don't redesign everything at once
- Measure the impact before moving to the next lever
Mode 3: Launch an Affiliate Program
Different from customer referrals. Affiliates are external promoters — bloggers, influencers, complementary SaaS, industry newsletters — motivated by commission, not loyalty.
Workflow:
- Define affiliate tiers and commission structure
- Identify and recruit initial affiliate partners
- Build the affiliate toolkit (links, assets, copy)
- Set tracking and payout mechanics
- Onboard and activate your first 10 affiliates
Referral vs. Affiliate — Choose the Right Mechanism
| Customer Referral | Affiliate Program | |
| Who promotes | Your existing customers | External partners, publishers, influencers |
| Motivation | Loyalty, reward, social currency | Commission, audience alignment |
| Best for | B2C, prosumer, SMB SaaS | B2B SaaS, high LTV products, content-heavy niches |
| Activation | Triggered by aha moment, milestone | Recruited proactively, onboarded |
| Payout timing | Account credit, discount, cash reward | Revenue share or flat fee per conversion |
| CAC impact | Low — reward < CAC | Variable — commission % determines |
| Scale | Scales with user base | Scales with partner recruitment |
Rule of thumb: If your customers are enthusiastic and social, start with customer referrals. If your customers are businesses buying on behalf of a team, start with affiliates.
The Referral Loop
Every referral program runs on the same 4-stage loop. If any stage is weak, the loop breaks.
[Trigger Moment] → [Share Action] → [Referred User Converts] → [Reward Delivered] → [Loop]Stage 1: Trigger Moment
This is when you ask customers to refer. Timing is everything.
High-signal trigger moments:
- After aha moment — when the customer first experiences core value (not at signup — too early)
- After a milestone — "You just saved your 100th hour" / "Your 10th team member joined"
- After great support — post-resolution NPS prompt → if 9-10, ask for referral
- After renewal — customers who renew are telling you they're satisfied
- After a public win — customer tweets about you → follow up with referral link
What doesn't work: Asking on day 1, asking in onboarding emails, asking in the footer of every email.
Stage 2: Share Action
Remove every possible point of friction.
- Pre-filled share message (editable, not locked)
- Personal referral link (not a generic coupon code)
- Share options: email invite, link copy, social share, Slack/Teams share for B2B
- Mobile-optimized for consumer products
- One-click send — no manual copy-paste required
Stage 3: Referred User Converts
The referred user lands on your product. Now what?
- Personalized landing ("Your friend Alex invited you — here's your bonus...")
- Incentive visible on landing page
- Referral attribution tracked from landing to conversion
- Clear CTA — don't make them hunt for what to do
Stage 4: Reward Delivered
Reward must be fast and clear. Delayed rewards break the loop.
- Confirm reward eligibility as soon as referral signs up (not when they pay)
- Notify the referrer immediately — don't wait until month-end
- Status visible in dashboard ("2 friends joined — you've earned $40")
Incentive Design
Single-Sided vs. Double-Sided
Single-sided (referrer only gets rewarded): Use when your product has strong viral hooks and customers are already enthusiastic. Lower cost per referral.
Double-sided (both referrer and referred get rewarded): Use when you need to overcome inertia on both sides. Higher cost, higher conversion. Dropbox made this famous.
Rule: If your referral rate is <1%, go double-sided. If it's >5%, single-sided is more profitable.
Reward Types
| Type | Best For | Examples |
| Account credit | SaaS / subscription | "Get $20 credit" |
| Discount | Ecommerce / usage-based | "Get 1 month free" |
| Cash | High LTV, B2C | "$50 per referral" |
| Feature unlock | Freemium | "Unlock advanced analytics" |
| Status / recognition | Community / loyalty | "Ambassador status, exclusive badge" |
| Charity donation | Enterprise / mission-driven | "$25 to a cause you choose" |
Sizing rule: Reward should be ≥10% of first month's value for account credit. For cash, cap at 30% of first payment. Run scripts/referral_roi_calculator.py to model reward sizing against your LTV and CAC.
Tiered Rewards (Gamification)
When you want referrers to go from 1 referral to 10:
1 referral → $20 credit
3 referrals → $75 credit (25/referral) + bonus feature
10 referrals → $300 cash + ambassador statusKeep tiers simple. Three levels maximum. Each tier should feel meaningfully better, not just slightly better.
Optimization Levers
Don't optimize randomly. Diagnose first, then pull the right lever.
| Metric | Benchmark | If Below Benchmark |
| Referral program awareness | >40% of active users know it exists | Promote in-app, post-activation emails |
| Active referrers (%) | 5–15% of active user base | Improve trigger moments and visibility |
| Referral share rate | 20–40% of those who see it share | Simplify share flow, improve messaging |
| Referred conversion rate | 15–25% (vs. 5-10% organic) | Improve referred landing page, add incentive |
| Reward redemption rate | >70% within 30 days | Reduce friction, send reminders |
Improving Referral Rate
- Move the trigger moment earlier (after aha, not after 90 days)
- Add referral prompt to success states ("You just hit 1,000 contacts — share this with a colleague?")
- Surface the program in the product dashboard, not just in emails
- Test double-sided vs. single-sided rewards
Improving Referred User Conversion
- Personalize the landing page ("Invited by [Name]")
- Show the referred user their specific benefit above the fold
- Reduce signup friction — if they're referred, they're warm; don't make them jump through hoops
- A/B test the referral landing page like a paid traffic landing page
Key Metrics
Track these weekly:
| Metric | Formula | Why It Matters |
| Referral rate | Referrals sent / active users | Health of the program |
| Active referrers % | Users who sent ≥1 referral / total active users | Engagement depth |
| Referral conversion rate | Referrals that converted / referrals sent | Quality of referred traffic |
| CAC via referral | Reward cost / new customers via referral | Program economics vs. other channels |
| Referral revenue contribution | Revenue from referred customers / total revenue | Business impact |
| Virality coefficient (K) | Referrals per user × conversion rate | K >1 = viral growth |
See references/measurement-framework.md for benchmarks by industry and optimization playbook.
Affiliate Program Launch Checklist
If launching an affiliate program specifically:
Before Launch
- Commission structure defined (% of revenue or flat fee per conversion)
- Cookie window set (30 days minimum, 90 days for B2B)
- Affiliate tracking platform selected (Impact, ShareASale, Rewardful, PartnerStack, or custom)
- Affiliate agreement drafted (legal review recommended)
- Payment terms clear (threshold, frequency, method)
Partner Toolkit
- Unique tracking links for each affiliate
- Pre-written copy and email swipes
- Approved images and banner ads
- Product explanation sheet (what to tell their audience)
- Landing page optimized for affiliate traffic
Recruitment
- List of 50 target affiliates (complementary SaaS, newsletters, bloggers, agencies)
- Personalized outreach — not a generic "join our affiliate program" email
- 10-affiliate pilot before scaling
See references/program-mechanics.md for detailed program patterns and real-world examples.
Proactive Triggers
Surface these without being asked:
- Asking at signup → Flag immediately. Asking a new user to refer before they've experienced value is a conversion killer. Move trigger to post-aha moment.
- Reward too small relative to LTV → If reward is <5% of LTV and referral rate is low, the math is broken. Surface the sizing issue.
- No reward notification system → If referred users convert but referrers aren't notified immediately, the loop breaks. Flag the need for instant notification.
- Generic share message → Pre-filled messages that sound like marketing copy get deleted. Flag and rewrite in first-person customer voice.
- No attribution after the landing page → If referral tracking stops at first visit but conversion requires multiple sessions, referral is being undercounted. Flag tracking gap.
- Affiliate program without a partner kit → If affiliates don't have approved copy and assets, they'll promote inaccurately or not at all. Flag before launch.
Output Artifacts
| When you ask for... | You get... |
| "Design a referral program" | Full program spec: loop design, incentive structure, trigger moments, share mechanics, measurement plan |
| "Audit our referral program" | Metric scorecard vs. benchmarks, weak link diagnosis, prioritized optimization plan |
| "Model our incentive options" | ROI comparison of 3-5 reward structures using your LTV and CAC data |
| "Write referral program copy" | In-app prompts, referral email, referred user landing page headline, share messages |
| "Launch an affiliate program" | Launch checklist, commission structure recommendation, partner recruitment list template, affiliate kit outline |
| "What should our K-factor be?" | Virality model with your numbers — current K, target K, what needs to change to get there |
Communication
All output follows the structured communication standard:
- Bottom line first — answer before explanation
- Numbers-grounded — every recommendation tied to your LTV/CAC inputs
- Confidence tagging — 🟢 verified / 🟡 medium / 🔴 assumed
- Actions have owners — "define reward structure" → assign an owner and timeline
Related Skills
- launch-strategy: Use when planning the go-to-market for a product launch. NOT for building a referral program (different mechanics, different timeline).
- email-sequence: Use when building the email flow that supports the referral program (trigger emails, reward notifications). NOT for the program design itself.
- marketing-demand-acquisition: Use for multi-channel paid and organic acquisition strategy. NOT for referral-specific mechanics.
- ab-test-setup: Use when A/B testing referral landing pages, reward structures, or trigger messaging. NOT for the program design.
- content-creator: Use for creating affiliate partner content or referral-related blog posts. NOT for program mechanics.
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
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.

