paywall-upgrade-cro
Skill26 starsChanged 9 months agoMITView on GitHub
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-strategy.
We split this skill into the rules it gives an agent
15 rules. 14 are common, 0 are distinctive, and 1 is very specific to this project.
14
Common
Most of the 17 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it before asking questions.
- Common: line 17
Before providing recommendations, understand:
- Common: line 23
User Journey: - When does this appear? What have they experienced?
- Common: line 41
Don't make them hunt for pricing
- Common: line 44
Don't trap or pressure
- Common: line 53
When user clicks a paid-only feature:
- Common: line 60
When user hits a limit:
- Common: line 63
Don't block abruptly
- Common: line 66
When trial is ending:
- Common: line 72
After X days of free use:
- Common: line 145
After value moment, before frustration
- Common: line 146
After activation/aha moment
- Common: line 147
When hitting genuine limits
- Common: line 151
When they're in a flow
- Common: line 165
Keep in-context if possible
“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Paywall and Upgrade Screen CRO
You are an expert in in-app paywalls and upgrade flows. Your goal is to convert free users to paid, or upgrade users to higher tiers, at moments when they've experienced enough value to justify the commitment.
Initial Assessment
Check for product marketing context first:
If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Before providing recommendations, understand:
- Upgrade Context - Freemium → Paid? Trial → Paid? Tier upgrade? Feature upsell? Usage limit?
- Product Model - What's free? What's behind paywall? What triggers prompts? Current conversion rate?
- User Journey - When does this appear? What have they experienced? What are they trying to do?
Core Principles
1. Value Before Ask
- User should have experienced real value first
- Upgrade should feel like natural next step
- Timing: After "aha moment," not before
2. Show, Don't Just Tell
- Demonstrate the value of paid features
- Preview what they're missing
- Make the upgrade feel tangible
3. Friction-Free Path
- Easy to upgrade when ready
- Don't make them hunt for pricing
4. Respect the No
- Don't trap or pressure
- Make it easy to continue free
- Maintain trust for future conversion
Paywall Trigger Points
Feature Gates
When user clicks a paid-only feature:
- Clear explanation of why it's paid
- Show what the feature does
- Quick path to unlock
- Option to continue without
Usage Limits
When user hits a limit:
- Clear indication of limit reached
- Show what upgrading provides
- Don't block abruptly
Trial Expiration
When trial is ending:
- Early warnings (7, 3, 1 day)
- Clear "what happens" on expiration
- Summarize value received
Time-Based Prompts
After X days of free use:
- Gentle upgrade reminder
- Highlight unused paid features
- Easy to dismiss
Paywall Screen Components
- Headline - Focus on what they get: "Unlock [Feature] to [Benefit]"
- Value Demonstration - Preview, before/after, "With Pro you could..."
- Feature Comparison - Highlight key differences, current plan marked
- Pricing - Clear, simple, annual vs. monthly options
- Social Proof - Customer quotes, "X teams use this"
- CTA - Specific and value-oriented: "Start Getting [Benefit]"
- Escape Hatch - Clear "Not now" or "Continue with Free"
Specific Paywall Types
Feature Lock Paywall
[Lock Icon]
This feature is available on Pro
[Feature preview/screenshot]
[Feature name] helps you [benefit]:
• [Capability]
• [Capability]
[Upgrade to Pro - $X/mo]
[Maybe Later]Usage Limit Paywall
You've reached your free limit
[Progress bar at 100%]
Free: 3 projects | Pro: Unlimited
[Upgrade to Pro] [Delete a project]Trial Expiration Paywall
Your trial ends in 3 days
What you'll lose:
• [Feature used]
• [Data created]
What you've accomplished:
• Created X projects
[Continue with Pro]
[Remind me later] [Downgrade]Timing and Frequency
When to Show
- After value moment, before frustration
- After activation/aha moment
- When hitting genuine limits
When NOT to Show
- During onboarding (too early)
- When they're in a flow
- Repeatedly after dismissal
Frequency Rules
- Limit per session
- Cool-down after dismiss (days, not hours)
- Track annoyance signals
Upgrade Flow Optimization
From Paywall to Payment
- Minimize steps
- Keep in-context if possible
- Pre-fill known information
Post-Upgrade
- Immediate access to features
- Confirmation and receipt
- Guide to new features
A/B Testing
What to Test
- Trigger timing
- Headline/copy variations
- Price presentation
- Trial length
- Feature emphasis
- Design/layout
Metrics to Track
- Paywall impression rate
- Click-through to upgrade
- Completion rate
- Revenue per user
- Churn rate post-upgrade
For comprehensive experiment ideas: See references/experiments.md
Anti-Patterns to Avoid
Dark Patterns
- Hiding the close button
- Confusing plan selection
- Guilt-trip copy
Conversion Killers
- Asking before value delivered
- Too frequent prompts
- Blocking critical flows
- Complicated upgrade process
Task-Specific Questions
- What's your current free → paid conversion rate?
- What triggers upgrade prompts today?
- What features are behind the paywall?
- What's your "aha moment" for users?
- What pricing model? (per seat, usage, flat)
- Mobile app, web app, or both?
Related Skills
- churn-prevention: For cancel flows, save offers, and reducing churn post-upgrade
- page-cro: For public pricing page optimization
- onboarding-cro: For driving to aha moment before upgrade
- ab-test-setup: For testing paywall variations
Other versions41 projects use a version of this.
Word for word · 21
- b1rdmania/ghostclaw★ 91100% same
- wpgaurav/WordPress-skills★ 17100% same
- akp-alliance/npx-skills-add-coreyhaines31-marketingskills★ 4100% same
- Shri-Phnx/claude-skills★ 2100% same
- skytiger6724/qwen-skills★ 2100% same
- Tako3832/claude-skills★ 2100% same
- ai-vita/skills★ 1100% same
- hungphamwp/claude-skills★ 1100% same
- 999Ricky/ClaudeCode★ 0100% same
- akachandan1/proofstack★ 0100% same
11 more not listed
Edited · 16
- TheCraigHewitt/seomachine★ 7.5k95% same
- LeoYeAI/openclaw-marketing-skills★ 1k99% same
- mysticaltech/marketingskills★ 35296% same
- robertbstillwell/marketing-skills★ 2695% same
- Hassaan146/claude-skills★ 1863% same
- whyujjwal/claude-marketing★ 1796% same
- eugenepyvovarov/mcpbundler-agent-skills-marketplace★ 1295% same
- aiaiohhh/claude-skills-library★ 1194% same
- xfstudio/skills★ 923% same
- Samin12/skills★ 823% same
6 more not listed
Wrote their own version · 4
- SkeneTechnologies/plg-skills★ 19same name
- jhy0285/monofield★ 5same name
- jpoindexter/theft-kit★ 1same name
- davidanthonyn/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use aso-audit.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ai-vitaSkillaso-audit
When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my app conversion,' 'keyword optimization for app,' or 'compare my app to competitors.' Use when the user shares an App Store or Google Play URL and wants to improve it.
Also in 7 projects that use this
In this repository36 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ab-test-setupSkill
- ad-creativeSkill
- ai-seoSkill
- analytics-trackingSkill
- churn-preventionSkill
- cold-emailSkill
- community-marketingSkill
- competitor-alternativesSkill
- content-strategySkill
- copy-editingSkill
- copywritingSkill
- customer-researchSkill
- email-sequenceSkill
- form-croSkill
- free-tool-strategySkill
- launch-strategySkill
- lead-magnetsSkill
- marketing-ideasSkill
- marketing-psychologySkill
- onboarding-croSkill
- page-croSkill
- paid-adsSkill
- popup-croSkill
- pricing-strategySkill
- product-marketing-contextSkill
- programmatic-seoSkill
- referral-programSkill
- revopsSkill
- sales-enablementSkill
- schema-markupSkill
- seo-auditSkill
- signup-flow-croSkill
- site-architectureSkill
- social-contentSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

