Clerk

Organization

clerk

Clerk authentication router. Use when user asks about Clerk CLI operations, adding authentication, setting up Clerk, custom sign-in flows, Swift or native iOS auth, native Android auth, Next.js patterns, React patterns, Vue patterns, Nuxt patterns, Astro patterns, TanStack Start patterns, Expo patterns, React Router patterns, Chrome Extension patterns, organizations, billing, subscriptions, payments, pricing, plans, seat-based pricing, feature entitlements, syncing users, testing, impersonating a user, or testing webhooks locally. Automatically routes to the specific skill based on their task.

Overview

Publisher	clerk
Repository	`skills`
Skill name	`clerk`
Stars	83
Forks	5
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by clerk on GitHub. Read the source before you install it.

Installation

Install the Clerk AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/clerk/skills/tree/main/skills/core/clerk
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/clerk/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/skills/core/clerk .claude/skills/clerk

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Clerk in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Clerk on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Clerk is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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, temporary dev keys via clerk init
Migration from other auth providers

Operating Clerk from the CLI → Use clerk-cli

Auth, linking, doctor, and environment pulls
User, org, session, app, and instance management
Impersonating a user (clerk impersonate) and local webhook testing (clerk webhooks listen)
Feature toggles (clerk enable orgs, clerk enable billing)
Backend, Platform, and Frontend API calls through clerk api
Deploy handoff and deploy status verification

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

React patterns → Use clerk-react-patterns

Hooks (useAuth, useUser, useClerk)
Protected routes, auth guards
Router integration

React Router patterns → Use clerk-react-router-patterns

Loaders & actions with auth
Route protection
SSR auth

Vue patterns → Use clerk-vue-patterns

Composables (useAuth, useUser, useClerk)
Vue Router guards
Pinia auth store integration

Nuxt patterns → Use clerk-nuxt-patterns

Server middleware auth
SSR auth with composables
Server API routes

Astro patterns → Use clerk-astro-patterns

SSR auth pages
Island components with React
Middleware & API routes

TanStack Start patterns → Use clerk-tanstack-patterns

Server functions with auth
Route protection via loaders
Vinxi server integration

Expo / React Native auth → Use clerk-expo

Prebuilt native components (AuthView, UserButton)
Custom flows: email, password, SMS/phone OTP, MFA
OAuth/SSO and native Google/Apple sign-in
Expo Router protected routes, token storage, push notifications

Chrome Extension patterns → Use clerk-chrome-extension-patterns

Background scripts auth
Popup auth flows
Content scripts with sync host

B2B / Organizations → Use clerk-orgs

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

Billing & Subscriptions → Use clerk-billing

<PricingTable /> component
Plan and feature gating with has()
Seat-based B2B billing with organizations
Subscription lifecycle webhooks
Free trials, invoicing

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

Android / native mobile auth → Use clerk-android

Native Android Kotlin and Jetpack Compose projects
clerk-android-api and clerk-android-ui implementation guidance
Source-driven patterns from clerk-android
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-cli - CLI operations and Clerk resource management
/clerk-custom-ui - Custom flows & appearance
/clerk-nextjs-patterns - Next.js patterns
/clerk-react-patterns - React patterns
/clerk-react-router-patterns - React Router patterns
/clerk-vue-patterns - Vue patterns
/clerk-nuxt-patterns - Nuxt patterns
/clerk-astro-patterns - Astro patterns
/clerk-tanstack-patterns - TanStack Start patterns
/clerk-expo - Expo / React Native
/clerk-chrome-extension-patterns - Chrome Extension patterns
/clerk-orgs - Organizations
/clerk-billing - Billing & subscriptions
/clerk-webhooks - Webhooks
/clerk-testing - Testing
/clerk-swift - Swift/native iOS
/clerk-android - Native Android
/clerk-backend-api - Backend REST API

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

Frequently asked questions

What does the Clerk AI skill do?

Why use Clerk on TypingMind?

Because you install it once and use it with any model. Clerk is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Clerk in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/clerk/skills/tree/main/skills/core/clerk. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Clerk?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Clerk?

As many as you like. As long as a model supports skills, you can use Clerk with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Clerk AI skill free?

Yes. It is published on GitHub by clerk under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Mle Workflow

affaan-m

CommunityPopular

Production machine-learning engineering workflow for data contracts, reproducible training, model evaluation, deployment, monitoring, and rollback. Use when building, reviewing, or hardening ML…

Diagnosing Bugs

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

E2e Testing

Patrones de pruebas E2E con Playwright, Page Object Model, configuración, integración CI/CD, gestión de artefactos y estrategias para pruebas inestables.

Eval Harness

Framework formal de evaluación para sesiones de Claude Code que implementa principios de desarrollo orientado a evals (EDD)

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Clerk Skills Router

Version Detection

By Task

Quick Navigation

Frequently asked questions

Related AI Skills

Set up your own AI workspace now