superwall-editor
Superwall Paywall Editor
Paywalls are built in a browser editor that exposes its tools over an authenticated relay. This skill drives that relay from the CLI — the exact same surface the MCP gateway uses — so every tool you invoke runs inside the live browser session the user has open.
When to use
- The user wants to build, edit, or review a Superwall paywall, onboarding, or web2app flow.
- The user pastes a pairing code and asks you to take over editing.
- The user asks "what tools can you run right now?" — discover them via the browser, not from memory.
Start here: attach, then discover
Never assume a tool name or signature from memory. The browser is the source of truth and its tool set changes across releases.
Preferred API launch flow:
More from superwall/skills
superwall
Provides Superwall REST API access, ClickHouse data analytics, documentation lookup, SDK integration triage, dashboard linking, and SDK source cloning. Use when the user asks about Superwall paywalls, campaigns, subscriptions, API usage, data analysis, SDK integration, webhook events, or debugging SDK behavior.`
1.1Ksuperwall-ios-quickstart
Superwall quickstart for native iOS apps (Swift/Objective-C). Use for iOS SDK setup.
93superwall-expo-quickstart
Superwall quickstart for Expo apps, including Expo projects shipping to iOS and Android.
79superwall-flutter-quickstart
Superwall quickstart for Flutter apps.
35superwall-android-quickstart
Superwall quickstart for native Android apps. Use for Android SDK setup.
30paywall-editor
Build and edit live Superwall paywalls from the CLI. Attach to a running browser editor session using a pairing code, list the tools the browser exposes right now, and invoke them. Covers native sw-* elements, editing workflow, design standards, and the attach/call/release lifecycle. Use whenever the user wants to design, build, modify, or review a Superwall paywall, onboarding, or web2app flow.
11