Source profileQuality 81/100

MoizIbnYousaf/marketing-cli/skills/referral-program/SKILL.md

referral-program

Designs viral referral programs with incentive structures, sharing mechanics, and tracking. Covers one-sided, two-sided, tiered, and milestone models with viral coefficient calculations. Use when someone wants word-of-mouth growth, viral loops, invite programs, or says 'referral', 'viral loop', 'word of mouth', 'invite program', 'refer a friend', 'growth loop', 'referral incentive', 'affiliate program', 'ambassador program', 'get users to invite friends', or 'organic growth'. Even casual mention

Source repository stars
27
Declared platforms
0
Static risk flags
0
Last source update
2026-07-28
Source checked
2026-07-28

Decision brief

What it does—and where it fits

Designs viral referral programs with incentive structures, sharing mechanics, and tracking. Covers one-sided, two-sided, tiered, and milestone models with viral coefficient calculations.

Best for

  • Design a referral program that turns existing users into an acquisition channel. Define the incentive model, sharing mechanics, copy, and launch plan. Focus on programs that actually get used — not "refer a friend" link…

Not for

  • Referral link buried in settings — if users can't find it, they won't share. It needs to be visible in the main dashboard, not hidden three clicks deep.
  • Requiring both parties to be paid users before reward triggers — this kills conversion because the referee has no incentive to sign up, and the referrer waits forever for credit.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/MoizIbnYousaf/marketing-cli --skill "skills/referral-program"
Safe inspection promptEditorial

Inspect the Agent Skill "referral-program" from https://github.com/MoizIbnYousaf/marketing-cli/blob/f12fbcbe4929584697b309b9096c9427b0cfce8e/skills/referral-program/SKILL.md at commit f12fbcbe4929584697b309b9096c9427b0cfce8e. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Workflow

    Evaluate and recommend the right model:

    Best for: High-value products, enterprise, low-frequency purchasesPros: Simple, lower cost per referralCons: Less motivation for referee to convert
  2. 02

    Step 1: Choose Referral Model

    Evaluate and recommend the right model:

    Best for: High-value products, enterprise, low-frequency purchasesPros: Simple, lower cost per referralCons: Less motivation for referee to convert
  3. 03

    Step 2: Define the Incentive

    Referrer reward should be 10-25% of first-year LTV

    Referrer reward should be 10-25% of first-year LTVReferee reward should lower the barrier to first purchaseTwo-sided: referee reward can be smaller than referrer reward
  4. 04

    Step 3: Design Sharing Mechanics

    Unique referral link (required, baseline) - Personal URL: product.com/ref/[username] or product.com/r/[code] - One-click copy button - Auto-populated share text

    Personal URL: product.com/ref/[username] or product.com/r/[code]One-click copy buttonAuto-populated share text
  5. 05

    Step 4: Write Referral Copy

    Post-achievement trigger:

    Post-achievement trigger:

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score81/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars27SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
MoizIbnYousaf/marketing-cli
Skill path
skills/referral-program/SKILL.md
Commit
f12fbcbe4929584697b309b9096c9427b0cfce8e
License
MIT
Collected
2026-07-28
Default branch
main
View the original SKILL.md

Referral Program Design

Purpose

Design a referral program that turns existing users into an acquisition channel. Define the incentive model, sharing mechanics, copy, and launch plan. Focus on programs that actually get used — not "refer a friend" links that collect dust.

Reads

  • brand/audience.md — Personas, what they value, their networks
  • brand/positioning.md — Value props, pricing context for incentive sizing
  • brand/voice-profile.md — Brand voice for all referral copy

Brand Integration

  • audience.md — Incentive type depends on audience. B2B audiences prefer account credits. B2C audiences prefer discounts or free months. Developer audiences prefer swag or extended trials.
  • positioning.md — Referral messaging reinforces the brand's positioning angle, not generic 'share with a friend' copy. If positioning is around simplicity, the referral CTA is 'Know someone drowning in complexity?'
  • voice-profile.md — All referral copy (dashboard prompts, share text, emails) should match the brand voice. A casual brand writes "Your friend's gonna love this" while a professional brand writes "Share a professional recommendation."

Workflow

Step 1: Choose Referral Model

Evaluate and recommend the right model:

One-Sided (Referrer only gets reward)

  • Best for: High-value products, enterprise, low-frequency purchases
  • Pros: Simple, lower cost per referral
  • Cons: Less motivation for referee to convert
  • Example: "Give your friend our link, you get $50 credit"

Two-Sided (Both get reward)

  • Best for: SaaS, marketplaces, subscription products
  • Pros: Higher conversion (referee has incentive), feels fair
  • Cons: Higher cost per referral
  • Example: "Give $20, get $20"

Tiered (Rewards increase with referral count)

  • Best for: Products with power users, community-driven products
  • Pros: Creates referral champions, gamification
  • Cons: Complex to communicate, top-heavy rewards
  • Example: "1 referral = 1 month free. 5 = premium forever."

