clerk

Routes Clerk authentication tasks to framework-specific implementation skills.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/Rajaryan1726/ai-code-review-system --skill clerk-rajaryan1726
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clerk
Source: https://github.com/Rajaryan1726/ai-code-review-system/tree/main/client/.agents/skills/clerk
Command: npx skills add https://github.com/Rajaryan1726/ai-code-review-system --skill clerk-rajaryan1726

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers integrating Clerk authentication often don't know which SDK pattern, CLI command, or framework-specific approach applies to their project, leading to mismatched implementations across Next.js, React, Expo, and other platforms. ## Core Features & Use Cases - Task-Based Routing: Directs requests to 19 specialized skills covering setup, CLI operations, custom UI, organizations, billing, webhooks, and testing. - SDK Version Detection: Reads package.json to distinguish Core 2 (v5–v6) from current (v7+) Clerk SDKs and applies the correct patterns. - Framework Coverage: Provides guidance for Next.js, React, React Router, Vue, Nuxt, Astro, TanStack Start, Expo, Chrome Extensions, Swift, and Android. - Use Case: A developer asks how to add organization-based billing to a Next.js app; the router detects the SDK version and routes to clerk-orgs and clerk-billing with the correct API patterns. ## Quick Start Ask how to add Clerk authentication to your framework of choice and get routed to the right implementation guide.

Frequently Asked Questions about clerk

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add Clerk authentication to a Next.js app?▼

Clerk setup for Next.js is handled by the clerk-setup skill, which covers framework detection, environment variables, and API keys. For advanced patterns like middleware and server actions, the router directs you to clerk-nextjs-patterns.

How do I build a custom sign-in flow with Clerk?▼

Custom sign-in and sign-up flows use the useSignIn and useSignUp hooks covered by the clerk-custom-ui skill. It also handles appearance theming and conditional rendering with the Show component, with separate guidance for Core 2 and current SDKs.

What is the difference between Clerk Core 2 and the current SDK?▼

Core 2 packages use @clerk/clerk-react and @clerk/clerk-expo at versions v5–v6, while current packages use @clerk/react and @clerk/expo at v7+. The router checks package.json to detect your version and applies the matching patterns.

Does Clerk support native iOS and Android apps?▼

Yes, Clerk supports native mobile through clerk-swift for SwiftUI projects using ClerkKit and clerk-android for Kotlin and Jetpack Compose projects. Expo and React Native apps should use the clerk-expo skill instead.

How do I test Clerk webhooks locally?▼

Local webhook testing uses the clerk webhooks listen CLI command, covered by the clerk-cli skill. For webhook event handling and data syncing patterns in your application code, the router points to clerk-webhooks.