paywall-optimization
When the user wants to design, test, or optimize their app's paywall — layout, copy, pricing display, trial offers, plan structure, hard vs soft paywall, paywall placement, or paywall A/B tests. Use when the user mentions "paywall", "paywall design", "paywall conversion", "trial-to-paid", "soft paywall", "hard paywall", "paywall A/B test", "paywall copy", "plan picker", "annual vs monthly display", "best paywall", "RevenueCat paywall", "Superwall", "Adapty", or "my paywall isn't converting". For overall pricing strategy and monetization model choice, see monetization-strategy. For trial nurtur
npx skills add Eronred/aso-skills --skill paywall-optimization --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Paywall Optimization You are a paywall conversion specialist with deep knowledge of subscription app pricing psychology, A/B testing, and the major paywall frameworks (RevenueCat, Superwall, Adapty, native StoreKit). Your goal is to diagnose paywall under-performance and ship a higher-converting variant within 1–2 release cycles. ## Initial Assessment 1. Check for `app-marketing-context.md` — read it for app, audience, and price-point context 2. Ask for the **App ID** and **paywall framework** (RevenueCat / Superwall / Adapty / native) 3. Ask for current **paywall view → trial start** and **trial → paid** rates (last 30 days) 4. Ask for a **screenshot of the current paywall** (or 2–3 if there are variants) 5. Ask for **plan structure** — monthly, annual, lifetime, weekly? What price points? If RevenueCat is connected, pull subscription metrics first. If `asc-metrics` is available, cross-check trial counts. ## Diagnose Before You Redesign Run the **Paywall Conversion Funnel** before changing anything: | Stage | Healthy Range | Red Flag | |---|---|---| | App open → paywall view | 60–95% (depends on placement) | <50% (paywall buried) | | Paywall view → CTA tap | 25–45% | <15% (copy/
- Initial Assessment
- Diagnose Before You Redesign
- The 7-Element Paywall Audit
- Paywall Placement Strategy
- Pricing Display Patterns
- A/B Testing Playbook
- Output Template
- Common Mistakes
- Cross-Skill Handoffs
What does the paywall-optimization skill do?
When the user wants to design, test, or optimize their app's paywall — layout, copy, pricing display, trial offers, plan structure, hard vs soft paywall, paywall placement, or paywall A/B tests. Use when the user mentions "paywall", "paywall design", "paywall conversion", "trial-to-paid", "soft paywall", "hard paywall", "paywall A/B test", "paywall copy", "plan picker", "annual vs monthly display", "best paywall", "RevenueCat paywall", "Superwall", "Adapty", or "my paywall isn't converting". For overall pricing strategy and monetization model choice, see monetization-strategy. For trial nurtur
How do I install it?
Run `npx skills add Eronred/aso-skills --skill paywall-optimization --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Eronred/aso-skills, a repository with 1,708 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.