Paywalls

Use this when you're building in-app upgrade screens, feature gates, or those modals that appear when users hit their free tier limits. It covers timing (show after the aha moment, not during onboarding), copywriting patterns for different trigger types (usage limits vs trial expiration vs feature locks), and the actual UI components that work. The emphasis on "value before ask" and respecting the dismiss action is solid advice that'll save you from annoying users into churning. Includes specific templates for different paywall types and clear guidance on what to A/B test. Distinct from public pricing pages, this is all about those in-product moments where someone's already using your app and deciding whether to pay.

skills.sh installs: 78.1K
GitHub stars: 59.5K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add coreyhaines31/marketingskills --skill paywalls --agent claude-code

Installs into .claude/skills of the current project.

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.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, 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?