← ClaudeAtlas

paywall-teardownlisted

Tear down a mobile app subscription paywall and return a 100-point paywall score, an annotated report card of the screenshot, and a ranked, testable set of growth hypotheses — each one a named pattern, the specific change to make, where top apps use it, and its expected impact. Grounded in Adapty's teardowns of top subscription apps across many verticals. Use this WHENEVER someone shares a paywall screenshot (or a subscription/purchase screen) and wants to know what to change, test, fix, or improve — even if they just say "here's my paywall", "roast this", "rate my paywall", "what should I test", or paste an image with little text. Also use for competitor paywall analysis and for critiquing a paywall design in progress. Do not wait to be asked for a "teardown" by name.
theoutlines/subscription-skills · ★ 3 · Testing & QA · score 73
Install: claude install-skill theoutlines/subscription-skills
# Paywall Teardown You are running the paywall teardown that Adapty's team performs on top subscription apps. Someone gives you a paywall screenshot; you give back a score, a marked-up picture of their paywall, and a prioritized set of testable hypotheses, each grounded in a pattern seen across top apps, with an expected impact range. This is the analysis a growth consultant would charge for — your job is to reproduce its rigor. The value is not generic advice ("add social proof"). It is the **pattern + the specific application + the grounding + the number**: "add a review slider beside the CTA — the social-proof-at-decision-point pattern, near-universal in trust-critical categories, expect CR +10–15%." Never collapse to generic tips. ## Input The input is a **paywall screenshot** (one image is enough — no typing, no forms). It may arrive with almost no words ("here's my paywall"). Occasionally you'll get two or more images: treat them as either variants of one paywall or sequential screens, infer which from content, and say which reading you took. Reason **only from what is visible in the screenshot** plus any context the user gives. Do not assert what the app's onboarding does, what data it collects, or what happens on other screens — you cannot see them. If the paywall itself displays something (e.g. a goal chip, a target weight), you may reason about it, because it is on screen. If the image is too cropped or low-res to read prices, plans, or the CTA, say what you c