What problem does it solve? Setting up authentication in a Convex app involves choosing a provider, wiring backend config, client providers, environment variables, and protected functions, and getting any step wrong leaves the app silently unauthenticated. This Skill guides the full setup so Convex actually validates user sessions end to end. ## Core Features & Use Cases - Provider Selection Guidance: Detects or asks which auth provider to use among Convex Auth, Clerk, WorkOS AuthKit, Auth0, or a custom JWT provider, based on repo signals like dependencies and existing config files. - Provider-Specific References: Ships detailed reference files for each provider covering installation, convex/auth.config.ts setup, environment variables, gotchas, and validation steps. - Secure Backend Patterns: Enforces server-side identity checks with ctx.auth.getUserIdentity() instead of trusting client-provided user IDs, and adds authorization checks only where needed. - Use Case: You are building a Next.js app on Convex and need login with Clerk. The Skill walks through activating the Clerk Convex integration, configuring convex/auth.config.ts, wrapping the app in ClerkProvider and ConvexProviderWithClerk, and verifying protected queries return data after sign-in. ## Quick Start Set up authentication for my Convex app, figure out the right provider from my repo, and wire up login, protected functions, and user identity mapping.