auth0
Auth0 skills for setting up authentication, migrating from other providers, implementing Multi-Factor Authentication (MFA), framework-specific SDK integrations and CLI.
Installation
Via Codex / ChatGPT desktop:
Add the repository marketplace from .agents/plugins/marketplace.json to the
Plugins UI, then install Auth0. It tracks the published main snapshot. The
public plugin directory requires submission and approval through the
OpenAI plugin submission portal.
Via Claude Code:
First, add the Auth0 marketplace if you haven't already:
/plugin marketplace add auth0/agent-skills
Then install the plugin:
/plugin install auth0@auth0-agent-skills
Via Skills CLI:
npx skills add auth0/agent-skills/plugins/auth0
Via an Agent Plugins-compatible client:
Load the plugins/auth0 directory using the client's plugin install flow.
Agent Plugins defines the portable package format,
not a universal install command.
Skills
| Skill | Description | Documentation |
|---|---|---|
| auth0 | Adds Auth0 authentication to any app. Covers 36+ frameworks (React, Next.js, React Router, Vue, Angular, Express, Flask, FastAPI, Spring Boot, Swift, Android, Kotlin Multiplatform, Flutter, Laravel, Go, PHP, .NET MAUI, ASP.NET Core, React Native, Expo, Ionic, and more), MFA, Organizations, Universal Portals for hosted account and organization self-service, Vercel native integration, custom domains, ACUL screen generation, branding, debugging auth errors, security best practices, running a tenant security & configuration audit (CheckMate), a plan-aware tenant health check, and migration from other providers. | SKILL.md |
Forcing the skill with /auth0
Auto-detection is reliable on capable models. On a smaller/faster model in a session with many other skills installed, the assistant can occasionally miss the trigger — most often on open-ended questions ("how do I…?") rather than direct instructions. When that happens, name the skill explicitly:
/auth0 how do I configure brand colors in Auth0?
Naming the skill removes the selection step entirely, so it always activates.
Migrating from the individual skills
Earlier versions shipped one skill per SDK/framework (auth0-react,
auth0-nextjs, express-oauth2-jwt-bearer, …). These are now consolidated
into the single auth0 skill above, which routes to the same guidance by
detecting your framework. Plugin/marketplace installs swap in the consolidated
skill on the next update with nothing to do. If you referenced an old skill by
name — in your CLAUDE.md, another skill's requires.skills, or any
instruction file — those names no longer exist and the reference will dangle;
replace them with auth0. See the repository README
for full migration details.