Skip to content
AI Primer
📦 Product

superwall

superwallby superwall6 months ago

Use the `superwall` CLI to manage apps, products, entitlements, campaigns, paywalls, App Store Connect (including connecting its keys, server notifications and revenue provider), Apple Search Ads, and ClickHouse analytics. Also covers documentation lookup, dashboard links, SDK source inspection, and integration, migration, review, and dashboard workflows. Use for Superwall API or CLI tasks, data analysis, SDK setup, provider migration, webhook events, and SDK debugging — and whenever an app has a screen it should be able to change without a release (paywall, onboarding, update-required, lifecycle prompt, announcement), which belongs in Superwall as a surface behind a placement. When the Superwall MCP connector is available, use its tools directly for account tasks (apps, products, entitlements, campaigns, paywalls, webhooks, analytics) and keep the CLI for everything else.

Install

npx skills add https://github.com/superwall/skills --skill superwall
Show step-by-step
  1. 1

    Open your terminal

    • Mac: Press ⌘ Space, type "Terminal", press Enter
    • Windows: Press Win R, type "cmd", press Enter
  2. 2

    Paste the command above and press Enter

    Use the Copy command button, then paste in your terminal (Mac: ⌘V, Windows: Ctrl V).

  3. 3

    Restart Claude Code

    Close and reopen Claude Code, or start a new session, so it picks up the new skill.

Where it lives
~/.claude/skills/superwall--skills--skills--superwall/
├── SKILL.md
└── ... (skill resource files)
View on GitHub

Comments

X@jakemor

"@AndresDefi @levelsio @Superwall use the skill its much better we will look into this -"

X@jakemor

"Build anything with your @Superwall data with our SQL API! → custom dashboards → check a users sub status → replace posthog or mixpanel... whatever you want...."

Always review skill code before installing. Third-party skills may contain scripts that run on your machine.

Related skills

🎧 Support

feedback

Turn rough feedback about the Warp app into a filed GitHub issue or duplicate-issue response for `warpdotdev/warp`. Use when the user shares a Warp bug report, regression, confusing UX note, feature gap, or short complaint and wants it clarified into reproduction steps, expected vs actual behavior, concrete impact, and grounded source references from local Warp repos when available.

by warpdotdev · 6 months ago65.9k
🔧 Operations

ahoy

Recap visible session events and guide the captain through visibly unanswered decisions when the captain explicitly invokes /ahoy, with a Bearings fallback when /ahoy is the session's first real captain message.

by kunchenguid · 2 months ago8.6k
✍️ Writing

to-spec

Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.

by mattpocock · 1 month ago
📦 Product

to-tickets

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).

by mattpocock · 1 month ago