
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 nurture, dunning, and churn, see subscription-lifecycle. For where in the onboarding the paywall fires, see onboarding-optimization.
- Installs
- 1.9K
- Last 24h
- +15
- Trending rank
- #6957
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/appeeky/aso-skills --skill paywall-optimization- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads paywall-optimization automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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
- Check for
app-marketing-context.md— read it for app, audience, and price-point context - Ask for the App ID and paywall framework (RevenueCat / Superwall / Adapty / native)
- Ask for current paywall view → trial start and trial → paid rates (last 30 days)
- Ask for a screenshot of the current paywall (or 2–3 if there are variants)
- 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/offer weak) |
| CTA tap → purchase confirm | 70–90% | <50% (StoreKit friction or price shock) |
| Trial start → paid conversion | 25–60% (varies by category) | <15% (wrong audience or price) |
Identify the weakest stage. Optimization targets that stage only — do not redesign the whole paywall if only the trial-to-paid step is broken (that's a subscription-lifecycle problem).
The 7-Element Paywall Audit
Score the current paywall on each (1–5):
- Headline — does it state the outcome (not the feature)? "Unlock unlimited workouts" beats "Pro Plan".
- Value props — 3–5 max, benefit-led, scannable in <3 seconds.
- Social proof — rating, review count, user count, or named testimonials. Required above the fold.
- Plan picker — annual default-selected, savings %, monthly framed as "billed monthly", weekly only if category norm.
- Price anchoring — annual shown as monthly equivalent ("$3.33/mo, billed annually") + total ("$39.99/yr").
- Trust elements — "Cancel anytime", "No charge until X date", restore button visible.
- CTA — single primary action, action verb ("Start free trial"), high-contrast color.
Anything ≤2 is a quick win. Anything 3 is an A/B test candidate.
Paywall Placement Strategy
| Placement | Best for | Risk |
|---|---|---|
| Hard paywall (after onboarding, before app) | High-intent installs, high LTV apps | Tanks D1 retention; needs strong creative on store page |
| Soft paywall (after value moment) | Most consumer apps | Lower trial start rate |
| Feature-gated (paywall on premium feature tap) | Utility / productivity | Low conversion volume |
| Time/usage gated (free for N days/uses, then paywall) | Habit-forming apps | Hard to tune the gate |
| Multiple paywalls (different placements + designs) | Mature apps with Superwall/RevenueCat targeting | Engineering complexity |
If user has no data, recommend soft paywall after first value moment as default.
Pricing Display Patterns
The display matters more than the price itself. Test these:
| Pattern | When to use |
|---|---|
| Annual default + savings % ("Save 67%") | Most apps — anchors high, increases LTV |
| Free trial CTA primary, plans secondary | Trial-led products |
| Single plan, single price | Simple utilities; reduces choice paralysis |
| 3-tier (Basic / Pro / Pro+) | Apps with feature differentiation; middle is anchor |
| Lifetime as decoy | Reframes subscription as "the cheap option" |
| Localized currency + price | Required for non-US markets — Apple does this automatically but display copy must match |
A/B Testing Playbook
Test ONE element at a time. Required sample size depends on baseline conversion — use these floors:
| Baseline conversion | Min users/variant for ~10% lift detection |
|---|---|
| 5% | ~6,000 |
| 15% | ~2,000 |
| 30% | ~1,000 |
Test priority order (ship one per cycle):
- Headline copy (highest leverage)
- Trial offer (3-day vs 7-day vs no trial)
- Plan default (annual vs monthly pre-selected)
- CTA copy ("Start free trial" vs "Try free for 7 days" vs "Continue")
- Social proof element (rating vs user count vs testimonial)
- Visual style (clean vs bold vs photo background)
- Number of plans (1 vs 2 vs 3)
Tools: Superwall (no-deploy paywall tests, recommended), RevenueCat Experiments, Adapty A/B, native via remote config (e.g. Firebase Remote Config + own logic).
Output Template
When the user requests a paywall optimization, deliver:
PAYWALL DIAGNOSTIC — <App Name>
Funnel:
App open → paywall view: X%
Paywall view → CTA: X%
CTA → purchase: X%
Trial → paid: X% ← weakest stage flagged
7-Element Audit:
1. Headline: X/5 — <note>
2. Value props: X/5 — <note>
3. Social proof: X/5 — <note>
4. Plan picker: X/5 — <note>
5. Price anchor: X/5 — <note>
6. Trust: X/5 — <note>
7. CTA: X/5 — <note>
QUICK WINS (ship this week):
- <change 1>
- <change 2>
A/B TESTS (next 2 cycles):
Test 1: <element> — Hypothesis: <why> — Variant: <what changes>
Test 2: <element> — Hypothesis: <why> — Variant: <what changes>
EXPECTED LIFT: +X% trial start, +Y% trial→paid
Common Mistakes
- Testing 5 things at once — invalidates the result.
- Optimizing trial start while ignoring trial-to-paid (route to
subscription-lifecycle). - Killing tests at p=0.05 without sample size — false positives in low-traffic apps.
- Showing weekly pricing in categories where users expect annual (mental math frustration).
- No restore-purchase button — guaranteed Apple rejection.
- Hiding "cancel anytime" — kills conversion among trial-skeptics.
Cross-Skill Handoffs
- Trial-to-paid is the bottleneck →
subscription-lifecycle - Pricing model itself is wrong (subscription vs IAP vs one-time) →
monetization-strategy - Paywall fires too early/late in onboarding →
onboarding-optimization - Want to A/B test the App Store page that drives paywall traffic →
ab-test-store-listing
FAQ
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 nurture, dunning, and churn, see subscription-lifecycle. For where in the onboarding the paywall fires, see onboarding-optimization.
How do I install paywall-optimization?
Run npx skills add https://github.com/appeeky/aso-skills --skill paywall-optimization in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/paywall-optimization/ (personal) or .claude/skills/paywall-optimization/ (project).
Which AI agents can use paywall-optimization?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is paywall-optimization safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains paywall-optimization?
It is published by appeeky in appeeky/aso-skills. It has 1,931 recorded installs.
More from appeeky/aso-skills
aso-audit
appeeky/aso-skills
When the user wants a full ASO health audit, review their App Store listing quality, or diagnose why their app isn't ranking. Also use when the user mentions "ASO audit", "ASO score", "why am I not ranking", "listing review", or "optimize my app store page". For keyword-specific research, see keyword-research. For metadata writing, see metadata-optimization.
keyword-research
appeeky/aso-skills
When the user wants to discover, evaluate, or prioritize App Store keywords. Also use when the user mentions "keyword research", "find keywords", "search volume", "keyword difficulty", "keyword ideas", or "what keywords should I target". For implementing keywords into metadata, see metadata-optimization. For auditing current keyword performance, see aso-audit.
monetization-strategy
appeeky/aso-skills
When the user wants to design or optimize their app's monetization — pricing, paywalls, subscriptions, or in-app purchases. Also use when the user mentions "pricing", "paywall", "subscription", "IAP", "how to monetize", "revenue optimization", "free trial", or "conversion to paid". For retention impact, see retention-optimization. For competitive pricing, see competitor-analysis.
metadata-optimization
appeeky/aso-skills
When the user wants to optimize App Store metadata — title, subtitle, keyword field, or description. Also use when the user mentions "optimize my title", "ASO metadata", "keyword field", "character limits", "app description", or "write my subtitle". For keyword discovery, see keyword-research. For full ASO audits, see aso-audit.
competitor-analysis
appeeky/aso-skills
When the user wants to analyze competitors' App Store strategy, find keyword gaps, or understand competitive positioning. Also use when the user mentions "competitor analysis", "competitive research", "keyword gap", "what are my competitors doing", or "compare my app to". For keyword-specific research, see keyword-research. For metadata writing, see metadata-optimization.
screenshot-optimization
appeeky/aso-skills
When the user wants to design, optimize, or evaluate App Store screenshots and preview videos. Also use when the user mentions "screenshots", "app preview", "product page design", "screenshot design", "creative assets", or "what should my screenshots show". For A/B testing screenshots, see ab-test-store-listing. For full ASO audit, see aso-audit.
Popular testing & qa skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
grilling
mattpocock/skills
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
migrate-to-shoehorn
mattpocock/skills
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
run-train
lllllllama/rigorpilot-skills
Rigor Train skill for deep learning research repositories. Use when a documented or selected training command should be run conservatively for startup verification, short-run verification, full kickoff, or resume, with command, config, seed, log, checkpoint, status, and metric evidence written to standardized trainoutputs/. Do not use for environment setup, exploratory sweeps, speculative idea implementation, or end-to-end orchestration.
test-driven-development
obra/superpowers
Use when implementing any feature or bugfix, before writing implementation code
finishing-a-development-branch
obra/superpowers
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work