auth0-nextjs
Use when adding authentication to Next.js applications (login, logout, protected pages, middleware, server components) - supports App Router and Pages Router with @auth0/nextjs-auth0 SDK.
90
87%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
89%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 is a strong skill description that clearly communicates when to use it (authentication in Next.js) and includes excellent trigger terms covering both user-facing concepts (login, logout) and technical specifics (App Router, @auth0/nextjs-auth0 SDK). The main weakness is that the capabilities listed are more feature categories than concrete actions, which slightly reduces specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Next.js authentication) and lists some actions (login, logout, protected pages, middleware, server components), but these are more feature areas than concrete actions like 'configure middleware' or 'implement session handling'. | 2 / 3 |
Completeness | Explicitly answers both what (authentication for Next.js with Auth0 SDK) and when ('Use when adding authentication to Next.js applications') with clear trigger guidance at the start of the description. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'authentication', 'login', 'logout', 'protected pages', 'middleware', 'server components', 'App Router', 'Pages Router', '@auth0/nextjs-auth0', and 'Next.js' - these match how developers naturally describe auth needs. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific technology stack (Next.js + Auth0 SDK), router types (App Router, Pages Router), and authentication-specific triggers - unlikely to conflict with generic auth or other framework skills. | 3 / 3 |
Total | 11 / 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 skill with excellent actionability and progressive disclosure. The workflow is clear with proper sequencing for both Next.js 15 and 16. Minor verbosity in some sections (When NOT to Use, repeated middleware patterns) prevents a perfect conciseness score, but overall the skill effectively teaches Auth0 integration.
Suggestions
Consolidate the Next.js 15 and 16 middleware examples by showing the shared pattern once and noting only the differences (proxy.ts option for v16)
Consider moving the 'When NOT to Use' section to a reference file or condensing to a single sentence, as Claude can infer appropriate SDK choices
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary explanations like the 'When NOT to Use' section and verbose middleware examples that repeat similar patterns. The common mistakes table is valuable but could be more condensed. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples throughout. Environment setup, middleware configuration, client components, and server-side methods all have concrete, working code snippets with clear file paths. | 3 / 3 |
Workflow Clarity | Clear 6-step numbered workflow with explicit checkpoints. Includes detection step for project structure, version-specific guidance (Next.js 15 vs 16), and a final test step. The sequence is logical and complete. | 3 / 3 |
Progressive Disclosure | Excellent structure with quick start in main file and detailed documentation clearly signaled with one-level-deep references to setup.md, integration.md, and api.md. Quick Reference section provides scannable summary with links to detailed guides. | 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.
- Repository
- auth0/agent-skills
- Commit
fbcbfb1
- 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.