skillboardUpdated every 6 hours
skillboardWhen the user wants to plan, implement, or optimize creator program strategy. Also use when the user mentions "creator program," "creator partnership," "content co-creation," "creator ambassador," "creator economy," "creator collaboration," "UGC program," "creator incentives," or "creator community." For influencers, use influencer-marketing.
Guides creator program strategy for AI/SaaS products. Long-term partnerships with creators for content co-creation and brand building. Differs from affiliate (sales focus) and influencer (paid promotion focus).
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 content needs.
Identify:
| Dimension | Creator Program | Affiliate | Influencer | |-----------|-----------------|-----------|------------| | Goal | Brand + content co-creation | Direct sales | Brand exposure | | Incentive | Credits, free use, revenue share | Commission | Paid, product | | Content | Must use product to create | Links | Influencer original | | Relationship | Long-term | Transactional | Flexible |
| Model | Use | Examples | |-------|-----|----------| | Credits | AI tools; cost control | Credit-based AI tools | | Payment | High-quality content; budget available | Paid creator programs | | Hybrid | Credits + commission, brand partnership | Common for SaaS | | Marketplace | Template/plugin sales; revenue share | Design tools, CMS marketplaces |
| Phase | Weeks | Tasks | |-------|-------|-------| | Plan | 1–2 | Goals, incentives, application form, resources | | Launch | 3–4 | Landing page, promotion, tracking | | Recruit | 5–8 | Screen applications, outreach, onboarding | | Co-create | 9–12 | Content publishing, support, promotion | | Optimize | Ongoing | Metrics, feedback, incentive tweaks |
| Principle | Use | |-----------|-----| | Value for all | Each participant (creators, content, integrations) gains value—not just the platform | | Integrations | Product must integrate with upstream/downstream tools; enables solution bundling | | Multi-product | Form solution suites; support partners including you in their stacks |
Creators + community: Free tools + high-quality creator content; mutual promotion; user-generated quality often exceeds in-house.
| Challenge | Solution | |-----------|----------| | Content quality | Clear standards; review; suspend non-compliant | | Brand consistency | Guidelines; content review; unified tags | | Measurement | UTM; KPIs: applications, approval rate, content output | | Cost control | Credit model; tier incentives; limit creator count |
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/creator-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/creator-program"
cp -r "skills/channels/partnerships/creator-program" ".claude/skills/creator-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.