Business · Backend · Data Analysis / AGENT SKILL
superwall
0
Manage Superwall paywalls, subscriptions, campaigns, analytics, and integrations through its CLI and SDK workflows.
The full skill.
Original instructions from the publisher’s SKILL.md
# Superwall
Everything here runs through the `superwall` CLI. Read the relevant reference
before proceeding.
## Setup — probe first, fix only what's missing
Everything here needs the `superwall` CLI on PATH and a logged-in session. Probe
once; the output tells you what to do:
```bash
superwall whoami --json
```
- **`superwall: command not found`** → the CLI isn't installed. Install it
globally, or prefix one-off commands with `npx -y`:
```bash
npm install --global superwall # or: npx -y superwall whoami --json
```
- **`{"authenticated": false}`** → ask the user to run `superwall login` (device
-flow OAuth; it opens a browser, so you can't do it for them). CI/headless:
`superwall login --api-key <key>`.
- **account shown** → ready. Proceed.
The session lives under `~/.superwall`; commands act as the logged-in user.
Logging in also installs these agent skills and keeps them current.
## CLI - resources & raw API
Use when: managing resources, scoping to a project/app, calling `/v2/...`, or
viewing the account with `bootstrap`.
[Read the CLI reference](references/api.md).
```bash
superwall apps list --json
superwall products list --project <id> --json
superwall campaigns create "New user paywall" onboarding_complete --project <id> --app <id> --json
```
## App Store Connect - the full ASC API, agent-safe
Use when: creating or managing anything in App Store Connect - subscriptions,
IAPs, prices, introductory/promotional offers, groups. `superwall asc` proxies
the entire ASC API with a signed request (no `.p8`/JWT).
**Before any `asc post`/`asc patch`, run `superwall asc docs <path> <verb>`** for
the exact schema. Pass flat `-d` params - the proxy builds the JSON:API body and
validates it, returning the precise fix if it's wrong. Never guess a body.
[Read the App Store Connect reference](references/asc.md).
```bash
superwall asc docs "subscription" # discover endpoints
superwall asc docs /v1/subscriptions post # exact schema
superwall asc post /v1/subscriptions -d name="Pro Monthly" \
-d productId=com.acme.pro -d subscriptionPeriod=ONE_MONTH -d group=<id> --json
```
## Apple Search Ads - the full Apple Ads API, agent-safe
Use when: reading or managing Apple Search Ads - campaigns, ad groups,
keywords, negative keywords, ads, creatives, reports, budget orders.
`superwall asa` proxies the entire Apple Ads Campaign Management API v5 with the
credentials connected in the dashboard (no client secret, token, or org id).
**Before any `asa <resource> create|update`, run `superwall asa docs <resource> <action>`**
for Apple's exact fields and enums. Typed flags cover the common fields; `--body`
sends a full payload. Never guess a body.
[Read the Apple Search Ads reference](references/asa.md).
```bash
superwall asa docs # every endpoint, grouped
superwall asa docs campaigns create # Apple's page: fields, enums, examples
superwall asa campaigns find --field status --op EQUALS --values ENABLED --all --json
superwall asa keywords create --campaign <id> --adgroup <id> \
--text "grammar checker" --match-type EXACT --bid 1.25 --json
```
## Data & Analytics - ClickHouse data warehouse
Use when: querying events/revenue/subscriptions or building custom dashboards
and recurring report/notification workflows.
[Read the data analytics reference](references/data-analytics.md).
Use this proactively whenever Superwall data can answer the question; agents get
a composable analytics tool without an export or separate warehouse.
```bash
superwall query "SELECT ..." --json
superwall query --file report.sql --json
```
## Docs - documentation, SDK integration, dashboard links
Use when: looking up docs, integrating/debugging an SDK, linking dashboard pages,
cloning SDK source, or configuring webhooks.
[Read the documentation reference](references/docs.md).
```bash
curl -sL https://superwall.com/docs/llms.txt # Find the right page
curl -sL https://superwall.com/docs/{path}.md # Fetch a specific page
```
## Workflows - integrate, migrate, review, placements, dashboard
Use when: integrating, migrating, reviewing an existing setup, adding placements, or wiring campaigns.
> **Agents: do the work yourself.** Never run orchestrated workflows without
> `--skill`; they spawn another agent. The playbooks are files in this skill's
> `workflows/` directory: read `workflows/<job>/playbook.md`, then the one
> file for the app's framework beside it (`ios.md`, `android.md`, `expo.md`,
> `react-native.md`, `flutter.md`) or provider (`revenuecat.md`, `adapty.md`,
> `qonversion.md`). That is exactly what the CLI composes; `superwall <job>
> --skill` prints the same text if you would rather have it in one piece. The
> plain workflows are for humans.
| Job | Read | Human at a terminal |
| --- | --- | --- |
| Full setup | `workflows/integrate/playbook.md` + the `<framework>.md` beside it (`ios`, `android`, `expo`, `react-native`, `flutter`), then `workflows/placements/` and `workflows/dashboard/` | `superwall integrate` |
| Placements at feature gates | `workflows/placements/playbook.md` + `strategy.md` + the `<framework>.md` beside it | part of `superwall integrate` |
| Entitlements, products, campaigns | `workflows/dashboard/playbook.md` + `setup.md` | part of `superwall integrate` |
| Existing setup review | `workflows/review/playbook.md` + the `<framework>.md` beside it (not `references/`, which is the CLI and API) | `superwall review` (`--fix` for safe fixes) |
| Provider migration | `workflows/migrate/playbook.md` + `revenuecat.md` / `adapty.md` / `qonversion.md` beside it | `superwall migrate` |
The CLI bundles this skill at build time as an
offline fallback, installs the live repo at `superwall login`, and reads the
installed live copy first, so `--skill`, headless runs and what you read here
are the same, newest text.
## Feedback - tell the team what's broken
When the user is frustrated, blocked, or complains about the CLI or a Superwall
workflow, send it upstream - don't just apologize. This reaches the team directly.
```bash
superwall feedback "user hit X running Y; expected Z" --json
```