luna/marketingskills
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

feat: consolidate page-cro and form-cro into unified cro skill

Browse Source 
- Create skills/cro/ with shared CRO analysis framework
- Move page-specific content to references/page.md
- Move form-specific content to references/form.md
- Copy experiments reference from page-cro
- Remove skills/page-cro/ and skills/form-cro/
- Update all cross-references across skills, tools, README, AGENTS.md

BREAKING: page-cro and form-cro are replaced by cro.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Corey Haines
2026-04-03 16:27:53 -07:00
parent 83150fdc08
commit 8b82f733b6
39 changed files with 151 additions and 286 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/paywalls/SKILL.md
+2 -2
View File
@@ -1,6 +1,6 @@
---
name: paywalls
description: When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see page-cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.
description: When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.
metadata:
version: 1.1.0
---
@@ -222,6 +222,6 @@ What you've accomplished:
## Related Skills
- **churn-prevention**: For cancel flows, save offers, and reducing churn post-upgrade
- **page-cro**: For public pricing page optimization
- **cro**: For public pricing page optimization
- **onboarding**: For driving to aha moment before upgrade
- **ab-testing**: For testing paywall variations