skills/referral-program/SKILL.md
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,' or 'affiliate payout.' Use this whenever someone wants existing users or partners to bring in new customers. For launch-specific virality, see launch-strategy.
npx skillsauth add MileniumTick/skills referral-programInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
Check for product marketing context first:
If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md 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):
Best for:
Characteristics:
Best for:
Characteristics:
Trigger Moment → Share Action → Convert Referred → Reward → (Loop)
High-intent moments:
Ranked by effectiveness:
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
For examples and incentive sizing: See references/program-examples.md
If few customers are referring:
If referrals aren't converting:
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
| Problem | Fix | |---------|-----| | Low awareness | Add prominent in-app prompts | | Low share rate | Simplify to one click | | Low conversion | Optimize referred user experience | | Fraud/abuse | Add verification, limits | | One-time referrers | Add tiered/gamified rewards |
Program health:
Business impact:
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]
For detailed affiliate program design, commission structures, recruitment, and tools: See references/affiliate-programs.md
For implementation, see the tools registry. Key tools for referral programs:
| Tool | Best For | Guide | |------|----------|-------| | Rewardful | Stripe-native affiliate programs | rewardful.md | | Tolt | SaaS affiliate programs | tolt.md | | Mention Me | Enterprise referral programs | mention-me.md | | Dub.co | Link tracking and attribution | dub-co.md | | Stripe | Payment processing (for commission tracking) | stripe.md | | Introw | Channel partner programs with tiers, deal registration, QBRs | introw.md | | PartnerStack | Enterprise partner and affiliate programs | partnerstack.md |
development
Writes, reviews, and debugs idiomatic Rust code with memory safety and zero-cost abstractions. Implements ownership patterns, manages lifetimes, designs trait hierarchies, builds async applications with tokio, and structures error handling with Result/Option. Use when building Rust applications, solving ownership or borrowing issues, designing trait-based APIs, implementing async/await concurrency, creating FFI bindings, or optimizing for performance and memory safety. Invoke for Rust, Cargo, ownership, borrowing, lifetimes, async Rust, tokio, zero-cost abstractions, memory safety, systems programming.
development
Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook. Use this skill when: (1) writing new Rust code or functions, (2) reviewing or refactoring existing Rust code, (3) deciding between borrowing vs cloning or ownership patterns, (4) implementing error handling with Result types, (5) optimizing Rust code for performance, (6) writing tests or documentation for Rust projects.
development
Master Rust async programming with Tokio, async traits, error handling, and concurrent patterns. Use when building async Rust applications, implementing concurrent systems, or debugging async code.
tools
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.