nextauth-skill
Set up NextAuth.js v5 (Auth.js) with providers, callbacks (jwt, session, signIn), adapter pattern (Prisma/Drizzle), middleware protection, session management, and custom pages.
87
85%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
82%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, technically specific description that clearly identifies the technology (NextAuth.js v5/Auth.js) and lists concrete capabilities. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill over others. The technical terminology is appropriate for the developer audience.
Suggestions
Add a 'Use when...' clause with trigger phrases like 'Use when implementing authentication in Next.js, setting up Auth.js, configuring NextAuth providers, or protecting routes with middleware'
Consider adding common user phrasings like 'login', 'authentication', 'sign in/sign up', 'protected routes' to capture more natural language queries
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Set up NextAuth.js v5', 'providers', 'callbacks (jwt, session, signIn)', 'adapter pattern (Prisma/Drizzle)', 'middleware protection', 'session management', and 'custom pages'. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance explaining when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'NextAuth.js', 'Auth.js', 'v5', 'Prisma', 'Drizzle', 'jwt', 'session', 'middleware', 'callbacks' - these are terms developers naturally use when seeking authentication help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific technology stack (NextAuth.js v5/Auth.js) and version-specific features; unlikely to conflict with generic auth skills or other framework-specific authentication skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that provides comprehensive, executable NextAuth.js v5 setup guidance. The code examples are complete and well-organized, covering all major patterns from basic config to custom pages. The main weakness is the lack of explicit validation steps or troubleshooting guidance for verifying the auth implementation works correctly.
Suggestions
Add a validation checklist after setup (e.g., 'Verify: 1. Visit /api/auth/session - should return null, 2. Sign in via /auth/signin, 3. Revisit /api/auth/session - should show user data')
Include common error scenarios and their solutions (e.g., 'If you see CSRF token mismatch, ensure AUTH_URL matches your actual URL')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only necessary configuration and code examples without explaining basic concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | All code examples are fully executable and copy-paste ready, from the scaffold commands to complete TypeScript configurations. The skill provides specific file paths, complete implementations, and working examples for every pattern. | 3 / 3 |
Workflow Clarity | While the project structure and patterns are well-organized, the skill lacks explicit validation checkpoints or feedback loops. There's no guidance on verifying the auth setup works correctly or troubleshooting common issues during implementation. | 2 / 3 |
Progressive Disclosure | The skill is well-structured with clear sections progressing from prerequisites to scaffold to patterns. References to related skills (prisma-schema-starter, drizzle-starter, jwt-auth-skill) are one level deep and clearly signaled in the Integration Notes section. | 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- achreftlili/deep-dev-skills
- Commit
181fcbc
- 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.