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

referral-programs

Designs and improves referral, affiliate, and word-of-mouth programs — incentive structure, mechanics, timing, and fraud control. Use this to build a referral or affiliate program, diagnose one that is not producing, decide what incentive to offer, or judge whether referral is a realistic channel for a product.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md3.4 KB
  • references/sources.md941 B

SKILL.md(原文)

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

Referral programs

Qualify the channel first

Referral programs amplify existing word of mouth. They do not create it.

If customers are not already recommending you unprompted, a program will not produce them — it will produce incentive-motivated signups that churn. Check first: is anyone referring today, and what do they say when they do?

Incentive design

  • Two-sided beats one-sided in most cases. It gives the referrer something to offer rather than something to gain, which removes the awkwardness that stops most referrals.
  • Match the reward to the product's value, not to a round number. Account credit usually outperforms cash, and costs less.
  • Reward the outcome you want. Paying on signup buys signups; paying on a retained, activated customer buys customers.
  • Cash rewards attract fraud, and fraud scales faster than the program does. Budget for detection before launch, not after.

Mechanics

The referral has to be effortless at the moment of enthusiasm, which means the ask must appear right after a success moment — not in a settings page nobody visits.

  • One-click share with pre-written text the referrer can edit.
  • A link that works everywhere and survives being pasted into any app.
  • Visible status: who was invited, what stage they reached, what has been earned. Ambiguity kills repeat referrals.
  • The referred person's experience must be better than a normal signup. Landing them on the generic homepage wastes the introduction.

Fraud control

Self-referral, disposable accounts, and coordinated rings. Minimum viable controls: reward only on a qualifying event well past signup, hold a payout window, deduplicate on payment method and device, and cap per-referrer volume pending review.

Affiliates are a different program

Affiliates are a paid channel with commercial terms, not enthusiastic customers. They need attribution rules, cookie windows, prohibited-methods terms — brand bidding and coupon-site behavior in particular — and monitoring. Run without terms and you will pay commission on customers you already had.

Measuring

Track referred-customer retention against baseline. If referred customers retain worse, the incentive is buying the wrong behavior and the program is losing money while appearing to work.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Launch referrals before the product retains. A referral program amplifies whatever is already there, churn included.
  • Pay a reward before the referred account is real — activated, paid, and past the refund window.
  • Ask for a referral in the same breath as an apology or an open support escalation.
  • Run affiliates and customer referrals on the same terms. They attract different people and need different controls.

レビュー

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

同じリポジトリのスキル

概要と使いどころ

Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.

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

cbrock84/headcount2,0312026年9月18日 更新

Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.

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

cbrock84/headcount2,0312026年9月18日 更新

Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.

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

cbrock84/headcount2,0312026年9月18日 更新

Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.

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

cbrock84/headcount2,0312026年9月18日 更新

Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.

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

cbrock84/headcount2,0312026年9月18日 更新

Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.

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

cbrock84/headcount2,0312026年9月18日 更新

cbrock84 のスキルをすべて見る

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