Skip to content
FunCoding

Search

Search docs, Skills and MCP

referral-program

Referral and affiliate program design covering referral loop architecture, incentive design, trigger moment optimization, viral coefficient modeling, affiliate program structure, and optimization playbook.

文档与办公883business-growth/referral-program/SKILL.md

Install

Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.

读取 https://funcoding.ai/skills/borghei/claude-skills/referral-program/install.md ,按里面的步骤帮我安装这个 Skill。

SKILL.md

Referral Program

Production-grade referral and affiliate program framework covering the 4-stage referral loop, incentive design methodology, trigger moment optimization, share mechanics, viral coefficient modeling, affiliate program architecture, and systematic optimization playbook. Designed to build programs that compound, not collect dust.

Core Capabilities

  • Program type & loop design — referral vs affiliate decision, plus the 4-stage loop (trigger → share → convert → reward)
  • Incentive design — single- vs double-sided, reward types, tiered gamification, reward economics against LTV/CAC
  • Trigger & share mechanics — in-product and email trigger points, share channel priority, first-person share copy
  • Referred-user experience — referral landing page, attribution rules, program copy set (prompts, emails, dashboards)
  • Growth math — K-factor modeling, revenue impact models, and lever-by-lever K improvement
  • Affiliate framework — commission models, tier systems, partner toolkit, recruitment
  • Optimization — diagnose-before-optimize playbook, metric benchmarks, troubleshooting, and three Python tools

When to Use

  • The user asks to "design a referral program", "launch an affiliate program", or "improve viral growth"
  • The decision between customer referral vs affiliate program needs to be made
  • An existing referral program has stalled (K-factor <1, low share rate, low referred-user conversion)
  • Reward structure needs sizing against CAC, margin, or LTV
  • Trigger moments need to be identified (when to ask, which in-product events, which lifecycle emails)
  • The user says "word-of-mouth isn't working" or "we want to add a refer-a-friend flow"

Clarify First

Before designing the referral program, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • Program type — customer referral vs affiliate (enthusiastic/social customers vs team buyers) (selects the entire framework)
  • Trigger moment — the in-product or lifecycle point where you ask (a broken Stage 1 can't be fixed by a bigger reward at Stage 4)
  • Reward economics — first-payment value, margin, and CAC (caps the reward at <30% of first payment)
  • Current referral rate (if any) — decides single- vs double-sided incentive and which stage to fix first

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the deliverable.

Quick Start

  1. Pick the program type — use the Referral vs Affiliate Decision table (enthusiastic/social customers → referral; team buyers → affiliate).
  2. Build the loop in order — trigger → share → convert → reward; a broken Stage 1 can't be fixed by a bigger reward at Stage 4.
  3. Size the incentive — cap reward at <30% of first payment; go double-sided if referral rate <1%.
  4. Model and validate — run the scripts (referral_economics_calculator.py, referral_funnel_analyzer.py, affiliate_commission_modeler.py) to size rewards, find the weakest stage, and model affiliate tiers.
  5. Optimize by priority — fix awareness first, then share flow, then referred experience, then the incentive.

References

Load the reference that matches the task — keep this file lean and pull detail on demand:

  • references/loop-and-incentives.md — Referral vs Affiliate decision table, the full 4-stage loop with per-stage tables, incentive design (single/double-sided, reward types, tiers, economics), and trigger moment architecture. Read when designing the core program.
  • references/share-and-experience.md — share channel priority, share message templates, referral landing page layout, attribution rules, and the program copy set (in-app prompt, dashboard, post-activation email). Read when building the sharing flow and referred-user experience.
  • references/modeling-and-affiliate.md — K-factor calculation and improvement levers, plus the full affiliate framework (commission structure, tier system, toolkit, recruitment). Read when modeling growth math or designing an affiliate program.
  • references/optimization-and-operations.md — optimization playbook, key metrics and benchmarks, revenue impact model, output artifacts, full tool reference, troubleshooting table, success criteria, and anti-patterns. Read when diagnosing a stalled program or operating the scripts.

Scope & Limitations

In scope: Customer referral program design (4-stage loop), incentive structure (single-sided, double-sided, tiered), trigger moment architecture, share mechanics, referral landing page specifications, viral coefficient modeling, affiliate program framework (commission models, tier systems, recruitment), and systematic optimization playbook.

Out of scope: Referral landing page visual design and CRO (use page-cro), signup flow optimization for referred users (use signup-flow-cro), post-signup onboarding for referred users (use onboarding-cro), churn prevention for referred customers (use churn-prevention), and reward pricing alignment (use pricing-strategy). Scripts operate on local data only -- no integrations with referral platforms (ReferralHero, Viral Loops, PartnerStack, etc.).

Limitations: K-factor benchmarks assume consumer or prosumer SaaS; B2B enterprise referral programs have different dynamics (lower K but higher per-referral value). Affiliate commission benchmarks (20-30% recurring) are SaaS-specific; marketplace and e-commerce commissions follow different models. Attribution windows (30-90 day cookies) face increasing limitations from browser privacy features (Safari ITP, Chrome third-party cookie deprecation). Revenue projections are estimates based on provided conversion rates.

Integration Points

  • pricing-strategy -- Referral reward sizing must align with pricing margins and LTV; reward should be <30% of first payment
  • signup-flow-cro -- Referred user signup flow should pre-fill email, show referrer context, and minimize friction
  • onboarding-cro -- Referred users may need different onboarding path (they arrive with context from the referrer)
  • churn-prevention -- Monitor referred customer retention separately; high referral churn wastes acquisition spend
  • page-cro -- Referral landing page conversion optimization follows page-cro methodology
  • popup-cro -- Post-purchase or post-milestone popups are natural referral trigger points

Similar Skills

pdf
anthropics/skills180k

pdf

Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.

Docs & office

discernment-nudge
anthropics/skills180k

discernment-nudge

After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.

Docs & office

doc-coauthoring
anthropics/skills180k

doc-coauthoring

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

Docs & office

docx
anthropics/skills180k

docx

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

Docs & office

pptx
anthropics/skills180k

pptx

Use this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.

Docs & office

canvas-design
anthropics/skills180k

canvas-design

Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.

Docs & office