Give your coding agent Clerk guidance for adding authentication, managing teams and subscriptions, and testing sign-in flows.
Clerk Skills helps AI coding agents implement Clerk authentication and user management across web and mobile apps. Its router skill guides the agent toward the relevant setup, framework or feature instructions for your request. You can describe the task naturally or invoke a specific skill, such as /clerk-setup, directly.
The full plugin also configures Clerk’s remote MCP server for account operations and SDK snippets. Using that connection requires signing in with your Clerk account and choosing a workspace; its account tools act with your workspace role.
Ask the agent to add Clerk to an existing project or scaffold a new app. The setup skill covers framework detection and initial configuration, while framework skills provide patterns for protecting routes and using authentication in application code.
Build custom sign-in and sign-up forms with Clerk hooks, or adjust the appearance of Clerk’s prebuilt components. The custom UI skill selects its flow guidance according to your installed SDK version.
For a business app with multiple customer teams, use the Organizations skill to implement organization switching, invitations, membership management and access checks based on roles and permissions.
Add pricing tables and check access by plan or feature. Clerk Billing must be enabled; development instances can use Clerk’s shared development gateway, while production payment processing requires a Stripe account.
Create verified webhook handlers for user and organization events, using a Clerk webhook signing secret. Webhook delivery is asynchronous and eventually consistent, so use session data or the Backend API when a request needs newly created data immediately.
Add Playwright or Cypress tests for authentication flows and application access. The testing skill covers test setup, authentication helpers and handling Clerk’s bot detection during automated tests.
Showing all 20
Direct Clerk requests to the relevant setup, framework or feature skill.
Add Clerk to an existing project or scaffold a new app.
Build custom authentication forms or style Clerk’s prebuilt components.
Protect Next.js routes and use authentication in Server Actions and middleware.
Add authentication hooks and protected routes to React single-page apps.
Handle authentication in React Router loaders, actions and server rendering.
Use Clerk composables, Vue Router guards and Pinia in Vue 3.
Handle authentication in Nuxt middleware, server routes and rendered pages.
Add authentication to Astro middleware, server-rendered pages and islands.
Protect TanStack React Start routes, server functions and loaders.
Implement extension sign-in across popups, service workers and web-app sessions.
Implement authentication in native Swift and SwiftUI apps using ClerkKit.
Implement authentication in native Kotlin and Jetpack Compose apps.
Add Expo and React Native authentication with @clerk/expo v3.4 or later.
Build team workspaces with invitations, organization switching and role-based access.
Add pricing tables and plan-based access checks with Clerk Billing enabled.
Manage Clerk resources from the terminal using the Clerk CLI.
Explore endpoints and make Backend API requests with a Clerk secret key.
Build verified event handlers for database sync; requires a webhook signing secret.
Test authentication flows with Playwright or Cypress.
No matching results.
Manage Clerk applications and users, configure production instances, and retrieve SDK snippets.
Install the full plugin to get the skills and the bundled Clerk MCP connection.
In your Claude Code session, add the Clerk Skills marketplace.
/plugin marketplace add clerk/skillsIn the same session, install the Clerk plugin.
/plugin install clerk@clerk-skillsTo use the bundled MCP server, open Claude Code’s MCP menu, select clerk and choose Authenticate. In your browser, sign in with your Clerk account, select the workspace and review the permissions before choosing Allow. The server acts with your role in that workspace.
Check availability by asking the agent to load the clerk router skill and identify the skill for authentication setup. It should identify clerk-setup. After authorizing MCP access, ask the agent to call the Clerk MCP server’s whoami tool and check that it returns the intended user and workspace.
In your terminal, add the Clerk Skills marketplace.
copilot plugin marketplace add clerk/skillsIn your terminal, install the Clerk plugin.
copilot plugin install clerk@clerk-skillsTo use the bundled MCP server, complete Clerk’s browser sign-in when your client requests authentication. Select the workspace, review the permissions and choose Allow. The server acts with your role in that workspace.
Check availability by asking the agent to load the clerk router skill and identify the skill for authentication setup. It should identify clerk-setup. After authorizing MCP access, ask the agent to call the Clerk MCP server’s whoami tool and check that it returns the intended user and workspace.
In your terminal, add the Clerk Skills marketplace.
cursor-agent plugin marketplace add https://github.com/clerk/skillsOpen Customize in Cursor and install the clerk plugin from the added marketplace. Choose project scope for this project or user scope to make it available across projects.
To use the bundled MCP server, open Customize, then MCPs. Under Needs attention, select Authenticate next to clerk. In your browser, sign in with your Clerk account, select the workspace, review the permissions and choose Allow. The server acts with your role in that workspace.
In Agent chat, open the slash menu and search for clerk-setup to find the installed skill. After MCP authentication, check that clerk appears under Connected. Ask the agent to call the Clerk MCP server’s whoami tool and confirm that it returns the intended user and workspace.
In your terminal, add the Clerk plugin marketplace.
codex plugin marketplace add clerk/skillsIn your terminal, add the Clerk plugin.
codex plugin add clerk@clerkStart a new Codex CLI session to load the plugin’s skills and tools.
To use the bundled MCP server, complete the Clerk sign-in when prompted: select your workspace, review the requested permissions and choose Allow. The server acts with your role in that workspace. Clerk’s Codex connection guide covers signing in again.
Check availability by asking the agent to load the clerk router skill and identify the skill for authentication setup. It should identify clerk-setup. After authorizing MCP access, ask the agent to call the Clerk MCP server’s whoami tool and check that it returns the intended user and workspace.