Agent skill

Paywall Optimization

by appeeky in appeeky/aso-skills

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.

MITAuto-check passedMarketing & SEO

Install Paywall Optimization

skills CLI
$ npx skills add appeeky/aso-skills --skill paywall-optimization -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install appeeky/aso-skills paywall-optimization --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/appeeky/aso-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/paywall-optimization .claude/skills/paywall-optimization && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
paywall-optimization
GitHub stars
2.1k
Token cost
~1.8k tokens
SKILL.md length
732 words
Files
1
Skills in repo
39
Repo updated
First seen
Licence
MIT

At a glance

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.

  • Works in 5 steps: Check for app-marketing-context.md —… → Ask for the App ID and paywall framework… → Ask for current paywall view → trial… → …
  • Wants to design
  • SKILL.md covers Initial Assessment, Diagnose Before You Redesign, The 7-Element Paywall Audit and Paywall Placement Strategy, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Paywall Optimization is an agent skill from appeeky/aso-skills. 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…

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Marketing & SEO, covering A/B testing and Pricing strategy. It works with RevenueCat. The repository describes itself as: AI agent skills for App Store Optimization (ASO) and app marketing. Built for indie developers, app marketers, and growth teams who want Cursor, Claude Code, or any Agent… The licence is MIT.

When your agent uses it

  • Wants to design
  • Optimize their apps paywall — layout
  • Pricing display
  • Hard vs soft paywall

Example prompts

  • “paywall”
  • “paywall design”
  • “paywall conversion”
  • “/paywall-optimization”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  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?

What it can do on your machine

Read from SKILL.md and the folder at commit 3919d7c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Paywall Optimization loads about 1.8k tokens when it runs. Until then it costs about 187 tokens; SKILL.md has 732 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~187
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from appeeky/aso-skills at commit 3919d7c, republished under its MIT licence (© appeeky). 732 words, ~1,758 tokens.

