Onboarding Teardown
Use when someone wants to improve, fix, test or critique a mobile app's onboarding — "here's my onboarding", "roast my flow", "why do users drop off before the paywall", a competitor's signup flow, a welcome or activation flow, a quiz, or a flow described in one sentence. Also use whenever YOU are the one designing or generating an onboarding sequence and were given no design reference to follow — no reference screens, no existing flow to copy, no spelled-out sequence — as in "build me an onboarding", "add a quiz before the paywall", "make a flow that converts"; this library is the reference i
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 onboarding-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/onboarding-teardown ~/.claude/skills/onboarding-teardownPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Onboarding Teardown
You are running the onboarding teardown that Adapty's team performs on top subscription apps.
Someone describes their flow (or sends screens, a render, or the flow config); you give back a
prioritized set of testable hypotheses, each grounded in a pattern seen across top apps, with an
expected impact range.
The value is not generic advice ("add personalization"). It is the **pattern + the specific
application + the grounding + the number**: "your loader promises a personalized plan and then
hands users to the paywall — add the plan-summary payoff between them; near-universal in wellness,
expect CR +10–20%." Never collapse to generic tips.
**Treat onboarding and the paywall as one funnel.** The strongest findings live at the seam: a goal
captured in onboarding that the paywall never mentions, a loader that promises personalization the
next screen doesn't deliver. A flow teardown that stops at the paywall's edge misses the most
valuable half. The paywall *screen's* own execution — plan cards, price display, CTA, proof
placement — belongs to `paywall-teardown`; see [Scope](#scope).
## How you sound
Every line the user reads, the fixed blocks included:
- **A growth colleague who has seen many onboardings.** Specific to this flow, 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-back; end on one next step.Details
- Skill name
onboarding-teardown- Repository
- adaptyteam/adapty-skills
- Path
plugin/skills/onboarding-teardown/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
FAQ
What does the Onboarding Teardown skill do?
Use when someone wants to improve, fix, test or critique a mobile app's onboarding — "here's my onboarding", "roast my flow", "why do users drop off before the paywall", a competitor's signup flow, a welcome or activation flow, a quiz, or a flow described in one sentence. Also use whenever YOU are the one designing or generating an onboarding sequence and were given no design reference to follow — no reference screens, no existing flow to copy, no spelled-out sequence — as in "build me an onboarding", "add a quiz before the paywall", "make a flow that converts"; this library is the reference i
How do I install the Onboarding 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 Onboarding 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.
Noise Emulate
9pasqal-io/agent-marketplace
Emulate a neutral-atom Pulser sequence's time evolution under the target Rydberg device's live noise model, producing noiseless and noisy trajectory curves with a quantile envelope. Asks where to run — this machine, a GPU cluster, or Pasqal Cloud emulators. Use this to study how noise shapes a signal over time; use validate-emu to decide whether an experiment is worth submitting. Triggered by phrases like "run a noise emulation of this sequence", "emu-mps with noise", "noise envelope".
Oldhand Learn
9berwinsingh/oldhand
Captures the durable, non-obvious lessons from a task (diagnosis recipes, API and platform quirks, environment traps, failed experiments with their numbers, decisions and their why, rollback points, user corrections) into the project's existing agent instruction file or the host's memory system, each note dated with why and how to apply, and corrects or deletes notes the task proved wrong. Use when the user says "write down what we learned on this task", "save the lessons from this task", "capture this task's lessons for next time", or at the end of the oldhand chain. Not for documenting code
Reduce Token
5sham-jadhav03/Claude_Skills
Activates compact, high-density response mode when the user types `/reduceToken` or any variant like `/reduceToken 500` or `/reduceToken study`. Apply this skill immediately and hold it for the entire session. Trigger on: `/reduceToken`, "token constraint", "reduce tokens", "compact mode", "token budget reminder", or when the user pastes a disclaimer about token limits. Do not wait to be asked twice — activate on first signal and confirm with a single line.
Browse the most popular Claude skills, all learning & education skills, or write your own with the skills generator.