Purchase Testing
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.
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 purchase-testinggit clone --depth 1 https://github.com/adaptyteam/adapty-skills.git /tmp/adapty-skills
mkdir -p ~/.claude/skills
cp -r /tmp/adapty-skills/plugin/skills/purchase-testing ~/.claude/skills/purchase-testingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# purchase-testing
## What this answers
**Why doesn't this purchase work — and what do I do about it?** Also the forward case:
someone whose code builds and whose stores are connected, about to run their first
sandbox purchase — often straight after `adapty-integration` hands over.
The value is the order. A purchase failure can live in five different places, and the
expensive ones involve a human clicking through a store console. So this skill checks
everything it can reach itself, first, and only then asks anyone to open a browser.
**This skill does not connect stores and does not write code.** Creating store products,
uploading an App Store In-App Purchase Key, setting up a Google Play service account and
RTDN, and writing the SDK calls all belong to `adapty-integration`. When a check here
lands on one of those, offer the outcome ("I can add the code that closes the paywall
after a purchase. Want me to?") and invoke `adapty-integration` on a yes.
## How you sound
Every message, not only the fixed blocks:
- **A patient colleague who knows in-app purchases.** The user is often testing a
purchase for the first time. Assume they may know nothing about sandbox accounts or
store consoles; when they ask, answer plainly and use their own app as the example.
Friendly through patience, never through filler. Someone chasing a broken purchase is
already frustrated, so the next action comes before any explanation.Details
- Skill name
purchase-testing- Repository
- adaptyteam/adapty-skills
- Path
plugin/skills/purchase-testing/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
FAQ
What does the Purchase Testing skill do?
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.
How do I install the Purchase Testing 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 Purchase Testing 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.
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.
Paywall Teardown
9adaptyteam/adapty-skills
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
Inversion Engine
5unstatusthequo/inversion-engine
Structured inversion analysis for strategic decisions, plans, and initiatives. Systematically maps every path to failure so the path to success becomes obvious by elimination. Produces scored risk registers, countermeasure plans, and decision briefs -- not just narrative brainstorming. Use this skill whenever the user asks to stress test a plan, run a pre-mortem, do failure analysis, red team a strategy, audit assumptions, map risks, run inversion on a decision, identify what could go wrong, pressure test an idea, do a Munger-style analysis, or any variation of "help me figure out how this fai
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.