How do I install the Clerk skill?

Run npx skillmds@latest add tomevault-io/clerk in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Clerk safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Clerk?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Clerk free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Clerk by tomevault-io — Agent Skill

Name: Clerk
Author: tomevault-io

Clerk

Clerk authentication router. Use when user asks about adding authentication, setting up Clerk, custom sign-in flows, Swift or native iOS auth, Next.js patterns, organizations, syncing users, or testing. Automatically routes to the specific skill based on their task. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Clerk Skills Router

Version Detection

Check package.json to determine the Clerk SDK version. This determines which patterns to use:

Package	Core 2 (LTS until Jan 2027)	Current
`@clerk/nextjs`	v5–v6	v7+
`@clerk/react` or `@clerk/clerk-react`	v5–v6	v7+
`@clerk/expo` or `@clerk/clerk-expo`	v1–v2	v3+
`@clerk/react-router`	v1–v2	v3+
`@clerk/tanstack-react-start`	< v0.26.0	v0.26.0+

Default to current if the version is unclear or the project is new. Core 2 packages use @clerk/clerk-react and @clerk/clerk-expo (with clerk- prefix); current packages use @clerk/react and @clerk/expo.

All skills are written for the current SDK. When something differs in Core 2, it's noted inline with > **Core 2 ONLY (skip if current SDK):** callouts. The exception is clerk-custom-ui, which has separate core-2/ and core-3/ directories for custom flow hooks since those APIs are entirely different between versions.

By Task

Adding Clerk to your project → Use clerk-setup

Framework detection and quickstart
Environment setup, API keys, Keyless flow
Migration from other auth providers

Custom sign-in/sign-up UI → Use clerk-custom-ui

Custom authentication flows with useSignIn / useSignUp hooks
Appearance and styling (themes, colors, layout)
<Show> component for conditional rendering

Advanced Next.js patterns → Use clerk-nextjs-patterns

Server vs Client auth APIs
Middleware strategies
Server Actions, caching
API route protection

B2B / Organizations → Use clerk-orgs

Multi-tenant apps
Organization slugs in URLs
Roles, permissions, RBAC
Member management

Webhooks → Use clerk-webhooks

Real-time events
Data syncing
Notifications & integrations

E2E Testing → Use clerk-testing

Playwright/Cypress setup
Auth flow testing
Test utilities

Swift / native iOS auth → Use clerk-swift

Native iOS Swift and SwiftUI projects
ClerkKit and ClerkKitUI implementation guidance
Source-driven patterns from clerk-ios
Do not use for Expo or React Native projects

Backend REST API → Use clerk-backend-api

Browse API tags and endpoints
Inspect endpoint schemas
Execute API requests with scope enforcement

Quick Navigation

If you know your task, you can directly access:

/clerk-setup - Framework setup
/clerk-custom-ui - Custom flows & appearance
/clerk-nextjs-patterns - Next.js patterns
/clerk-orgs - Organizations
/clerk-webhooks - Webhooks
/clerk-testing - Testing
/clerk-swift - Swift/native iOS
/clerk-backend-api - Backend REST API

Or describe what you need and I'll recommend the right one.

Source: mihaicrisan04/zalem — distributed by TomeVault.

---name: clerkdescription: Clerk authentication router. Use when user asks about adding authentication, setting up Clerk, custom sign-in flows, Swift or native iOS auth, Next.js patterns, organizations, syncing users, or testing. Automatically routes to the specific skill based on their task. Use when this capability is needed.---# Clerk Skills Router## Version DetectionCheck `package.json` to determine the Clerk SDK version. This determines which patterns to use:| Package | Core 2 (LTS until Jan 2027) | Current || -------------------------------------- | --------------------------- | -------- || `@clerk/nextjs` | v5–v6 | v7+ || `@clerk/react` or `@clerk/clerk-react` | v5–v6 | v7+ || `@clerk/expo` or `@clerk/clerk-expo` | v1–v2 | v3+ || `@clerk/react-router` | v1–v2 | v3+ || `@clerk/tanstack-react-start` | < v0.26.0 | v0.26.0+ |**Default to current** if the version is unclear or the project is new. Core 2 packages use `@clerk/clerk-react` and `@clerk/clerk-expo` (with `clerk-` prefix); current packages use `@clerk/react` and `@clerk/expo`.All skills are written for the current SDK. When something differs in Core 2, it's noted inline with `> **Core 2 ONLY (skip if current SDK):**` callouts. The exception is `clerk-custom-ui`, which has separate `core-2/` and `core-3/` directories for custom flow hooks since those APIs are entirely different between versions.---## By Task**Adding Clerk to your project** → Use `clerk-setup`- Framework detection and quickstart- Environment setup, API keys, Keyless flow- Migration from other auth providers**Custom sign-in/sign-up UI** → Use `clerk-custom-ui`- Custom authentication flows with `useSignIn` / `useSignUp` hooks- Appearance and styling (themes, colors, layout)- `<Show>` component for conditional rendering**Advanced Next.js patterns** → Use `clerk-nextjs-patterns`- Server vs Client auth APIs- Middleware strategies- Server Actions, caching- API route protection**B2B / Organizations** → Use `clerk-orgs`- Multi-tenant apps- Organization slugs in URLs- Roles, permissions, RBAC- Member management**Webhooks** → Use `clerk-webhooks`- Real-time events- Data syncing- Notifications & integrations**E2E Testing** → Use `clerk-testing`- Playwright/Cypress setup- Auth flow testing- Test utilities**Swift / native iOS auth** → Use `clerk-swift`- Native iOS Swift and SwiftUI projects- ClerkKit and ClerkKitUI implementation guidance- Source-driven patterns from `clerk-ios`- Do not use for Expo or React Native projects**Backend REST API** → Use `clerk-backend-api`- Browse API tags and endpoints- Inspect endpoint schemas- Execute API requests with scope enforcement## Quick NavigationIf you know your task, you can directly access:- `/clerk-setup` - Framework setup- `/clerk-custom-ui` - Custom flows & appearance- `/clerk-nextjs-patterns` - Next.js patterns- `/clerk-orgs` - Organizations- `/clerk-webhooks` - Webhooks- `/clerk-testing` - Testing- `/clerk-swift` - Swift/native iOS- `/clerk-backend-api` - Backend REST APIOr describe what you need and I'll recommend the right one.---> Source: [mihaicrisan04/zalem](https://github.com/mihaicrisan04/zalem) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions