When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
Guides affiliate program page content and structure for conversion and quality affiliate signups.
When invoking: On first use, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product, audience, and proof points.
Identify:
| Item | Include | |------|---------| | Commission rate | Percentage or flat | | Recurring vs. one-time | Duration of recurring | | Cookie/tracking window | How long the cookie lasts | | Minimum payout | Threshold to receive payment | | Payment schedule | When payouts occur | | Payment methods | PayPal, bank transfer, etc. | | Refund/chargeback policy | How they affect commissions |
Affiliates stake their reputation; convince them it's worth promoting:
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/affiliate-program · pinned to the source commit
git clone https://github.com/kostja94/marketing-skills.git
cd marketing-skills
git checkout 70987bad4ebe9dce1f74858c1c64f3f8810f18e4
mkdir -p ".claude/skills/affiliate-program"
cp -r "skills/pages/marketing/affiliate-program" ".claude/skills/affiliate-program"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 70987bad4ebe. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.