agentleFS
SkeneTechnologiesSkeneTechnologies/plg-skills/skills/referral-program/SKILL.md

referral-program

Skill19 starsChanged 9 months agoMITView on GitHub

When the user wants to design a referral or affiliate program -- including reward structures, referral mechanics, two-sided incentives, or partner programs. Also use when the user says "refer a friend," "referral reward," "affiliate program," "ambassador program," or "referral ROI." For viral loop design, see viral-loops. For growth loops, see growth-loops.

We split this skill into the rules it gives an agent

15 rules. 0 are common, 12 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 49 edited versions we read keep these.

  • 12

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before designing or optimizing a referral program, answer these:

    line 14
  2. Distinctive:

    If you have access to the user's codebase, analyze it before asking diagnostic questions.

    line 29
  3. Very specific:

    Find referral/invite code: Search for *referral*, *invite*, *refer*, *share*, *ambassador* in components and routes

    line 31
  4. Distinctive:

    Check referral mechanics: Search for referral codes, invite links, referral URLs -- how are referrals tracked?

    line 32
  5. Very specific:

    Find reward logic: Search for reward, credit, bonus, referral_reward, referral_credit -- what do referrers/referees get?

    line 33
  6. Distinctive:

    Check invite flow: Search for invite modals, share buttons, email invite forms -- how do users invite others?

    line 34
  7. Very specific:

    Find referral tracking: Search for referral_source, referred_by, invite_code, ref= -- how are referrals attributed?

    line 35
  8. Distinctive:

    Check social sharing: Search for share buttons -- Twitter/X, LinkedIn, Facebook, copy-link, email share

    line 36
  9. Distinctive:

    Find referral dashboard: Search for referral status pages -- can users see how many people they've referred?

    line 37
  10. Distinctive:

    Check for viral content: Search for public profiles, shareable outputs, embeddable content that could drive organic referrals

    line 38
  11. Distinctive:

    Every referral program follows four steps: Trigger, Share, Incentive, Reward.

    line 90
  12. Distinctive:

    Referral prompt timing: When in the user journey to surface the referral ask

    line 362
  13. Distinctive:

    When designing a referral program, produce this specification:

    line 384
  14. Distinctive:

    Add in-product surfaces (dashboard widget, milestone prompts)

    line 456
  15. Distinctive:

    Test new share mechanisms

    line 465

“Common” is measured: kept by at least 6 in 10 of the 49 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 Program

You are a referral program designer. Design and optimize structured programs that reward users for bringing in new customers. A referral program formalizes word-of-mouth by adding incentives, tracking, and scalable mechanics to organic recommendation behavior.


1. Diagnostic Questions

Before designing or optimizing a referral program, answer these:

  1. Do your users already recommend your product organically? (Check NPS, social mentions, support tickets saying "my friend told me about you")
  2. What is your current NPS? (NPS > 40 is a strong foundation for referrals; NPS < 20 means fix the product first)
  3. What is your customer LTV and gross margin? (Determines max reward budget)
  4. What is your current CAC by channel? (Referral program should beat other channels on CAC)
  5. What percentage of users have a network that matches your ICP? (B2B: do users know people at other companies? B2C: do users know people with the same need?)
  6. Have you tried a referral program before? (Learn from past attempts)
  7. What is the natural sharing behavior in your product? (Team invites, content sharing, public profiles)
  8. What reward types would your users value? (Credits, cash, features, discounts)

Codebase Audit (Optional)

If you have access to the user's codebase, analyze it before asking diagnostic questions. Use findings to pre-fill answers and focus recommendations on what actually exists.

  1. Find referral/invite code: Search for *referral*, *invite*, *refer*, *share*, *ambassador* in components and routes
  2. Check referral mechanics: Search for referral codes, invite links, referral URLs -- how are referrals tracked?
  3. Find reward logic: Search for reward, credit, bonus, referral_reward, referral_credit -- what do referrers/referees get?
  4. Check invite flow: Search for invite modals, share buttons, email invite forms -- how do users invite others?
  5. Find referral tracking: Search for referral_source, referred_by, invite_code, ref= -- how are referrals attributed?
  6. Check social sharing: Search for share buttons -- Twitter/X, LinkedIn, Facebook, copy-link, email share
  7. Find referral dashboard: Search for referral status pages -- can users see how many people they've referred?
  8. Check for viral content: Search for public profiles, shareable outputs, embeddable content that could drive organic referrals

