本文へ移動
cccskills
無料GitHub で公開

suede-referrals

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.

インストール方法を見る

含まれるファイル(6)

  • SKILL.md8.3 KB
  • agents/openai.yaml581 B
  • CARD.md4.2 KB
  • evals/evals.json6.3 KB
  • references/affiliate-programs.md4.3 KB
  • references/program-examples.md3.2 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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:

  1. In-product sharing (highest conversion)
  2. Personalized link
  3. Email invitation
  4. Social sharing
  5. 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

ProblemFix
Low awarenessAdd prominent in-app prompts
Low share rateSimplify to one click
Low conversionOptimize referred user experience
Fraud/abuseApply the fraud controls below
One-time referrersAdd 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.

ToolBest ForVerify Before Use
Rewardful / ToltSaaS affiliate programsBilling integration, attribution, payouts
Mention MeEnterprise referral programsIdentity, fraud, and reporting controls
Dub.coLink tracking and attributionAttribution window and privacy settings
StripeCommission-related payment recordsLive objects, fees, approvals, tax workflow
IntrowTiered channel partner operationsDeal registration and payout governance
PartnerStackEnterprise partner ecosystemsFees, 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-packaging to coordinate the approved program launch.
  • Use suede-emails for referral invitation and nurture sequences.
  • Use suede-marketing-psychology to test incentive framing.
  • Use suede-ab-testing to design and evaluate the incentive, messaging, and placement tests above.
  • Use suede-analytics to define and read referral attribution.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Suede-affiliated Amazon money-recovery audit for restocking fees, short or denied refunds, and Amazon-billed subscriptions. Use when the user mentions a restocking fee, a short or denied Amazon refund, or a forgotten Prime Video Channel, Audible, Kindle Unlimited, or Prime charge, or asks whether Amazon still owes or bills them. Read-only discovery; no chat, cancellation, or dispute without the account owner's per-item confirmation, and never a promise of recovery. Requires an authenticated Claude in Chrome session. NOT FOR: bank chargebacks, marketplace A-to-z seller claims, price-protection claims, or subscriptions billed outside Amazon (use subscription-recovery).

日本語の概要は準備中です。原文の説明を表示しています。

JasonColapietro/suede-creator-skills1272026年10月12日 更新

Suede Labs Android app factory: plan, build, test, and release a production-grade native Android app from a product idea through Google Play. Use for requests to create, ship, submit, monetize, or modernize an Android app. Covers Kotlin and Jetpack Compose architecture, API-level policy verification, accessibility, privacy and Data Safety, Play Billing, Play Integrity, account deletion, testing, performance, store assets, signing, staged rollout, and a release evidence gate. NOT FOR: iOS work (private Suede Labs companion, not in this pack: ios-app-factory), a review-only pass on an existing app (use suede-code-review), or live Play listing and keyword audits on a shipped app (use suede-aso).

日本語の概要は準備中です。原文の説明を表示しています。

JasonColapietro/suede-creator-skills1272026年10月12日 更新

Design, review, and visually QA web and app interfaces against explicit design laws so shipped screens look intentional instead of generic AI output.

日本語の概要は準備中です。原文の説明を表示しています。

JasonColapietro/suede-creator-skills1272026年10月12日 更新

Suede AI full-stack surface builder that runs design, copy, and visual QA as one pass: landing pages, brand surfaces, product UI, dashboards, campaigns, launch pages, and reference-to-target restyles (suedify). Use when a build needs layout and words together, when a redesign or launch surface has to ship end to end, when the request is 'make this site look like that one', or when design, copy, asset, and QA lanes have to move at once. NOT FOR: a design-token, dark-mode, or single-component decision (use suede-design); copy with no layout work (use johnny-suede-write, or suede-copy for one standalone conversion surface); conversion and funnel architecture (use suede-site-alchemy); multi-agent orchestration protocols, WIP protection, and rollback trees (use suede-agent-teams).

日本語の概要は準備中です。原文の説明を表示しています。

JasonColapietro/suede-creator-skills1272026年10月12日 更新

Suede Labs full writing stack: sharper copy for docs, pages, email, social, headlines, CTAs, product listings, and public explainers, with an SEO/AEO/AI EO pass, persona and framework selection, brand-voice alignment, and a scored ship gate. Use when a writing job spans more than one surface, needs a voice retune as well as a draft, needs discoverability metadata alongside the copy, when the document is one an agent reads such as a SKILL.md, CLAUDE.md, or AGENTS.md, or when the user asks for 'the full writing stack', a launch package, or a public explainer talk-track. NOT FOR: one standalone conversion surface in one pass (use suede-copy); stripping AI patterns from text you did not write (use suede-deslop); a researched multi-phase piece for a high-stakes public surface (use suede-ship-copy); a deep standalone SEO audit (use suede-seo-audit); copy that ships inside a design or layout build (use johnny-suede-design).

日本語の概要は準備中です。原文の説明を表示しています。

JasonColapietro/suede-creator-skills1272026年10月12日 更新

Suede Labs workflow for turning a website, PWA, dashboard, or marketplace into an iOS app. Use when the user has a live site or web app and asks to put it on the App Store, wrap it in an app, ship an iOS version, or convert a PWA to native, covers URL audit, shell-vs-native strategy, App Store 4.2 wrapper risk, native value requirements, screenshots, metadata, privacy answers, and the release gate. NOT FOR: building a native iOS app with no existing site (private Suede Labs companion, not in this pack: ios-swiftui-product); repairing or releasing an existing Capacitor shell (private Suede Labs companion, not in this pack: ios-capacitor-shell); Android conversions (use android-app-factory); live listing and keyword audits on a shipped app (use suede-aso).

日本語の概要は準備中です。原文の説明を表示しています。

JasonColapietro/suede-creator-skills1272026年10月12日 更新

JasonColapietro のスキルをすべて見る

このスキルの問題を報告する