auth0-quickstart
auth0/agent-skills
Detect your framework and route to the right Auth0 authentication setup workflow.
What is auth0-quickstart?
Entry point for adding Auth0 authentication to any app. Detects your framework (React, Next.js, Vue, Angular, Express, Flask, etc.) and routes you to the appropriate framework-specific skill. Use this when you want to add login to your app but aren't sure which Auth0 SDK to use.
- Automatically detects your project framework from package.json and project files
- Routes to the correct framework-specific Auth0 skill (auth0-react, auth0-nextjs, auth0-vue, auth0-angular, auth0-express, auth0-flask, etc.)
- Guides Auth0 CLI installation and account setup
- Creates Auth0 applications with correct configuration for your framework type (SPA, Regular Web App, or Native)
- Provides environment variable setup and common mistake prevention
How to install auth0-quickstart
npx skills add https://github.com/auth0/agent-skills --skill auth0-quickstart- Auth0 account (free tier available)
- Auth0 CLI installed (brew install auth0/auth0-cli/auth0 on macOS/Linux)
- Node.js project with package.json, or equivalent framework project files
How to use auth0-quickstart
- 1.Run framework detection commands to identify your project type (check package.json or project files)
- 2.Install Auth0 CLI if not already installed
- 3.Run 'auth0 login' to authenticate with your Auth0 account
- 4.Create an Auth0 application using the appropriate type (SPA, Regular Web App, or Native) with the provided commands
- 5.Retrieve your Client ID and Client Secret from the created application
- 6.Use the framework-specific skill (auth0-react, auth0-nextjs, auth0-express, etc.) for the next steps
Use cases
- Adding login/authentication to a React, Vue, or Angular single-page application
- Setting up Auth0 in a Next.js or Express.js server-side application
- Configuring authentication for a React Native or Expo mobile app
- Migrating an existing app to Auth0 without knowing which SDK to use
- Creating Auth0 applications with proper callback URLs and application types for your framework
- Full-stack developers adding authentication to new or existing applications
- Frontend developers building SPAs or mobile apps
- Backend developers securing APIs with JWT validation
- Teams migrating from other auth providers to Auth0
auth0-quickstart FAQ
Tier 1 frameworks have dedicated skills. For Tier 2 frameworks (SvelteKit, Remix, Django, Rails, Laravel, Go, Spring Boot, iOS, Android, Flutter), use Auth0's official documentation linked in the skill.
No. SPAs use Client ID only. Client Secret is only needed for Regular Web Apps and backend APIs where you can securely store secrets.
For local development, use http://localhost:3000 for SPAs or http://localhost:3000/api/auth/callback for server apps. Update this in Auth0 Dashboard before deploying to production.
This skill sets up Auth0. For migrating users and code from other providers, use the auth0-migration skill instead.
Ensure Auth0 CLI is installed correctly (brew install auth0/auth0-cli/auth0), you have an Auth0 account, and your browser allows the authentication redirect.
Full instructions (SKILL.md)
Source of truth, from auth0/agent-skills.
name: auth0-quickstart description: > Use when adding Auth0 authentication to any app and unsure which SDK or skill to use. Detects the project's framework and routes to the right setup workflow — use this as the entry point even if the user just says "add login to my app" or "set up Auth0" without naming a framework. license: Apache-2.0 metadata: author: Auth0 support@auth0.com version: '1.0.0' openclaw: emoji: "\U0001F510" homepage: https://github.com/auth0/agent-skills requires: bins: - auth0 os: - darwin - linux install: - id: brew kind: brew package: auth0/auth0-cli/auth0 bins: [auth0] label: 'Install Auth0 CLI (brew)'
Auth0 Quickstart
Detect your framework and get started with Auth0 authentication.
Step 1: Detect Your Framework
Run this command to identify your framework:
# Check package.json dependencies (Node.js projects)
cat package.json | grep -E "react|next|vue|nuxt|angular|express|fastify|@nestjs|expo"
# Or check project files
ls -la | grep -E "angular.json|vue.config.js|next.config|app.json|Package.swift|build.gradle"
Framework Detection Table:
| Framework | Detection | Skill to Use |
|---|---|---|
| React (Vite/CRA) | "react" in package.json, no Next.js | auth0-react |
| Next.js | "next" in package.json | auth0-nextjs |
| Vue.js | "vue" in package.json, no Nuxt | auth0-vue |
| Nuxt | "nuxt" in package.json | auth0-nuxt |
| Angular | angular.json exists or "@angular/core" | auth0-angular |
| Express.js | "express" in package.json | auth0-express |
| Fastify (web app) | "fastify" in package.json, has @fastify/view | auth0-fastify |
| Fastify (API) | "fastify" in package.json, no view engine | auth0-fastify-api |
| React Native | "react-native" or "expo" in package.json | auth0-react-native |
| Flask | "flask" in requirements.txt, Pipfile, or pyproject.toml | auth0-flask |
| Node.js API | "express-oauth2-jwt-bearer" in package.json | express-oauth2-jwt-bearer |
| ASP.NET Core web app | *.csproj exists, has Views/ or Pages/ folder | auth0-aspnetcore-authentication |
Don't see your framework? See Tier 2 Frameworks below.
Step 2: Auth0 Account Setup
Install Auth0 CLI
macOS/Linux:
brew install auth0/auth0-cli/auth0
Windows:
scoop install auth0
# Or: choco install auth0-cli
Full installation guide: See CLI Reference
Login to Auth0
auth0 login
This opens your browser to authenticate with Auth0.
Step 3: Create Auth0 Application
Choose application type based on your framework:
Single Page Applications (React, Vue, Angular):
auth0 apps create --name "My App" --type spa \
--auth-method None \
--callbacks "http://localhost:3000" \
--logout-urls "http://localhost:3000" \
--metadata "created_by=agent_skills"
Regular Web Apps (Next.js, Nuxt, Express, Fastify):
auth0 apps create --name "My App" --type regular \
--callbacks "http://localhost:3000/api/auth/callback" \
--logout-urls "http://localhost:3000" \
--metadata "created_by=agent_skills"
Native Apps (React Native):
auth0 apps create --name "My App" --type native \
--auth-method None \
--callbacks "myapp://callback" \
--logout-urls "myapp://logout" \
--metadata "created_by=agent_skills"
Get your credentials:
auth0 apps list # Find your app
auth0 apps show <app-id> # Get client ID and secret
More CLI commands: See CLI Reference
Apply Branding (Optional)
After creating your application, apply branding so the Auth0 Universal Login page matches your app:
auth0 ul update \
--accent "#YOUR_BRAND_COLOR" \
--background "#YOUR_BACKGROUND_COLOR" \
--logo "https://your-app.com/logo.png" \
--favicon "https://your-app.com/favicon.ico"
This ensures users see your app's branding on the login screen instead of the default Auth0 branding. You can also use the acul-screen-generator skill for full custom login screen design.
Step 4: Use Framework-Specific Skill
Based on your framework detection, use the appropriate skill:
Tier 1 Frameworks (Dedicated Skills)
Frontend:
auth0-react- React SPAs (Vite, Create React App)auth0-nextjs- Next.js (App Router and Pages Router)auth0-vue- Vue.js 3 applicationsauth0-nuxt- Nuxt 3/4 applicationsauth0-angular- Angular 12+ applications
Backend:
auth0-express- Express.js web applicationsauth0-flask- Flask web applicationsauth0-fastify- Fastify web applicationsauth0-fastify-api- Fastify API authenticationexpress-oauth2-jwt-bearer- Node.js/Express API JWT Bearer validationauth0-aspnetcore-authentication- ASP.NET Core MVC, Razor Pages, Blazor Server web applications
Mobile:
auth0-react-native- React Native and Expo (iOS/Android)
Tier 2 Frameworks (Use Auth0 Docs)
Not yet available as separate skills. Use Auth0 documentation:
Frontend:
Backend:
Mobile:
Migration from Other Providers
Migrating from another auth provider? Use the auth0-migration skill.
The migration skill covers:
- User export from Firebase, Cognito, Supabase, Clerk, etc.
- Bulk import to Auth0
- Code migration patterns (before/after examples)
- JWT validation updates
- Gradual migration strategies
Reference Documentation
Environment Variables
Framework-specific environment variable setup:
Auth0 Concepts
Core concepts and troubleshooting:
CLI Commands
Complete Auth0 CLI reference:
Common Mistakes
| Mistake | Fix |
|---|---|
| Wrong application type | SPAs need "Single Page Application", server apps need "Regular Web Application", mobile needs "Native" |
| Callback URL not configured | Add your app's callback URL to Allowed Callback URLs in Auth0 Dashboard |
| Using wrong credentials | Client Secret only needed for Regular Web Apps, not SPAs |
| Hardcoding credentials in code | Always use environment variables, never commit secrets to git |
| Not testing locally first | Set up localhost URLs in Auth0 before deploying to production |
| Mixing application types | Don't use SPA SDK for server-side apps or vice versa |
Related Skills
Core Integration
auth0-migration- Migrate from other auth providers
SDK Skills
auth0-spa-js- SPA integrationauth0-react- React SPA integrationauth0-nextjs- Next.js integrationauth0-vue- Vue.js integrationauth0-nuxt- Nuxt 3/4 integrationauth0-angular- Angular integrationauth0-express- Express.js integrationauth0-flask- Flask web app integrationauth0-fastify- Fastify web app integrationauth0-fastify-api- Fastify API integrationexpress-oauth2-jwt-bearer- Node.js/Express API JWT Bearer validationauth0-react-native- React Native CLI (bare workflow) integrationauth0-expo- Expo (managed workflow) integrationauth0-android- Android (Kotlin/Java) integrationauth0-swift- iOS/macOS (Swift) integrationauth0-fastapi-api- FastAPI API authenticationauth0-aspnetcore-authentication- ASP.NET Core web app authenticationauth0-aspnetcore-api- ASP.NET Core API authentication
Advanced Features
auth0-mfa- Multi-Factor Authentication
References
Related skills
More from auth0/agent-skills and the wider catalog.

auth0-react
Add Auth0 authentication to React SPAs with login, logout, protected routes, and user sessions.

auth0-react-native
>

auth0-vue
>

auth0-angular
>

xiaohongshu-skills
|

capability-evolver
Self-evolution engine for AI agents that analyzes runtime history and autonomously applies protocol-constrained improvements via local Proxy mailbox.