About clerk-auth
clerk-auth is a skill for implementing Clerk authentication, including middleware, organizations, webhooks, and user synchronization. It is intended for developers working on sign-in, user management, or multi-tenant applications, with guidance on authorization and safe webhook handling.
Key features
- 01Clerk authentication patterns
- 02Middleware and organization guidance
- 03Webhook verification and event handling
- 04User synchronization safeguards
- 05Route and resource authorization
Use cases
- 01Adding sign-in and sign-up
- 02Implementing organization-based access
- 03Synchronizing users through webhooks
- 04Securing server routes and actions
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/clerk-authin Claude Code to confirm it loaded.
Bundled filesreferences/detailed-guide.md
Details
From the project READMEClerk Authentication
Expert patterns for Clerk auth implementation, middleware, organizations, webhooks, and user sync
Detailed Guide
Read the detailed guide before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely.
When to Use
- User mentions or implies: adding authentication
- User mentions or implies: clerk auth
- User mentions or implies: user authentication
- User mentions or implies: sign in
- User mentions or implies: sign up
- User mentions or implies: user management
- User mentions or implies: multi-tenancy
- User mentions or implies: organizations
- User mentions or implies: sso
- User mentions or implies: single sign-on
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Guide snippets are independent alternatives/files, not one deployable module; duplicate default exports and omitted Prisma models/imports must be resolved in the actual project. Pin compatible Next.js/Clerk versions and check current middleware/proxy filenames. Authenticate each server route/action, validate inputs and authorize organization permissions/individual resources; client UI and org:admin do not grant global-user access. Verify webhook raw bytes first, then use a durable transactional event inbox keyed by Svix ID plus a domain ordering/tombstone policy; upsert alone does not prevent stale events resurrecting deleted users or overwriting newer state. Hard deletion must follow the application’s retention/foreign-key policy. Choose actual primary email rather than array order and allow phone-only identities. Use synthetic test instances and never log signing secrets/raw private payloads. See Clerk sync guidance and Svix raw payload verification.