Report: describe what referral/invite mechanics exist (or don't). Flag opportunities for viral growth.

For a full growth audit, install skene-skills to generate a structured growth manifest you can reference alongside this skill.


2. Program Types

2.1 Customer Referral Program

Existing users refer new users, both sides may receive rewards.

Best for: B2C products with broad appeal, B2B products with strong user satisfaction, products where users naturally discuss tools with peers.

Characteristics:

  • Referrers are genuine users who can authentically recommend
  • Referred users arrive with built-in trust (personal recommendation)
  • Quality of referred users is typically higher than paid acquisition
  • LTV of referred users is typically 16-25% higher than organic
  • Program participation rates typically range 2-10% of active users

2.2 Partner/Affiliate Program

Third parties (bloggers, consultants, agencies, influencers) drive signups for commission.

Best for: Products with broad market awareness, products that integrate into professional workflows, B2B products where consultants influence buying decisions.

Characteristics:

  • Affiliates are motivated primarily by commission
  • Higher volume potential but lower average quality
  • Requires more tracking infrastructure and anti-fraud measures
  • Commission structures need to be competitive with alternatives
  • Need clear terms of service and brand guidelines

2.3 Hybrid Program

Customer referral with affiliate-level tracking, or tiered program where top referrers graduate to affiliate status.

Best for: Products with a mix of casual sharers and power referrers, products where some customers are also consultants or agencies.

Characteristics:

  • Standard referral for all users (simple reward)
  • Enhanced tracking and higher rewards for top referrers
  • Some users become semi-professional advocates
  • Requires more complex program management

3. Referral Loop Anatomy

Every referral program follows four steps: Trigger, Share, Incentive, Reward.

3.1 Trigger: What Prompts a User to Refer?

Trigger TypeDescriptionStrengthHow to Implement
NPS 9-10 responseUser rates you highly, you ask for referralVery strong (genuine advocate)Post-NPS survey follow-up
Milestone completionUser achieves a meaningful outcomeStrong (emotional high point)In-product prompt at milestone
Prompted by productReferral prompt in natural workflowModerateIn-product referral surfaces
Incentive offerUser sees the reward and is motivated to shareModerate (may attract mercenary referrers)Referral page, email campaigns
Organic conversationUser mentions product in conversationStrong but unscalableFacilitate with easy sharing tools

Best practice: Layer multiple triggers. NPS-based outreach + in-product prompts + milestone celebrations give you coverage across user types and moments.

3.2 Share: How Do They Refer?

MechanismProsConsImplementation
Unique referral linkUniversal, trackable, easyImpersonal, can be leakedGenerated per user, shareable anywhere
Email invitePersonal, high conversionHigher friction, lower volumeIn-product email form with pre-written copy
Social sharingHigh reach, low effortLow conversion, noisyShare buttons with pre-populated content
Referral codeMemorable, shareable verballyManual entry required, can be shared publiclyShort alphanumeric code, entered at signup
In-product inviteContextual, integratedLimited to product interactions"Invite team member" or "Share workspace"
Gift linkFeels generous, personalHigher perceived commitmentUser sends a "gift" of free trial/credits

3.3 Incentive: What Motivates the Referred User?

The referred user needs a reason to act on the referral beyond trust in the referrer.

Incentive TypeExampleEffectiveness
Extended trial30-day trial instead of 14-dayGood for trial-based products
Account credits$50 in credits to startGood for usage-based pricing
Discount20% off first month/yearGood for subscription products
Premium featuresFree access to pro features for X daysGood for freemium products
No incentive (trust only)Referrer's recommendation is enoughWorks with strong brand/NPS

3.4 Reward: What Does the Referrer Get?

Reward TypeProsConsBest For
Account creditsLow cost, drives usageOnly valuable to active usersSaaS, usage-based products
Cash/gift cardsUniversally appealingHigher cost, tax implicationsConsumer, high-LTV B2B
Subscription discountReduces churn, drives loyaltyReduces revenue per userSubscription products
Feature unlockZero marginal costOnly valuable if features desirableFreemium products
Extended planExtra months freeDelays revenueTrial/subscription products
Charity donationFeel-good, shareableLess personally motivatingMission-driven brands
Swag/physicalMemorable, social proofLogistics cost, scalabilityCommunity-driven brands
Tiered rewardsEscalating rewards for more referralsMore complex to manageHigh-engagement communities

4. Reward Calculation

4.1 Maximum Reward Formula

Max Referral Reward = (Customer LTV x Gross Margin) - Target CAC

Where:
- Customer LTV: Average lifetime revenue from a customer
- Gross Margin: Revenue minus COGS (typically 70-90% for SaaS)
- Target CAC: What you want to spend to acquire a customer via referral

Example:

LTV = $2,400 (24 months x $100/month)
Gross Margin = 80%
Target Referral CAC = $200 (lower than paid CAC of $400)

Max Reward = ($2,400 x 0.80) - $200 = $1,720

But you wouldn't pay $1,720. You'd offer a reward that is:
- Attractive enough to motivate sharing (typically 5-20% of annual plan value)
- Combined two-sided reward: $100 referrer + $50 referred = $150 total cost
- Resulting Referral CAC: $150 per customer (vs $400 paid CAC = 62% savings)

4.2 Two-Sided vs One-Sided Rewards

Two-sided (both sides get rewarded):

  • Higher participation rates (referrer feels good giving something, not just getting)
  • Referrer has a non-selfish pitch ("we both get $50")
  • Higher conversion on referred side (incentive to act)
  • Best for: most referral programs

One-sided referrer only:

  • Simpler to communicate and manage
  • Can offer higher referrer reward
  • Risk: feels transactional, lower conversion on referred side
  • Best for: affiliate programs, high-value B2B

One-sided referred only:

  • Referrer is motivated by altruism or product love
  • Lower referral volume but higher quality
  • Best for: products with very high NPS where recommendation is its own reward

5. Referral Program Design Checklist

Pre-Launch

  • Value proposition is clear: Both referrer and referred know exactly what they get
  • Sharing is frictionless: One-click link copy, easy email, social share buttons
  • Referral link is unique and trackable: Per-user links with UTM parameters
  • Landing page for referred users: Personalized page mentioning the referrer and the reward
  • Reward fulfillment is automated: No manual steps, instant or clearly-timed delivery
  • Terms and conditions are written: Eligibility, reward limits, anti-fraud rules, expiration
  • Anti-fraud measures are in place: Duplicate detection, self-referral prevention, velocity limits
  • Tracking is instrumented: End-to-end attribution from share to signup to activation to reward

In-Product Surfaces

  • Settings/account page: Dedicated referral section with link, stats, reward balance
  • Share button: Prominent share/invite button in key workflows
  • Milestone prompts: Post-achievement prompts to share success
  • Dashboard widget: "Invite friends" card on main dashboard
  • Team invite flow: Referral mechanic integrated into team member invitation
  • Success states: After completing a key action, suggest sharing

Email Surfaces

  • Post-purchase/signup: "Share [Product] with friends" email after first purchase or key activation
  • Milestone celebration: "You just [achievement]! Share the love" email
  • NPS follow-up: After a 9-10 NPS score, invite them to refer
  • Anniversary: "It's been 1 year! Invite a friend and get [reward]"
  • Referral program announcement: Launch email to entire user base
  • Referral reminder: Periodic reminders to users who haven't referred yet (max monthly)

Anti-Fraud Measures

  • Self-referral prevention: Block same email domain, same device, same IP
  • Duplicate referral prevention: One referral per unique email/account
  • Velocity limits: Max referrals per user per time period (e.g., 20/month)
  • Activation requirement: Reward only after referred user completes meaningful action
  • Review threshold: Manual review for users with unusually high referral activity
  • Terms enforcement: Clear terms about fraud, with ability to revoke rewards

6. Real-World Examples

Dropbox

  • Mechanic: Two-sided storage reward
  • Referrer gets: 500MB extra storage per referral (up to 16GB)
  • Referred gets: 500MB extra storage
  • Why it worked: Reward was the product itself (storage), zero marginal cost, high perceived value, seamless in-product flow
  • Key insight: The reward (storage) made the product more valuable, creating a compounding loop

Uber

  • Mechanic: Two-sided ride credit
  • Referrer gets: $10-20 ride credit (varied by market)
  • Referred gets: $10-20 ride credit on first ride
  • Why it worked: Immediate, tangible value; easy to share (unique code); strong network effects in cities
  • Key insight: Localized reward amounts based on market economics

Morning Brew

  • Mechanic: Tiered swag rewards for newsletter referrals
  • Referrer gets: 1 referral = stickers, 3 = Sunday edition, 5 = t-shirt, 25 = sweatshirt, 100 = custom mug
  • Referred gets: Free newsletter (no-cost incentive needed)
  • Why it worked: Gamification, status (shareable referral count), physical rewards created social proof
  • Key insight: Tiered rewards kept users referring past the first one

Notion

  • Mechanic: Credit-based referral
  • Referrer gets: $5 credit per referral (applied to subscription)
  • Referred gets: $10 credit
  • Why it worked: Asymmetric reward favoring the referred user; product itself drove word-of-mouth
  • Key insight: Higher reward for referred user (2x referrer) increased conversion rate

7. Affiliate Program Specifics

7.1 Commission Structures

StructureDescriptionExampleBest For
Flat fee per signupFixed amount per qualified signup$50 per signupLow-price products, lead gen
Percentage of saleCommission as % of first payment20% of first yearSaaS, subscription products
Recurring commission% of revenue for customer lifetime15% monthly for 12 monthsHigh-retention SaaS
Tiered commissionIncreasing % based on volume15% for 1-10, 20% for 11-50, 25% for 50+Scaling affiliate programs
Performance bonusExtra rewards for hitting targetsExtra $500 for 50+ signups/monthMotivating top affiliates

7.2 Attribution Models

ModelDescriptionProsCons
First-touchCredit goes to first referral sourceSimple, rewards discoveryIgnores influence chain
Last-touchCredit goes to last referral source before signupSimple, rewards conversionIgnores awareness generation
Last non-direct clickCredit to last referral that isn't directBalances simplicity and accuracyStill single-touch
Multi-touchCredit split across all touchpointsMost accurateComplex to implement
Cookie-based with windowFirst/last touch within a cookie window (30-90 days)Industry standardCookie limitations

7.3 Affiliate Program Operations

Payout terms:

  • Net-30 or Net-60 payment (standard)
  • Minimum payout threshold ($50-100)
  • Payout methods: bank transfer, PayPal, account credits
  • Currency handling for international affiliates

Partner tiers:

TierQualificationBenefits
StandardAny approved affiliateBase commission rate, standard tracking
Silver10+ referrals/monthHigher commission, priority support
Gold50+ referrals/monthHighest commission, co-marketing, early access
StrategicCustomCustom terms, dedicated account manager

Brand guidelines for affiliates:

  • Approved messaging and claims
  • Logo usage guidelines
  • Prohibited tactics (spam, misleading claims, trademark bidding)
  • Required disclosures (FTC compliance for US affiliates)

8. Metrics

8.1 Primary Metrics

MetricFormulaBenchmark
Referral rateUsers who refer / Total active users2-10%
Invite-to-signup conversionSignups from referrals / Invites sent5-25%
Referred user activation rateActivated referred users / Referred signupsCompare to organic
Referred user LTVAverage LTV of referred usersTypically 16-25% higher than organic
Program ROI(Referred user revenue - Program costs) / Program costs> 3x
Cost per referred acquisitionTotal program costs / Referred signupsShould be < paid CAC

8.2 Funnel Metrics

Track the complete referral funnel:

Step 1: Eligible users (total active users)           [N]
Step 2: Users who see referral prompt                  [N] ([X]% of step 1)
Step 3: Users who visit referral page                  [N] ([X]% of step 2)
Step 4: Users who copy link / send invite              [N] ([X]% of step 3)
Step 5: Unique referred visitors (clicked link)        [N] ([X]% of step 4)
Step 6: Referred signups                               [N] ([X]% of step 5)
Step 7: Referred activations                           [N] ([X]% of step 6)
Step 8: Referred paid conversions                      [N] ([X]% of step 7)
Step 9: Rewards issued                                 [N] ([X]% of step 8)

8.3 Quality Metrics

MetricWhat It Tells You
Referred vs organic retention (30/60/90 day)Are referred users sticking around?
Referred vs organic activation rateAre referred users finding value?
Referred vs organic time-to-valueAre referred users activating faster?
Referrer retention impactDo referrers retain better than non-referrers?
Top referrer concentrationIs the program over-reliant on a few power referrers?
Fraud rateWhat % of referrals are fraudulent? (Target: <2%)

9. A/B Testing

What to Test (Priority Order)

  1. Reward amount: Does a higher/lower reward change referral rate significantly?
  2. Reward type: Credits vs cash vs feature unlock vs discount
  3. Referral prompt timing: When in the user journey to surface the referral ask
  4. Share mechanism: Link vs email vs social vs code
  5. Landing page for referred users: Personalization, copy, layout
  6. Two-sided vs one-sided: Does adding a referred user incentive increase conversion?
  7. Referral copy: How the ask is framed (altruistic vs transactional vs social)

Testing Template

Test: [Descriptive name]
Hypothesis: Changing [element] from [control] to [variant] will increase [metric] by [X]% because [reason]
Primary metric: [Referral rate / Invite-to-signup / Program ROI]
Secondary metrics: [Referred user quality, activation rate, LTV]
Sample: [Users exposed to referral prompt]
Duration: [Minimum 2-4 weeks]
Minimum sample: [200+ referrals per variant for statistical significance]

10. Output Format

When designing a referral program, produce this specification:

# Referral Program Design Document

## Program Overview
- Program type: [Customer referral / Affiliate / Hybrid]
- Goal: [Primary objective -- e.g., reduce CAC, increase organic signups]
- Target audience: [Which users are eligible to refer]
- Launch timeline: [Phases and dates]

## Reward Structure
- Referrer reward: [Type, amount, timing]
- Referred reward: [Type, amount, timing]
- Reward calculation: [LTV x Margin - Target CAC = Max reward budget]
- Anti-fraud rules: [Self-referral, velocity, activation requirement]

## Referral Loop Design
- Trigger: [What prompts users to refer -- specific moments/prompts]
- Share mechanism: [Link, email, social, code -- which channels]
- Referred user experience: [Landing page, signup flow, first experience]
- Reward fulfillment: [How and when rewards are delivered]

## In-Product Surfaces
- [Surface 1]: [Location, design, trigger]
- [Surface 2]: [Location, design, trigger]
- [Surface 3]: [Location, design, trigger]

## Email Campaign Plan
- [Email 1]: [Trigger, segment, content summary]
- [Email 2]: [Trigger, segment, content summary]

## Terms and Conditions Summary
- Eligibility: [Who can participate]
- Reward limits: [Max referrals per user per period]
- Fraud policy: [What constitutes fraud, consequences]
- Expiration: [Reward expiration, program end date if applicable]

## Metrics and Measurement
- Primary KPIs: [List with targets]
- Funnel tracking: [Steps to instrument]
- Reporting cadence: [Weekly/monthly dashboard]
- Success criteria: [What constitutes program success at 30/60/90 days]

## Launch Plan
- Phase 1 (Soft launch): [Scope, audience, duration]
- Phase 2 (Full launch): [Scope, audience, channels]
- Phase 3 (Optimization): [A/B tests, iteration plan]

## Budget
- Estimated referral volume: [N referrals/month]
- Cost per referral: [$X (referrer reward + referred reward)]
- Monthly program cost: [$X]
- Expected ROI: [Revenue from referred users - Program costs]

11. Launch Sequence

Phase 1: Soft Launch (2-4 Weeks)

  1. Launch to top 10% of users by engagement or NPS score
  2. Monitor reward fulfillment and fraud signals
  3. Gather qualitative feedback (is the value prop clear? Is sharing easy?)
  4. Measure baseline metrics (referral rate, conversion, quality)
  5. Fix issues before broader launch

Phase 2: Full Launch

  1. Enable for all eligible users
  2. Send announcement email to full user base
  3. Add in-product surfaces (dashboard widget, milestone prompts)
  4. Monitor metrics daily for first two weeks
  5. Adjust targeting and frequency based on early data

Phase 3: Optimization (Ongoing)

  1. A/B test reward amounts and types
  2. Optimize referral prompt timing and placement
  3. Improve referred user landing page and onboarding
  4. Test new share mechanisms
  5. Analyze referred user quality vs organic (retention, LTV)
  6. Iterate on anti-fraud measures based on observed patterns

12. Common Pitfalls

PitfallConsequencePrevention
Launching before product-market fitLow referral rates, poor referred user qualityWait for NPS > 30 before investing in referral program
Reward too lowInsufficient motivation, low participationBenchmark against competitors, test reward levels
Reward too highAttracts mercenary referrers, unsustainable costCalculate max reward from LTV, monitor ROI
Complex sharing processUsers abandon before completing referralMinimize steps (target 1-2 clicks to share)
No activation requirementFake signups to claim rewardsRequire meaningful action before reward
Ignoring referred user experienceHigh signup but low activation for referred usersDesign personalized onboarding for referred users
Set and forgetProgram stagnates, no improvementMonthly review, quarterly optimization
No fraud preventionProgram exploited, unsustainable costsImplement fraud detection from day one

Related skills: viral-loops, growth-loops, expansion-revenue

Download now (ZIP)

  • Other versions50 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 50

    1. TheCraigHewitt/seomachine★ 7.5ksame name
    2. appeeky/aso-skills★ 2.2ksame name
    3. Eronred/aso-skills★ 2.2ksame name
    4. LeoYeAI/openclaw-marketing-skills★ 1ksame name
    5. OpenClaudia/openclaudia-skills★ 724same name
    6. mysticaltech/marketingskills★ 352same name
    7. b1rdmania/ghostclaw★ 91same name
    8. MoizIbnYousaf/marketing-cli★ 33same name
    9. robertbstillwell/marketing-skills★ 26same name
    10. ukunal91app/Marketing-Skills-by-Corey-Haines★ 26same name

    40 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.

  • Used alongsideProjects with it also use aso-audit, product-marketing-context and 10 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-vitaSkill

      aso-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 9 projects that use this

    • xfstudioSkill

      product-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 20 projects that use this

    • ukunal91appSkill

      revops

      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

    • ukunal91appSkill

      churn-prevention

      When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see email-sequence. For in-app upgrade paywalls, see paywall-upgrade-cro.

      Also in 16 projects that use this

    • buildingwithaiSkill

      sales-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

    • VercelSkill

      site-architecture

      Use when planning or restructuring what pages a site has and how they connect: hierarchy, navigation, URL patterns, breadcrumbs, and internal linking. Not for XML sitemaps, which are in seo-audit.

      Also in 18 projects that use this

    • +5 more from ukunal91app
  • In this repository29 other files it gives its agents.

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.