PlugWiki

clerk-billing Skill: What It Does and How to Install It

Makes your coding agent add Clerk Billing to your app: pricing table, checkout, plan and feature gates, seat limits and webhooks.

Installs
17.1K
on skills.sh
Stars
89
on GitHub
Files
5
besides SKILL.md
Updated
Oct 2026
last repo commit

The SKILL.md has the agent turn on Billing for your Clerk instance, create plans and features, render <PricingTable />, gate access with has({ plan }) or has({ feature }), and handle billing webhooks. It can enable billing and edit plans from the Clerk CLI (clerk enable billing, clerk config pull, clerk config patch), or you can use the dashboard. The examples use @clerk/nextjs.

It loads for pricing tables, checkout, plan gating, trials and subscription lifecycle questions. Billing must be enabled first, and the SKILL.md says production instances need a Stripe account for payment processing, while development instances can use a shared Clerk development gateway.

Good for

  • SaaS developers selling plans with Clerk
  • B2B teams with per-organization plans and seat limits
  • Teams gating features by plan with has()

Install clerk-billing

Claude Code

  1. 1

    Copy this prompt.

    Install the clerk-billing skill in Claude Code. Run this command:

/plugin marketplace add clerk/skills
/plugin install clerk@clerk-skills

Then check that it loaded and tell me how to use it.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Pick one route. The plugin installs all 20 skills in the Clerk repo (counted from the repo tree) and adds the Clerk MCP server from the repo's .mcp.json, which points at https://mcp.clerk.com/mcp. The skills-only routes install just this skill and no MCP server config. This skill's CLI commands need the Clerk CLI and a linked project; the clerk-cli skill covers that setup. The README says to open /plugin, go to Marketplaces, select clerk-skills and enable auto-update if you want updates.

From the project README. Source.

What's in the skill

When it loads

Clerk Billing for subscription management - render Clerk's PricingTable and in-app checkout drawer, configure subscription plans, seat-limit plans for B2B, feature entitlements with has(), and billing webhooks. Use for SaaS monetization, plan gating, checkout flows, trials, invoicing, and subscription lifecycle management.

Sections in SKILL.md

  1. Quick Start
  2. Dashboard shortcuts
  3. Agent-first: Programmatic billing config
  4. Enable Billing via CLI
  5. Pull current billing config
  6. Edit and apply
  7. Raw PATCH (full control)
  8. Notes
  9. What Do You Need?
  10. References
  11. Documentation
  12. Features vs Plans: When to Use Which
  13. Key Patterns
  14. 1. Render the Pricing Table
  15. 2. Check Feature Entitlements (Server-Side)
  16. 3. Check Feature Entitlements (Client-Side)

Key facts