Download SKILL.mdSave it as .claude/skills/paywall-optimization/SKILL.md (or your agent's skills folder).
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:

StageHealthy RangeRed Flag
App open → paywall view60–95% (depends on placement)<50% (paywall buried)
Paywall view → CTA tap25–45%<15% (copy/offer weak)
CTA tap → purchase confirm70–90%<50% (StoreKit friction or price shock)
Trial start → paid conversion25–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

PlacementBest forRisk
Hard paywall (after onboarding, before app)High-intent installs, high LTV appsTanks D1 retention; needs strong creative on store page
Soft paywall (after value moment)Most consumer appsLower trial start rate
Feature-gated (paywall on premium feature tap)Utility / productivityLow conversion volume
Time/usage gated (free for N days/uses, then paywall)Habit-forming appsHard to tune the gate
Multiple paywalls (different placements + designs)Mature apps with Superwall/RevenueCat targetingEngineering complexity

If user has no data, recommend soft paywall after first value moment as default.

Show full SKILL.md (308 more words)Show less

Pricing Display Patterns

The display matters more than the price itself. Test these:

PatternWhen to use
Annual default + savings % ("Save 67%")Most apps — anchors high, increases LTV
Free trial CTA primary, plans secondaryTrial-led products
Single plan, single priceSimple utilities; reduces choice paralysis
3-tier (Basic / Pro / Pro+)Apps with feature differentiation; middle is anchor
Lifetime as decoyReframes subscription as "the cheap option"
Localized currency + priceRequired 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 conversionMin 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

© appeeky, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/paywall-optimization of appeeky/aso-skills.

Open the folder on GitHubat commit 3919d7c

Compare with similar skills

Paywall Optimization next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Paywall Optimization compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Paywall Optimization this skillappeeky/aso-skills2.1k—~1.8kAutomated safety check: PassMIT
Conversion Rate Optimizationmanojbajaj95/claude-gtm-plugin104—~1.2kAutomated safety check: PassMIT
Paywall Optimizervibeeval/vibecosystem531—~3.2kAutomated safety check: PassMIT
Pricing Strategistnicepkg/ai-workflow285—~3.9kAutomated safety check: PassMIT
AnalyticsNexus-JPF/note-companion8696 repos~2.2kAutomated safety check: PassMIT
Ab Test Setupfreekmurze/dotfiles1k15 repos~1.8kAutomated safety check: PassNone

Similar skills

  • Conversion Rate Optimization

    manojbajaj95/claude-gtm-plugin

    Conversion rate optimization for marketing pages and lead-capture forms.

    104 GitHub stars~1.2k tokensUpdated 19 days ago
    Marketing & SEOAuto-check passed
  • Paywall Optimizer

    vibeeval/vibecosystem

    AI-powered paywall optimizasyon. An agent skill from vibeeval/vibecosystem.

    531 GitHub stars~3.2k tokensUpdated 2 mo ago
    Marketing & SEOAuto-check passed
  • Pricing Strategist

    nicepkg/ai-workflow

    Design and optimize pricing strategies for SaaS products including tiering, packaging, value metrics, and experimentation.

    285 GitHub stars~3.9k tokensUpdated 8 mo ago
    Sales & SupportAuto-check passed
  • Analytics

    Nexus-JPF/note-companion

    When the user wants to set up, improve, or audit analytics tracking and measurement.

    869 GitHub starsUsed in 6 repos~2.2k tokens
    Marketing & SEOAuto-check passed
  • Ab Test Setup

    freekmurze/dotfiles

    When the user wants to plan, design, or implement an A/B test or experiment.

    1k GitHub starsUsed in 15 repos~1.8k tokens
    Marketing & SEOAuto-check passed
  • Ad Test Designer

    aaron-he-zhu/aaron-marketing-skills

    A skill your agent uses when the user asks to "design an A/B test", "set up a creative/landing test", "run an incrementality test", or "is this result statistically and practically material?"…

    2.9k GitHub starsUsed in 2 repos~2.8k tokens
    Marketing & SEOAuto-check passed

More from appeeky/aso-skills

All 39 skills in this repo
  • Ab Test Store Listing

    appeeky/aso-skills

    When the user wants to A/B test App Store product page elements to improve conversion rate.

    2.1k GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed
  • Android Aso

    appeeky/aso-skills

    When the user wants to optimize their Google Play Store listing — title, short description, full description, keywords, ratings, or Play Store-specific features.

    2.1k GitHub stars~1.7k tokensUpdated yesterday
    Auto-check passed
  • App Analytics

    appeeky/aso-skills

    When the user wants to set up, interpret, or improve their app analytics and tracking.

    2.1k GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed
  • App Clips

    appeeky/aso-skills

    When the user wants to implement, optimize, or use App Clips for app discovery and conversion.

    2.1k GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed
  • App Icon Optimization

    appeeky/aso-skills

    When the user wants to design, test, or improve their app icon to increase tap-through rate and conversions in App Store search and browse.

    2.1k GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed
  • App Marketing Context

    appeeky/aso-skills

    When the user wants to create or update their app marketing context document.

    2.1k GitHub stars~910 tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Paywall Optimization

What does Paywall Optimization 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. Paywall Optimization is an agent skill from appeeky/aso-skills. 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.

When should I use Paywall Optimization?

Paywall Optimization fits situations like: wants to design; optimize their apps paywall — layout; pricing display; hard vs soft paywall.

How do I install Paywall Optimization in Claude Code?

Run `npx skills add appeeky/aso-skills --skill paywall-optimization -a claude-code`. Or copy the skill folder (skills/paywall-optimization in appeeky/aso-skills) into .claude/skills/paywall-optimization in your project. Claude Code loads it when a task matches its description.

How do I install Paywall Optimization in Codex?

Run `npx skills add appeeky/aso-skills --skill paywall-optimization -a codex`. Or copy the skill folder (skills/paywall-optimization in appeeky/aso-skills) into .agents/skills/paywall-optimization in your project. Codex loads it when a task matches its description.

Can I use Paywall Optimization in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add appeeky/aso-skills --skill paywall-optimization -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/paywall-optimization, .gemini/skills/paywall-optimization, .github/skills/paywall-optimization and .opencode/skills/paywall-optimization in your project.

What does Paywall Optimization need to run?

SKILL.md names no scripts, command-line tools or credentials: Paywall Optimization is instructions for the agent only.

Does Paywall Optimization access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Paywall Optimization safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Paywall Optimization use?

Paywall Optimization is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Paywall Optimization use?

About 1.8k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Paywall Optimization?

Skills that share tags, products or a category with Paywall Optimization: Conversion Rate Optimization (manojbajaj95/claude-gtm-plugin, 104 stars), Paywall Optimizer (vibeeval/vibecosystem, 531 stars), Pricing Strategist (nicepkg/ai-workflow, 285 stars) and Analytics (Nexus-JPF/note-companion, 869 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Paywall Optimization?

appeeky (a GitHub organization) maintains it in appeeky/aso-skills, which has 2,149 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on October 6, 2026.

Source: appeeky/aso-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.