Milestone (Unlock rewards at specific counts)

  • Best for: Products wanting viral moments
  • Pros: Creates sharing bursts, clear goals
  • Cons: Can feel like a grind
  • Example: "3 friends = swag. 10 friends = lifetime access."

Selection criteria:

  • Product price point and margins
  • Customer lifetime value (can you afford the incentive?)
  • Network effects (does the product get better with more users?)
  • Purchase frequency (one-time vs recurring)

Step 2: Define the Incentive

Incentive Types

TypeBest WhenExample
Account creditRecurring subscription"$20 off next month"
Extended trialFreemium model"+7 days of Pro"
Feature unlockGated features exist"Unlock advanced analytics"
Cash/gift cardHigh LTV, B2B"$50 Amazon card"
DiscountE-commerce, one-time"25% off next purchase"
DonationMission-driven brand"$10 to charity of choice"
Exclusive accessWaitlist/beta"Skip the waitlist"
Physical swagCommunity brand"Free branded merch"

Incentive Sizing Rules

  • Referrer reward should be 10-25% of first-year LTV
  • Referee reward should lower the barrier to first purchase
  • Two-sided: referee reward can be smaller than referrer reward
  • Always test: the "right" incentive is discovered, not guessed
  • Stack with existing promotions cautiously — don't train discount hunters

Step 3: Design Sharing Mechanics

Sharing Methods (Offer All, Optimize for Top 2)

Unique referral link (required, baseline)

  • Personal URL: product.com/ref/[username] or product.com/r/[code]
  • One-click copy button
  • Auto-populated share text

Referral code (supplement to link)

  • Short, memorable: 4-6 characters
  • Personalizable: user's name or custom code
  • Easy to share verbally

Email invite (high-intent channel)

  • Import contacts option (Google, Outlook)
  • Or manual email entry
  • Pre-written message, editable by user

Social sharing (volume channel)

  • Twitter/X: Pre-populated tweet with link
  • LinkedIn: Professional framing for B2B
  • WhatsApp/SMS: Direct message with link
  • Platform-native share sheet on mobile

In-product prompts (highest conversion trigger)

  • Post-success moment: "You just [achievement]! Share with a friend?"
  • Milestone celebration: "You've been using [Product] for 30 days!"
  • Team detection: "Looks like [colleague] could use this too"

Friction Reduction Checklist

  • One-click sharing (no extra steps)
  • Pre-written share text (editable)
  • Referral link visible in dashboard at all times
  • Mobile-optimized sharing flow
  • No login required for referee to see the offer
  • Referee landing page explains the incentive immediately

Step 4: Write Referral Copy

Referrer-Facing Copy

Dashboard prompt:

Give [incentive], Get [incentive]

Share [Product] with friends and you both get rewarded.
You've earned [X] so far from [Y] referrals.

[Copy Your Link]  [Invite by Email]

Post-achievement trigger:

Nice — you just [achievement]!

Know someone who'd love this too?
Share your link and you both get [incentive].

[Share Now]  [Maybe Later]

Email nudge:

Subject: You have $[X] in referral rewards waiting

You've been using [Product] for [X] weeks and
[specific achievement]. Know someone who'd benefit?

Share your personal link and you both get [incentive]:
[referral link]

[Share via Email]  [Copy Link]

Referee-Facing Copy

Referral landing page:

[Referrer name] invited you to [Product]

[Referrer] thinks you'd love [Product] — and they're
giving you [incentive] to try it.

[What Product Does — one sentence]

[Claim Your [Incentive]]

[Social proof: X users, rating, testimonial]

Referee welcome email:

Subject: [Referrer] gifted you [incentive] for [Product]

Welcome! [Referrer name] shared [Product] with you
and you've got [incentive] waiting.

Here's how to get started:
1. [Quick start step]
2. [Quick start step]
3. [Quick start step]

[Get Started with [Incentive]]

Step 5: Plan Launch Strategy

Pre-Launch (1 week before)

  • Seed with top 10% most active users first
  • Personal email from founder: "You're getting early access to our referral program"
  • Goal: Get first 50 referrals to validate mechanics

Launch (Week 1)

  • In-app announcement banner for all users
  • Email blast to full user base
  • Social media announcement
  • Add referral link to user dashboard permanently

Sustained Growth (Ongoing)

  • Trigger-based prompts (post-achievement, milestone, NPS 9-10)
  • Monthly referral leaderboard (optional, for tiered/milestone)
  • Seasonal boost: "Double rewards this month"
  • New user onboarding: mention referral program during setup

Viral Coefficient Calculation

Viral Coefficient (K) = i x c

i = invitations sent per user
c = conversion rate of invitations

K > 1 = viral growth (each user brings >1 new user)
K = 0.5 = healthy referral supplement
K < 0.2 = program needs work

Example:
- Average user sends 5 invites
- 15% of invites convert
- K = 5 x 0.15 = 0.75 (strong, not viral)

To improve K:
- Increase i: More sharing triggers, easier sharing mechanics
- Increase c: Better referee landing page, stronger incentive

Referral Program Metrics

MetricFormulaHealthy Range
Participation rateUsers who shared / Total users10-25%
Shares per userTotal shares / Participating users3-8
Invite conversion rateSignups / Total shares10-25%
Referral revenue %Referred revenue / Total revenue15-35%
Time to first referralAvg days from signup to first share<30 days
Viral coefficientInvites x Conversion rate>0.3
Referral CACProgram cost / Referred customers<Paid CAC

Anti-Patterns

  • Referral link buried in settings — if users can't find it, they won't share. It needs to be visible in the main dashboard, not hidden three clicks deep.
  • Requiring both parties to be paid users before reward triggers — this kills conversion because the referee has no incentive to sign up, and the referrer waits forever for credit.
  • Complex reward rules nobody understands — if the incentive takes more than one sentence to explain, participation drops. Simplicity drives sharing.
  • Rewards that expire too quickly (<30 days) — referrers who discover the program after a few weeks feel cheated. Give at least 90 days.
  • No tracking dashboard for referrers — without visibility into "how many people clicked, how many signed up," referrers lose motivation to keep sharing.
  • Generic share text that sounds corporate — "Check out this tool" gets ignored. Pre-written text should sound like something a real person would say.
  • Making the referee create an account before seeing the product — the referee should see the value (and their incentive) before being asked to commit.

Edge Cases

  • B2B enterprise: End-users often aren't the buyers. Referral must target decision-makers. Consider "recommend to your network" framing instead of "invite a friend." Reward the referrer's company, not just the individual.
  • Marketplaces (two-sided): Design separate referral programs for each side (e.g., rider referral vs. driver referral). Each side needs different incentives and copy.
  • Pre-launch / no existing users: Use waitlist-style referrals (Morning Brew model). "Refer friends to move up the waitlist" or "Unlock early access by inviting 3 friends."
  • Low-price products: Cash incentives may exceed product value. Use product-based rewards (extra storage, extended trial, feature unlock) instead of money.

Launch Measurement Milestones

  • Week 2: Check participation rate (target: >5% of active users sharing) and shares per user (target: >2). If below, the prompt timing or incentive needs adjustment.
  • Month 1: Evaluate invite conversion rate (target: >10%) and K-factor (target: >0.3). If conversion is low, the referee landing page or incentive needs work.
  • Month 3: Full program review — referral CAC vs. paid CAC, referred customer LTV vs. average LTV, fraud rate. Decide whether to scale, adjust incentives, or restructure the model.

Output

Each referral program design produces:

  • Recommended model with justification
  • Incentive structure (type, size, trigger conditions)
  • Sharing mechanics spec (channels, copy, UX flow)
  • Referrer and referee copy for all touchpoints
  • Launch plan (pre-launch, launch, sustained)
  • Metrics dashboard spec
  • Viral coefficient projection

Quality Checks

  • Incentive is ROI-positive (reward < LTV margin)
  • Sharing flow is 2 clicks or fewer
  • Copy provided for both referrer and referee touchpoints
  • Anti-fraud measures defined (at minimum: email verification, delayed payout)
  • Referee landing page has clear incentive + product value + CTA
  • Referral link is visible in user dashboard, not buried in settings
  • Copy matches brand voice (if voice-profile.md exists)
  • Launch plan includes measurement milestones with specific targets

Alternatives

Compare before choosing

Computed 9827

MoizIbnYousaf/marketing-cli

higgsfield-generate

Use when the user wants to generate an image or video via Higgsfield AI. Covers 30+ models: Soul V2, Seedance 2.0, Kling 3.0, Veo 3.1, GPT Image 2, Nano Banana 2. Also covers Marketing Studio — branded ad video/image with avatars and products. Use whenever: "generate an image", "make a video", "animate this photo", "image-to-video", "img2vid", "edit this image with AI", "produce a clip", "create an ad", "make a UGC video", "marketing video", "brand video", "TV spot", "import product from URL", "

Computed 9438,313

wshobson/agents

brand-landingpage

Brand-first landing page designer — runs a brand-identity interview (colors, typography, shape language), then generates and iterates on a polished landing page via Stitch with deployment-ready HTML. Use when the user asks to create, design, or build a landing page, homepage, or marketing page and has no established visual direction. Skip when they have a design mockup, need a dashboard or app UI, are working at component level, building a multi-page app, or restyling with known design tokens —

Computed 9342,015

coreyhaines31/marketingskills

emails

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold out

Computed 92165

JasonColapietro/suede-creator-skills

suede-workflow-skills

Umbrella workflow for 67 public skills: Full Send, copy, design, code review, SEO, launch packaging, MCP QA, iOS and Android app shipping, and creator workflows. Loads the full public skill pack.