Use Case
Clerk Auth isn't just for solo use β teams can share skills and build consistent AI workflows across the organization. Clerk auth with API Keys beta (Dec 2025), Next.js 16 proxy.ts (March 2025 CVE context), API version 2025-11-10 breaking changes, clerkMiddleware() options, webhooks, production considerations (GCP outages), and component reference. Prevents 15 documented errors. Use when: API keys for users/orgs, Next.js 16 middleware filename, troubleshooting JWKS/CSRF/JWT/token-type-mismatch errors, webhook verification, user type inconsistencies, or testing with 424242 OTP. This guide covers how to deploy Clerk Auth for your team, standardize prompts, and create shared workflows that everyone can use.
Install Clerk Auth in your project directory: .claude/skills/clerk-auth/
Commit the skill folder to your repository so the whole team has access
Document your team's standard prompts in a shared README
Use Clerk Auth in code reviews, standups, and planning sessions
Iterate: collect feedback from the team and refine your prompts
Copy these prompts and use them with your AI agent after installing Clerk Auth
How can my team use Clerk Auth together?
Set up Clerk Auth for our project so everyone can use it
Create a shared workflow using Clerk Auth for our team
Select your agent
Option 1: Install via CLI (recommended)
Recommended (no pre-install needed)
npx clawhub@latest --dir ~/.claude/skills install clerk-authOr via clawhub CLI (if already installed)
clawhub --dir ~/.claude/skills install clerk-authβ οΈ Requires Node.js 18+. No Node? Use Option 2 below to download the ZIP instead. Install Node.js β
Option 2: Manual install (no Node required)
Download the ZIP, extract it, and place the folder at the path below. Restart your agent to activate.
Install path
~/.claude/skills/clerk-auth/π‘Extract and place the folder at the path above, then restart your agent.