adaptyteam
- 12 skills
- 0 followers
- 14 hours ago last updated
- ▌ Adapty CLI · adaptyteam bundleUse when setting up or managing Adapty in-app subscriptions, paywalls, or placements via CLI.
- ▌ Apple Ads · adaptyteam bundleUse when operating a connected Apple Ads account through the Adapty CLI — weekly check-ins, cohort and keyword bid reviews, competitor keyword opportunities from Market Intelligence, search-term harvesting, negative-keyword mining, CPP routing, bids, budgets, keywords, campaigns, and rule automations. Requires the adapty CLI and an Adapty account. Use apple-ads-audit for read-only account health or live structure diagnostics, and apple-ads-strategy for planning without an account.
- ▌ Apple Ads Audit · adaptyteam bundleUse for read-only diagnostics of a connected Apple Ads account: account health, live campaign and ad-group structure, traffic ownership, duplicate exact keywords, missing cross-negatives, serving problems, spend without results, or a simple same-window comparison of Apple total installs and Adapty installs. Triggers on "audit my Apple Ads account", "what is broken", "which campaigns need attention", "is my live structure correct", or "why are Apple and Adapty installs different". Never use it to design a new account, run a weekly review, or make changes.
- ▌ Adapty CLI Setup · adaptyteam<!-- GENERATED — synced from adaptyteam/adapty-cli@v0.8.3 (docs/agent/skills/adapty-cli-setup/SKILL.md). Do not edit here.
- ▌ Apple Ads Strategy · adaptyteam bundleUse when planning Apple Search Ads before there is anything to read — designing an account structure, choosing which campaigns and ad groups to create, building a keyword taxonomy and starting negative list, sizing a starting budget, or deciding whether Apple Ads fits an app at all. Triggers on "how do I launch Apple Search Ads", "what campaigns should I create", "which keywords should I target", "structure my ASA account", or any Apple Ads question about an app that is not connected yet. Needs no account, no CLI and no subscription.
- ▌
- ▌ Ads Manager · adaptyteam bundleUse when managing Apple Search Ads through the Adapty CLI — reading campaign, ad group, keyword or ad performance, changing bids or budgets, adding or pausing keywords, launching or pausing a campaign, creating a whole campaign structure in bulk from JSON or an Apple Ads template, harvesting search terms, or setting up rule-based ad automations.
- ▌ Flow Generator · adaptyteam bundleUse when a user wants to change an Adapty flow by editing its builder config JSON — add a locale, translate a paywall or onboarding, rewrite copy, add/remove/reorder screens, add tabs or plan pickers, wire quiz branching, or build an onboarding sequence — and also once a flow is published, to point a placement at it so an app can fetch it. Triggers on "edit my flow config", "add a language to my paywall", "translate my onboarding", "remove a screen from the flow", "add tabs to my paywall", "build me a paywall like this", "build me an onboarding", a supplied Adapty flow config, and on "publish my flow", "I published my flow", "attach my flow to a placement", "create a placement for this flow", "my flow does not show up in the app".
- ▌ Paywall Teardown · adaptyteam bundleUse 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 evaluates and corrects the screen you produce. Also use when reviewing a paywall render or flow config produced by the flow-generator skill. Do not wait to be asked for a "teardown" by name.
- ▌ Adapty Integration · adaptyteam bundleUse when a user wants to integrate Adapty SDK into a mobile app, set up in-app purchases with Adapty, add a paywall to their app, or move to Adapty from another purchase system. Triggers on "integrate Adapty", "add Adapty to my app", "set up subscriptions", "add a paywall", "migrate from RevenueCat", "replace RevenueCat with Adapty", "move off Superwall", or similar.
- ▌ Migrate Placements · adaptyteam bundleUse when someone wants to move an app from paywall placements to Flow Builder flows — "migrate my placements to flows", "switch my paywalls to flows", "we have 40 placements on paywalls and want flows", or a bulk request across many apps or paywalls. Creates NEW flow placements alongside the existing paywall ones and hands back the old→new mapping plus the SDK call change. Never converts a placement in place — the backend refuses a type change. Complements `flow-generator` (which builds and publishes flows) and `adapty-integration` (which owns the app-side call sites).
- ▌ Onboarding Teardown · adaptyteam bundleUse 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 in that case, and it evaluates and corrects the flow you produce. Also use when reviewing an onboarding flow config or a set of `flows config preview` renders produced by the flow-generator skill. Do not wait to be asked for a "teardown" by name.