Clerk Skills plugin
Official Clerk skills that teach an agent to add authentication to Next.js, React, Vue, Expo, Swift and Android apps
- 93 ★ on the repository
- Last commit
Extended access
Why this level
- The skills edit project code and work with Clerk keys, while the backend-api skill calls the application REST API.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/clerk-skillsDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The skills edit project code and work with Clerk keys, while the backend-api skill calls the application REST API.
This is third-party code. Review the repository files before installing.
What it does
Clerk Skills is the official skill set from Clerk for working with its authentication service. The `clerk` plugin bundles every skill with the Clerk MCP server, while `npx skills` installs only the skills into any agent. The entry point is the router skill `/clerk`, which sends a request to the right specialist. Core skills: `clerk-setup` adds Clerk to an existing project, scaffolds a new app in an empty folder or links an existing Clerk application; `clerk-cli` manages users, organizations, applications and environment keys; `clerk-custom-ui` builds custom sign-in and sign-up forms; `clerk-backend-api` explores and calls the REST API. For frameworks there are patterns for Next.js, React, React Router, Vue, Nuxt, Astro, TanStack Start and Chrome extensions. Separate skills cover B2B organizations, billing with plans and feature gating, webhooks and E2E tests with Playwright and Cypress, plus native apps on Swift, Android and Expo.
Who it is for. Web and mobile developers adding Clerk to an app who want the agent to know the right patterns instead of guessing from stale documentation.
Good fit when
- A Next.js project needs sign-in and sign-up with route protection through middleware and Server Actions
- An Expo app needs SMS code sign-in or OAuth with native components
- The stock Clerk forms do not fit and you need a custom sign-in form with your own styling
- Clerk users have to be synced to a database through webhooks, for example with Prisma
- A B2B product needs organizations, roles and pricing plans that gate features by subscription
Not a fit when
- The project uses another authentication provider: the skills are built for Clerk only
- You need general web application security guidance not tied to a service
- One small change in a working integration is enough and the agent can read the Clerk docs on its own
Example request
Add Clerk to my Next.js app: sign-in, sign-up and protection for the /dashboard route.Limitations
The skills work with Clerk only and need its account or temporary development keys: for a new project on a supported framework `clerk init` starts without an account or browser sign-in, and the account can be claimed later. The `clerk` plugin connects the remote MCP server mcp.clerk.com, which receives agent requests. The `clerk-backend-api` skill calls the application REST API, so give keys carefully. In Codex the `clerk` plugin replaced the earlier `clerk-skills@clerk`, and in Copilot CLI you run `copilot plugin enable clerk@clerk-skills` once after the migration. Read the agent output before shipping it to production.
How to disable. Remove the plugin through `/plugin` in Claude Code or with `codex plugin remove clerk@clerk` in Codex. Skills installed through `npx skills` are deleted from the agent skills directory.
FAQ
How do I install the Clerk skills in Claude Code?
Run `/plugin marketplace add clerk/skills` and `/plugin install clerk@clerk-skills`. Auto-update is enabled in `/plugin`, on the Marketplaces tab.
How does the `clerk` plugin differ from installing with `npx skills`?
The plugin installs every skill and connects the Clerk MCP server. `npx skills add clerk/skills` installs only the skills and works with any agent.
Which frameworks are covered?
Next.js, React, React Router, Vue, Nuxt, Astro, TanStack Start and Chrome extensions, plus Swift, Android and Expo for mobile apps.
Do I need a Clerk account to start?
For a new project on a supported framework `clerk init` creates temporary development keys without an account or browser sign-in. The account can be claimed later.
Which agents are supported?
The repository carries manifests for Claude Code, Codex, Cursor and GitHub Copilot CLI, and `npx skills` installs the skills into other agents.
Discussion
No questions or reviews yet.
Related
PluginsHundreds of per-provider skills teach an agent to receive webhooks, verify signatures and handle events, with code examples.
WorkOS Skills: AuthKit, SSO and RBAC for agents
WorkOS Skills
Official WorkOS skills: a router and 40 references on AuthKit, SSO, Directory Sync, RBAC, Vault and moves from Auth0 and Clerk
Five Saleor skills for an agent: apps, storefronts, store configuration as code and backend internals
Better Auth skills
Better Auth Skills
Official Better Auth skills: scaffold authentication in JS and TS projects and guide a secure setup
Official Firebase plugin for agents: 14 skills on Firestore, Auth, Hosting, Crashlytics, Remote Config and security rules
The official Payload CMS skill shipped inside the package: collections, fields, hooks, access control, queries and database adapters
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Clerk Skills (this card) | no | 93 | ||
| Better Auth skills | no | 230 | skills for the Better Auth library; Clerk Skills work with the hosted Clerk service | |
| Auth0 MCP Server | yes | OAuth | 122 | Auth0 MCP server for tenant management; Clerk Skills teach an agent to write a Clerk integration |
README in short
The README lists install options for four agents, a skill table by group (core, frameworks, features, mobile), a quick start and example requests naming the skill that fires.