auth0-nextjs
Use when adding authentication to Next.js applications with both server and client-side auth - supports App Router and Pages Router with @auth0/nextjs-auth0 SDK
86
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 100%
↑ 1.08xAgent success when using this skill
Validation for skill structure
Discovery
72%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description has strong distinctiveness and good trigger terms due to specific technology mentions (Auth0, Next.js, specific SDK). However, it lacks concrete action verbs describing what the skill actually does - it reads more like a feature list than a capability description. The 'Use when' clause exists but focuses on context rather than user intent triggers.
Suggestions
Add specific actions the skill performs, e.g., 'Configures login/logout flows, sets up protected routes, manages user sessions, handles authentication callbacks'
Expand the 'Use when' clause with user intent triggers like 'when user asks about login, logout, protecting pages, or managing auth state in Next.js'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (authentication, Next.js) and mentions some capabilities (server and client-side auth, App Router and Pages Router support), but doesn't list concrete actions like 'configure login flows', 'set up protected routes', or 'handle session management'. | 2 / 3 |
Completeness | Has a 'Use when' clause which is good, but the 'what' portion is weak - it describes what the skill supports rather than what actions it performs. The 'when' is present but could be more explicit about trigger scenarios. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'authentication', 'Next.js', 'auth', 'App Router', 'Pages Router', '@auth0/nextjs-auth0', and 'SDK'. Good coverage of terms developers would naturally use when seeking auth help. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche: Auth0 authentication specifically for Next.js with the @auth0/nextjs-auth0 SDK. Unlikely to conflict with generic auth skills or other framework-specific auth skills due to the explicit technology stack mentioned. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill that provides clear step-by-step guidance for Auth0 Next.js integration. Its strengths are the executable code examples, clear workflow, and excellent progressive disclosure to reference materials. Minor verbosity in showing duplicate code patterns and the extensive common mistakes table slightly reduce token efficiency.
Suggestions
Consolidate the Next.js 15 and 16 middleware examples by noting they're identical and only showing the code once, with a note that Next.js 16 also supports proxy.ts as an alternative
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some redundancy, such as showing nearly identical middleware code for Next.js 15 and 16 Option 1, and the optional Auth0Provider section could be more condensed. The common mistakes table is valuable but lengthy. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples throughout - from installation commands to complete TypeScript implementations for auth0 client, middleware, provider setup, and UI components. All code is concrete and runnable. | 3 / 3 |
Workflow Clarity | Clear 6-step numbered workflow with explicit sequencing from installation through testing. Each step builds logically on the previous one, and the final step includes a concrete validation checkpoint (test the login flow). | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise quick start in the main file and clear one-level-deep references to detailed documentation (Setup Guide, Integration Guide, API Reference). The 'Common Use Cases' section provides well-signaled links to specific sections in reference docs. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.