Author
Clerk (the skill is in Clerk's own clerk/skills repo)
License
MIT (README, plugin.json and SKILL.md frontmatter; the repo has no LICENSE file)
Installs on skills.sh
17,148 (Nov 2, 2026)
GitHub stars
89 for the whole clerk/skills repo (Nov 2, 2026)
Last repo commit
Oct 30, 2026
What it includes
6 files including SKILL.md: 4 reference files and an evals/evals.json file
Needs
Billing enabled in the Clerk Dashboard; NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY, CLERK_SECRET_KEY and CLERK_WEBHOOK_SIGNING_SECRET; a Stripe account for production (SKILL.md compatibility line)
Works in
Claude Code, Codex, Cursor and GitHub Copilot CLI through the plugin; any agent through npx skills

What it includes

  • Turn on Billing in the dashboard or with clerk enable billing.

    The CLI route needs a linked project and can target users, orgs or both. Billing cannot be enabled on an unclaimed app.

    Try: “Enable Clerk Billing for my app”

    Runs code · Enable Billing

  • Create plans in the right tab and attach features to them.

    User plans and organization plans live in separate tabs, and features are scoped per plan. They can be edited by hand or through a billing.json config.

    Write · Plans and features

  • Pull billing config to billing.json, preview with --dry-run, then apply.

    Uses clerk config pull --keys billing, then clerk config patch --file billing.json. Pass --instance prod to target production.

    Runs code · Config pull and patch

  • Render PricingTable and CheckoutButton.

    Selecting a plan opens Clerk's in-app checkout drawer. Pass for="organization" for B2B. Source: references/billing-components.md.

    Try: “Add a pricing page with Clerk Billing”

    Write · Pricing table and checkout

  • Gate UI and API routes with has({ feature }) or has({ plan }).

    Use has({ feature }) for a capability and has({ plan }) for a tier. Works on the server with auth() and on the client with useAuth().

    Try: “Gate the export button behind the pro plan”

    Write · Plan and feature checks

  • Individual subscriptions, organization plans and seat-limit plans.

    Sources: references/b2c-patterns.md and references/b2b-patterns.md.

    Write · B2C and B2B patterns

  • Handle subscription and payment events with verifyWebhook.

    The reference covers 15 events, with Clerk event names such as subscriptionItem.canceled, not Stripe's. Source: references/billing-webhooks.md.

    Write · Billing webhooks

  • Diagnose an empty PricingTable or a has() that returns false.

    A table of errors such as cannot_render_billing_disabled with the dashboard fix for each.

    Read · Error signatures

From the official docs

Permissions

Medium risk

The skill can change plans and billing settings in your Clerk instance, and it edits your code and webhook route. Use --dry-run first, check whether the command targets dev or production, and review the diff before you commit it.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • It can change plans and billing settings in Clerk

    The SKILL.md shows clerk enable billing, clerk config patch --file billing.json and a raw clerk api --platform PATCH call that edit plans, features and toggles. It shows --dry-run before the real patch, and --instance prod targets production, so preview first and confirm the instance. github.com

  • It edits your code and webhook route

    The SKILL.md examples add pricing tables, plan checks and a billing webhook handler that uses CLERK_WEBHOOK_SIGNING_SECRET. Review the diff, and keep the webhook route out of auth.protect(). github.com

  • Billing APIs are marked experimental

    The SKILL.md notes that Billing APIs are still experimental and tells you to pin your @clerk/nextjs and clerk-js package versions. github.com

  • The plugin route also adds the Clerk MCP server

    The plugin's .mcp.json registers https://mcp.clerk.com/mcp. Use the skills CLI route if you only want this skill. github.com

Security advisories

No published security advisories as of Nov 2, 2026.

Technical details
Turning on read-onlyNo read-only mode.
Talks toWebFetch tool (the frontmatter allows it). Clerk Platform API through the clerk CLI (config and api commands)
Sign-in and keysThe SKILL.md lists NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY, CLERK_SECRET_KEY and CLERK_WEBHOOK_SIGNING_SECRET as required.
Scopes

  • Your project files

  • Your Clerk instance billing settings (when you use the CLI route)

  • Webhook signing secret

Questions

What does clerk-billing do?

It makes your coding agent add Clerk Billing: enable it, set up plans and features, render a pricing table and checkout, gate access with has(), and handle subscription webhooks.

How do I install clerk-billing?

Use the install box above. The Claude Code plugin route installs every Clerk skill and the Clerk MCP server, and the skills CLI route installs only this skill. Pick one route, not both, or you get the skills twice.

Is clerk-billing official?

Yes. It is published in Clerk's own clerk/skills repository, and the plugin.json in that repo lists Clerk as the author.

Does clerk-billing work in the Claude app or Codex?

Codex, Cursor and GitHub Copilot CLI each have a plugin install in the README. The README does not document uploading Clerk skills to the Claude app, and this skill's job is to change code in a local project, so the install box has no Claude app tab.

Does it need a Clerk account or API key?

You need a Clerk publishable key, a secret key and a webhook signing secret, which the SKILL.md's compatibility line lists, and Billing turned on for your instance. The CLI route also needs the Clerk CLI signed in and the project linked.

Is clerk-billing safe to install?

Its SKILL.md makes the agent change files in your project and use Clerk keys from your env file, and its frontmatter allows the WebFetch tool. Our advice: read each change before you commit it, and keep the secret key out of git. It can also change billing settings in your Clerk instance, so preview with --dry-run and check the --instance value.

Does it need Stripe?

Only for production. The SKILL.md says development instances can use the shared Clerk development gateway with no Stripe account, and production instances need a Stripe account for payment processing.

Does it only work with Next.js?

Its code examples use @clerk/nextjs. The billing setup, plans and webhook events are not tied to the framework, and the SKILL.md points to clerk-nextjs-patterns for Next.js specifics.

Information

updated Nov 2, 2026

Repository
clerk/skills
Folder
skills/clerk-billing

clerk/skillsskills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 5
  1. clerk-billing SKILL.md · github.com
  2. clerk-billing billing-webhooks.md · github.com
  3. clerk/skills README · github.com
  4. clerk plugin.json · github.com
  5. clerk .mcp.json · github.com

Updated Nov 2, 2026.