SkillAgentSearch skills...

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

Install / Use

npx skills add appeeky/aso-skills --skill paywall-optimization

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

86/100

Supported Platforms

Universal

Our assessment of paywall-optimization

paywall-optimization scores 86/100 on our quality scale, 2387th of 4,714 Development & Engineering skills we index.

Its SKILL.md is 6.9 KB long, well organised into 10 sections with 1 code example: a thorough specification that gives an agent plenty to work with.

With 2,095 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
29/30
Structure
17/20
Description
15/15
Adoption
14/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 3 months ago, so paywall-optimization is actively maintained.
  • Our last check on 2026-10-31 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

paywall-optimization compared with similar skills

All 4 of these similar skills score higher than paywall-optimization; compare them before choosing.

SkillScoreStarsUpdatedFormat
paywall-optimization (this skill)by appeeky862.1k3mo agoSKILL.md
taste-skillby Leonxlnx100117.8k9d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.3ktodayCLAUDE.md
claude-howtoby luongnv8910047.4k3d agoCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10040.0k8d agoCLAUDE.md

Frequently asked questions

How do I install paywall-optimization?
Run npx skills add appeeky/aso-skills --skill paywall-optimization. The install tabs above show the steps for each supported agent.
Which AI agents does paywall-optimization work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is paywall-optimization safe to use?
It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is paywall-optimization still maintained?
The repository was last updated about 3 months ago, so paywall-optimization is actively maintained.

name: paywall-optimization description: 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. metadata: version: 1.0.0

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/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):

  1. Headline — does it state the outcome (not the feature)? "Unlock unlimited workouts" beats "Pro Plan".
  2. Value props — 3–5 max, benefit-led, scannable in <3 seconds.
  3. Social proof — rating, review count, user count, or named testimonials. Required above the fold.
  4. Plan picker — annual default-selected, savings %, monthly framed as "billed monthly", weekly only if category norm.
  5. Price anchoring — annual shown as monthly equivalent ("$3.33/mo, billed annually") + total ("$39.99/yr").
  6. Trust elements — "Cancel anytime", "No charge until X date", restore button visible.
  7. 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):

  1. Headline copy (highest leverage)
  2. Trial offer (3-day vs 7-day vs no trial)
  3. Plan default (annual vs monthly pre-selected)
  4. CTA copy ("Start free trial" vs "Try free for 7 days" vs "Continue")
  5. Social proof element (rating vs user count vs testimonial)
  6. Visual style (clean vs bold vs photo background)
  7. 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

Related Skills

View on GitHub
GitHub Stars2.1k
CategoryDevelopment
Updated2mo ago
Forks126

Languages

MDX

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions