Agent skill · software engineering · aiskillstore
convex-setup-auth
Sets up Convex authentication with user management, identity mapping, and access control. Use this skill when adding login or signup to a Convex app, configuring Convex Auth, Clerk, WorkOS AuthKit, Auth0, or custom JWT providers, wiring auth.config.ts, protecting queries and mutations with ctx.auth.getUserIdentity(), creating a users table with identity mapping, or setting up role-based access control, even if the user just says "add auth" or "make it require login.
Why this skill is useful
Provides specific setup instructions and integration patterns for multiple authentication providers in Convex that the AI wouldn't reliably generate on its own.
What it needs
Requires @auth0/*, @clerk/*, @workos-inc/* installed locally. Requires auth0, clerk, convex, workos account access. About 4k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Convex Authentication Setup Implement secure authentication in Convex with user management and access control. When to Use Setting up authentication for the first time Implementing user management (users table, identity mapping) Creating authentication helper functions Setting up auth providers (Convex Auth, Clerk, WorkOS AuthKit, Auth0, custom JWT) When Not to Use Auth for a non-Convex backend Pure OAuth/OIDC documentation without a Convex implementation Debugging unrelated bugs that happen to surface near auth code The auth provider is already fully configured and the user only needs a one-line fix First Step: Choose the Auth Provider Convex supports multiple authentication approaches. Do not assume a provider. Before writing setup code: 1. Ask the user which auth solution they want, unless the repository already makes it obvious 2. If the repo already uses a provider, continue with that provider unless the user wants to switch 3. If the user has not chosen a provider and the repo does not make it obvious, ask before proceeding Common options: Convex Auth - good default when the user wants auth handled directly in Convex Clerk - use when the app already uses Clerk or the user wants Clerk's hosted auth features WorkOS AuthKit - use when the app already uses WorkOS or the user wants AuthKit specifically Auth0 - use when the app already uses Auth0 Custom JWT provider - use when integrating an existing auth system not covered above Look for signals in the repo before asking: Dependencies such as @clerk/, @workos-inc/, @auth0/, or Convex Auth packages Existing files such as convex/auth.config.ts, auth middleware, provider wrappers, or login components Environment variables that clearly point at a provider After Choosing a Provider Read the provider's official guide and the matching local reference file: Convex Auth: official docs, then references/convex-auth.md Clerk: official docs, then references/clerk.md WorkOS AuthKit: official docs, then references/workos-authkit. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/convex-setup-auth