Web App Paywall Implementation Agent Skill

Implement paywalls, subscription billing, and feature gating in web applications.

Context cost
12.3k tokensestimated from the bundle, loaded when it triggers
Bundle
1 file · 49.1 kBtext throughout, nothing executable
Licence
Apache-2.0the author’s own terms
Last change
—no release on file
Servers it uses
Noneruns standalone

What it does

Implement paywalls, subscription billing, and feature gating in web applications. Covers Stripe/Lemon Squeezy/Paddle integration, subscription lifecycle management, React/Next.js gating patterns, webhook handling, and pricing page design. Activate on 'paywall', 'subscription', 'billing', 'Stripe integration', 'feature gating', 'pricing tier', 'payment', 'monetize', 'charge users', 'Stripe Checkout', 'webhook handler', 'subscription state'.

What this skill changes about the agent has not been set out here as a list. Its SKILL.md, shown below, says it in the author’s own words.

authenticatione-commercepaymentspaywallstripesubscription

The skill itself

A skill is instructions the model reads, so you can see what you are getting: below is the start of its SKILL.md. The front matter loads with every session, the body loads when the skill triggers, and the whole file comes with the install.

SKILL.md49.1 kB · preview
--- license: Apache-2.0 name: webapp-paywall-implementation allowed-tools: Read,Write,Edit,Bash,Glob,Grep,WebSearch,WebFetch metadata: category: Monetization & Infrastructure tags: - paywall - stripe - subscription - billing - monetization - feature-gating - saas - webhook - checkout - lemon-squeezy - paddle pairs-with: - skill: indie-monetization-strategist reason: Pricing strategy decisions that inform what to gate and how - skill: nextjs-app-router-expert reason: Implementation patterns for Next.js App Router middleware and server-side gating - skill: supabase-admin reason: RLS policies for plan-gated database access - skill: modern-auth-2026 reason: Auth state carries subscription tier for gating decisions - skill: oauth-oidc-implementer reason: Identity layer that the paywall sits on top of category: Backend & Infrastructure tags: - paywall - payments - stripe - subscription - authentication ---
40# Web App Paywall Implementation
41
42Full-stack guide to putting a paywall around your web app -- from choosing a payment provider to handling failed payments at 3 AM. This is the implementation skill: it assumes you have already decided *what* to charge for (if not, start with **indie-monetization-strategist**) and focuses on *how* to build it correctly.
43
44## When to Use
45
46**Use for:**
47- Integrating Stripe Checkout, Lemon Squeezy, or Paddle into a web app
48- Building subscription lifecycle management (create, upgrade, downgrade, cancel, resume)
49- Implementing feature gating in React/Next.js (middleware, server-side, client-side)
50- Designing the database schema for subscription state
51- Handling webhooks reliably (signature verification, idempotency, race conditions)
52- Building pricing pages, upgrade flows, and customer portal redirects
53- Managing edge cases: failed payments, grace periods, refunds, proration
54
55**Do NOT use for:**
56- Pricing strategy and what to charge --> use **indie-monetization-strategist**
57- Payment page visual design only --> use **web-design-expert**
58- In-app mobile purchases (iOS/Android) --> App Store rules are a separate domain
This is a preview of SKILL.md. Download or install the skill to get the whole thing.
In the file
SKILL.md5,346 words
Files1
LicenceApache-2.0
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈420
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
11,855
on trigger
The instruction body, read only when the skill fires.
6.1%
of a 200k window
Ten skills this size would take about 61% of the window before you open a file.
050k100k150k200k context window

12.3k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

The procedure it runs

The procedure has not been set out here step by step. It is in the body of its SKILL.md: the start of it is shown above, and the whole file comes with the install.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It does ask the agent to write files and to fetch pages, using the file and network access your client already has.

What it asks for
Writes filesyes
Network accessyes

Read from the allowed-tools line of this skill’s own SKILL.md. It also asks for Bash, which could do either, so what is not named there is not ruled out. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

1 file, 49.1 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md49.1 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 1 file you can review in full before installing. The Apache-2.0 licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# Web App Paywall Implementation · 12.3k tokens when loaded · macOS, Linux mkdir -p .claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/web-app-paywall-implementation/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/web-app-paywall-implementation" ] && { [ ! -e .claude/skills/web-app-paywall-implementation ] || { mv .claude/skills/web-app-paywall-implementation "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/web-app-paywall-implementation" .claude/skills/ && echo "Installed .claude/skills/web-app-paywall-implementation"
On Windows, or any OS with Node 20+
npx mcprush@latest skill add curiositech/web-app-paywall-implementation

Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither. Writes to .claude/skills/web-app-paywall-implementation/ in the current project. For every project instead, run mkdir -p ~/.claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/web-app-paywall-implementation/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/web-app-paywall-implementation" ] && { [ ! -e ~/.claude/skills/web-app-paywall-implementation ] || { mv ~/.claude/skills/web-app-paywall-implementation "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/web-app-paywall-implementation" ~/.claude/skills/ && echo "Installed ~/.claude/skills/web-app-paywall-implementation" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/web-app-paywall-implementation/ only after the download succeeds, so files left there by another skill of the same name, or by an older release, do not mix in. A copy already there is moved aside, not deleted, and the line prints where. It appears as webapp-paywall-implementation in Gemini CLI, Codex, Copilot and Grok (its own name); Claude Code lists it by the folder name, web-app-paywall-implementation.

Which clients pick it up on their own

A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.

Claude Code.claude/skills/
Claude DesktopCustomize › Skills
ChatGPTSkills › Create › Upload
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok Build.grok/skills/
Microsoft CopilotSkills › Upload a skill
PerplexityComputer › Skills › Upload a skill
DeepSeek Harness.dsh/skills/
Zed.agents/skills/
Devin Desktop.devin/skills/
Windsurf (legacy).windsurf/skills/
OpenAI Agents SDKInstructions or sandbox Skills
HTTP / APIa request parameter
This release
Versionnot versioned
Publishedno release date on file
PriceFree
Referencecuriositech/web-app-paywall-implementation

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

—no reviews yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Sign in to review it

A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.

Sign in
Who can post

Anybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.

Publisher
Servers0
Claim this skill