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.
89
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 and covers the domain well with natural trigger terms. Its main weakness is that the capabilities are listed more as feature areas rather than concrete actions (e.g., 'login, logout, protected pages' rather than 'configure auth routes, wrap components with session providers, set up middleware guards'). Overall it would perform well in skill selection scenarios.
Suggestions
Rephrase feature areas as concrete actions, e.g., 'Configures Auth0 authentication routes, protects pages with session middleware, wraps server components with auth guards' instead of listing 'login, logout, protected pages'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (authentication in Next.js) and lists some actions (login, logout, protected pages, middleware, server components), but these are more like feature areas than concrete actions. It doesn't describe specific operations like 'configure auth middleware', 'wrap components with session providers', or 'set up callback routes'. | 2 / 3 |
Completeness | Explicitly answers both 'what' (adding authentication to Next.js apps with Auth0 SDK, supporting login/logout/protected pages/middleware/server components) and 'when' (starts with 'Use when adding authentication to Next.js applications'). The 'Use when...' clause is clear and explicit. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'authentication', 'login', 'logout', 'protected pages', 'middleware', 'server components', 'Next.js', 'App Router', 'Pages Router', '@auth0/nextjs-auth0'. These are terms users would naturally use when seeking auth help in Next.js. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — it targets a specific SDK (@auth0/nextjs-auth0), a specific framework (Next.js), and a specific domain (authentication). The combination of Auth0 + Next.js + specific router types makes it very unlikely to conflict with other 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, highly actionable skill that provides a clear 6-step workflow with executable code for every stage of Auth0 Next.js integration. Its main weakness is some redundancy—the Next.js 16 middleware Option 1 duplicates the Next.js 15 block verbatim, and the Quick Reference section repeats earlier content. The progressive disclosure is excellent with clear pointers to detailed reference files.
Suggestions
Eliminate the duplicated middleware code block for Next.js 16 Option 1 by noting it's identical to the Next.js 15 configuration rather than repeating it.
Trim the Quick Reference section to only include information not already covered in the workflow steps, or remove it entirely since the workflow is already a clear reference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but has notable redundancy: the middleware configuration for Next.js 16 Option 1 is identical to the Next.js 15 block, and the Quick Reference section largely repeats information already covered in the workflow. The Common Mistakes table and env setup are valuable but some explanatory text could be tightened. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code for every step: installation command, environment variables, Auth0Client setup, middleware configuration, provider wrapping, and client component. Commands like `openssl rand -hex 32` and specific file paths make guidance concrete and immediately usable. | 3 / 3 |
Workflow Clarity | The 6-step workflow is clearly sequenced with logical progression from install → configure → create client → add context → add UI → test. The skill includes important decision points (detect src/ directory, Next.js 15 vs 16) and a final verification step (Step 6: test the login flow). The Common Mistakes table serves as an effective validation checklist. | 3 / 3 |
Progressive Disclosure | The skill provides a clear quick-start overview inline with well-signaled one-level-deep references to Setup Guide, Integration Guide, and API Reference for detailed content. Common use cases link directly to specific sections in reference files. Content is appropriately split between the overview and detailed documentation. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 Passed | |
- Repository
- auth0/agent-skills
- Commit
9777204
- 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.