Agent skill
suede-referrals
Suede-owned referral and affiliate program discipline.
Filed under Onboarding, retention and expansion.
From JasonColapietro/suede-creator-skills · 79 skills · 135 · pushed 2026-09-13
What it does when it runs
Suede-owned referral and affiliate program discipline. Use when designing refer-a-friend mechanics, ambassador or partner incentives, fraud controls, attribution, payout logic, or viral-loop measurement. NOT FOR: executing payouts or changing billing, launch-wide packaging (use suede-launch-packaging), lifecycle messaging (use suede-emails), or reporting unverified referral lift.
Read from the skill and the 5 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- docs.nvidia.com
- skills.suedeai.ai
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/JasonColapietro/suede-creator-skills.git /tmp/suede-creator-skills git -C /tmp/suede-creator-skills sparse-checkout set "skills/suede-referrals" mkdir -p ~/.claude/skills/suede-referrals cp -R "/tmp/suede-creator-skills/skills/suede-referrals/." ~/.claude/skills/suede-referrals/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
Or take the whole library
This repo ships a .claude-plugin manifest, so Claude Code can install all 79 skills at once. Plugin skills are invoked as /<plugin>:<skill>, so they never collide with your own.
/plugin marketplace add JasonColapietro/suede-creator-skills /plugin
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from JasonColapietro/suede-creator-skills/blob/5c61ad997adb202d505a7e46eaf39dcd51edbdc5/skills/suede-referrals/SKILL.md, which is licensed MIT (repository). 1,167 words, 30 headings.
Suede Referral & Affiliate Programs
Suede Referrals designs measurable customer, affiliate, and partner loops from incentive economics through attribution and fraud controls. It separates modeled loop performance from observed results and keeps activation and payouts behind approval.
Before Starting
Check for product marketing context first:
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, 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):
1. Program Type
- Customer referral program, affiliate program, or both?
- B2B or B2C?
- What's the average customer LTV?
- What's your current CAC from other channels?
2. Current State
- Existing referral/affiliate program?
- Current referral rate (% who refer)?
- What incentives have you tried?
3. Product Fit
- Is your product shareable?
- Does it have network effects?
- Do customers naturally talk about it?
4. Resources
- Tools/platforms you use or consider?
- Budget for referral incentives?
Referral vs. Affiliate
Customer Referral Programs
Best for:
- Existing customers recommending to their network
- Products with natural word-of-mouth
- Lower-ticket or self-serve products
Characteristics:
- Referrer is an existing customer
- One-time or limited rewards
- Higher trust, lower volume
Affiliate Programs
Best for:
- Reaching audiences you don't have access to
- Content creators, influencers, bloggers
- Higher-ticket products that justify commissions
Characteristics:
- Affiliates may not be customers
- Ongoing commission relationship
- Higher volume, variable trust
Referral Program Design
The Referral Loop
Trigger Moment → Share Action → Convert Referred → Reward → (Loop)
Step 1: Identify Trigger Moments
High-intent moments:
- Right after first "aha" moment
- After achieving a milestone
- After exceptional support
- After renewing or upgrading
Prompt cadence for customers who have not referred: day 7, day 30, day 60,
and after any milestone. The timing is this skill's call; the message copy is
not — hand that to suede-emails.
Step 2: Design Share Mechanism
Ranked by effectiveness:
- In-product sharing (highest conversion)
- Personalized link
- Email invitation
- Social sharing
- Referral code (works offline)
Step 3: Choose Incentive Structure
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
Program Optimization
Improving Referral Rate
If few customers are referring:
- Ask at better moments
- Simplify sharing process
- Test different incentive types
- Make referral prominent in product
If referrals aren't converting:
- Improve landing experience for referred users
- Strengthen incentive for new users
- Ensure referrer's endorsement is visible
A/B Tests to Run
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
Common Problems & Fixes
| Problem | Fix |
|---|---|
| Low awareness | Add prominent in-app prompts |
| Low share rate | Simplify to one click |
| Low conversion | Optimize referred user experience |
| Fraud/abuse | Apply the fraud controls below |
| One-time referrers | Add tiered/gamified rewards |
Fraud Controls
Read references/affiliate-programs.md §Fraud Prevention before designing rewards or writing program terms — it carries the technical, policy, and structural control set (delayed payout after activation, device and IP signals, clawback on refunds, per-period caps, manual review of suspicious patterns). Every program in this skill uses it, customer referral programs included, not only affiliate programs.
Set these thresholds explicitly, because the reference leaves them open:
- Name the qualifying downstream event that releases a reward (a paid conversion or day-N retention, N stated), never signup alone.
- Hold payouts until the refund/chargeback window has closed, and state that window in days.
- State the dollar amount above which a payout goes to manual review before it is released.
Measuring Success
Key Metrics
Program health:
- Active referrers (referred someone in last 30 days)
- Referral conversion rate
- Rewards earned/paid
Business impact:
- % of new customers from referrals
- CAC via referral vs. other channels
- LTV of referred customers
- Referral program ROI
Typical Findings
Industry-reported ranges, published by referral-platform vendors and not measured on this product. Use them to calibrate a recommendation; never assert them as a result this program will produce or has produced.
- Referred customers have 16-25% higher LTV
- Referred customers have 18-37% lower churn
- Referred customers refer others at 2-3x rate
Launch Checklist
Before Launch
- Define program goals and success metrics
- Design incentive structure
- Build or configure referral tool
- Create referral landing page
- Set up tracking and attribution
- Define fraud prevention rules
- Create terms and conditions
- Test complete referral flow
Launch
- Announce to existing customers
- Add in-app referral prompts
- Update website with program details
- Brief support team
Post-Launch (First 30 Days)
- Review conversion funnel
- Identify top referrers
- Gather feedback
- Fix friction points
- Send reminder emails to non-referrers
Affiliate Programs
For affiliate program design, commission structures, recruitment, fraud prevention, and tools: See references/affiliate-programs.md
Tool Integrations
These are evaluation examples, not guaranteed integrations. Verify current vendor documentation, pricing, account access, attribution behavior, payout controls, tax support, and data-export terms before recommending a platform.
| Tool | Best For | Verify Before Use |
|---|---|---|
| Rewardful / Tolt | SaaS affiliate programs | Billing integration, attribution, payouts |
| Mention Me | Enterprise referral programs | Identity, fraud, and reporting controls |
| Dub.co | Link tracking and attribution | Attribution window and privacy settings |
| Stripe | Commission-related payment records | Live objects, fees, approvals, tax workflow |
| Introw | Tiered channel partner operations | Deal registration and payout governance |
| PartnerStack | Enterprise partner ecosystems | Fees, attribution, approval, data export |
Boundaries
- Do not enable a program, create affiliate accounts, issue links, execute payouts, or change billing and commission objects without verified live state and explicit approval.
- Do not invent attribution, conversion, fraud, or viral-coefficient results; distinguish modeled economics from observed data.
- Do not decide tax, labor, privacy, contest, endorsement, or incentive compliance. Surface the jurisdiction-specific review needed before launch.
Routing
- Use
suede-launch-packagingto coordinate the approved program launch. - Use
suede-emailsfor referral invitation and nurture sequences. - Use
suede-marketing-psychologyto test incentive framing. - Use
suede-ab-testingto design and evaluate the incentive, messaging, and placement tests above. - Use
suede-analyticsto define and read referral attribution.
Files bundled with it
These load only when the skill asks for them, so they cost nothing until it runs.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- referrals by coreyhaines31 · 50,138
- customer-referrals by louisblythe · 153
Need help setting it up?
This page tells you what suede-referrals does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.