Paywall Teardown
Use when someone shares a mobile subscription or purchase screen and wants to know what to change, fix, test or improve — "here's my paywall", "roast this", "what should I test", a competitor screenshot, a design in progress, or an image with almost no text. Also use whenever YOU are the one designing or generating a paywall screen and were given no design reference to follow — no reference image, no existing screen to copy, no layout spec — as in "make me a paywall", "make one that converts", "will this convert?", "is this any good?"; this library is the reference in that case, and it evaluat
Install
/plugin marketplace add adaptyteam/adapty-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add adaptyteam/adapty-skills --skill paywall-teardowngit clone --depth 1 https://github.com/adaptyteam/adapty-skills.git /tmp/adapty-skills
mkdir -p ~/.claude/skills
cp -r /tmp/adapty-skills/plugin/skills/paywall-teardown ~/.claude/skills/paywall-teardownPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Paywall Teardown
You are running the paywall teardown that Adapty's team performs on top subscription apps. You
are given a paywall — a screenshot, a render, or a config — and you give back 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.
## How you sound
Every line the user reads, the fixed blocks included:
- **A growth colleague who has seen many paywalls.** Specific to this screen, honest when it is
already good, never padded to look thorough.
- **"I" for what you do, "you" for what they do.** Lead with the read; end on one next step. No
opener, no recap of what they sent, no "let me know if…".
- **Bold at most one thing per paragraph.** Table rows need no bold.
- **Raw values only when the user will see them elsewhere** — a button label, a price, a menu
name. Never element ids or tool names.
- **Full, clickable links.** A docs page is read as its `.md` URL; the user gets the same URL without `.md`.Details
- Skill name
paywall-teardown- Repository
- adaptyteam/adapty-skills
- Path
plugin/skills/paywall-teardown/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
FAQ
What does the Paywall Teardown skill do?
Use when someone shares a mobile subscription or purchase screen and wants to know what to change, fix, test or improve — "here's my paywall", "roast this", "what should I test", a competitor screenshot, a design in progress, or an image with almost no text. Also use whenever YOU are the one designing or generating a paywall screen and were given no design reference to follow — no reference image, no existing screen to copy, no layout spec — as in "make me a paywall", "make one that converts", "will this convert?", "is this any good?"; this library is the reference in that case, and it evaluat
How do I install the Paywall Teardown skill?
Claude Code plugin: /plugin marketplace add adaptyteam/adapty-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Paywall Teardown popular?
It lives in adaptyteam/adapty-skills, which has 9 GitHub stars and 2 forks.
Related skills
Ab Tests
9adaptyteam/adapty-skills
Use when a user wants to run, check or end a regular A/B test of paywalls or flows through the Adapty CLI — plan it, create the draft, change it, start it, read its results, stop it with a winner, replace a running test with a changed one, archive it, or see which tests an app has. Triggers on "run an A/B test of these two paywalls", "test my new flow against the old one", "split traffic 50/50", "start the test", "stop the test, B wins", "end this experiment", "change the weights of my test", "which tests are running", "archive the old tests", "should I stop this test", "how did the test go",
Adapty Attribution
9adaptyteam/adapty-skills
Use when someone asks how their ad campaigns, channels, ad sets, ads, countries or keywords are performing in Adapty Attribution — ROAS, payback, CPI, cost per trial, installs, trial-to-paid, refunds, predicted revenue — which channel or campaign to scale or cut, where to move budget, why installs dropped, why Meta, TikTok or Google report different numbers than Adapty, or how to set up Adapty Attribution with Meta, TikTok, Google Ads, custom tracking links or a web funnel.
Adapty Docs
9adaptyteam/adapty-skills
Use when an Adapty question has no page already linked in the skill you are holding — how a product or dashboard feature behaves, what a setting does, a limit, store connections, Flow Builder, the Developer CLI, the server-side API, or an SDK method on any platform. Also use when you need a docs page and have no URL for it, or when a docs URL you tried returned 404. Not for making a change to an app's Adapty setup — connecting a store, or creating products, access levels or placements — which `adapty-integration` carries out through the Adapty CLI.
Purchase Testing
9adaptyteam/adapty-skills
Use when a sandbox or test purchase does not work, or when someone is about to make their first one. Triggers on "my sandbox purchase isn't going through", "the purchase sheet doesn't appear", "I bought it but nothing happened", "the paywall is blank on my phone", "no event in the Adapty dashboard", "how do I test purchases", "test on a real device", "restore doesn't work". Diagnoses first, so nobody is sent back to a console before the cheap checks have run. Complements `adapty-integration`, which owns writing the code and connecting the stores.
Mxl Driver Psi4 Rttddft
9TaoELi/MaxwellLink
This skill should be used when users want to run the Psi4 RT-TDDFT driver (rttddft) with MaxwellLink and need required inputs, parameters, and socket/embedded invocation patterns.
Idea Autopsy
5auracura/idea-autopsy
Stress-test a business idea — especially one an AI suggested — before anyone builds it. Use when the user says "autopsy this", "is this a business or bullshit", "test this idea", or pastes a startup/side-hustle idea and wants to know if it's real. Returns one of four verdicts: BUSINESS, BUSINESS WRONG OWNER (real idea, wrong constraints — says which), BULLETIN (it's really just content or information), or BULLSHIT, plus the smallest test that would prove it wrong. Built from a four-hour session in which an LLM pitched twelve businesses and eleven died.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.