Use when implementing auth in Nuxt apps with @onmax/nuxt-better-auth - provides useUserSession composable, server auth helpers, route protection, and Better Auth plugins integration.
94
93%
Does it follow best practices?
Impact
94%
1.25xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%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, well-crafted description that clearly identifies the specific package, framework, and concrete capabilities. It opens with an explicit 'Use when' trigger clause and lists distinct actions, making it easy for Claude to select this skill precisely when needed. The inclusion of the package name and specific composable/helper names provides excellent disambiguation.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'useUserSession composable, server auth helpers, route protection, and Better Auth plugins integration' — these are distinct, concrete capabilities. | 3 / 3 |
Completeness | Explicitly answers both what ('provides useUserSession composable, server auth helpers, route protection, and Better Auth plugins integration') and when ('when implementing auth in Nuxt apps with @onmax/nuxt-better-auth') with a clear 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes highly relevant natural keywords a user would say: 'auth', 'Nuxt', '@onmax/nuxt-better-auth', 'useUserSession', 'route protection', 'Better Auth'. These cover the specific package name, framework, and common auth-related terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a specific package (@onmax/nuxt-better-auth) within a specific framework (Nuxt). Very unlikely to conflict with generic auth skills or other framework-specific auth skills. | 3 / 3 |
Total | 12 / 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 well-structured skill that excels at conciseness and progressive disclosure. It serves as an effective index/overview that directs Claude to the right reference file based on the task at hand, with useful quick-reference code snippets inline. The main weakness is the lack of explicit multi-step workflows with validation checkpoints in the main skill body, though these may exist in the referenced files.
Suggestions
Add a brief sequenced setup workflow (e.g., 1. Install module → 2. Configure env vars → 3. Verify with test route) to improve workflow clarity for first-time setup tasks.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. It avoids explaining what Better Auth is or how authentication works conceptually. Every section serves a purpose: when to use, where to find details, quick reference code. The token budget note at the bottom is a nice touch. | 3 / 3 |
Actionability | The Quick Reference section provides fully executable, copy-paste ready code snippets for the three most common use cases (client auth, server auth, route protection). The guidance table and loading checklist make it immediately clear what to do for any given task. | 3 / 3 |
Workflow Clarity | The skill clearly identifies when to load which reference files and provides a task-based checklist, but it lacks explicit multi-step workflows with validation checkpoints. For example, there's no sequenced setup workflow (install → configure → verify) or error recovery guidance. The content delegates workflows to reference files without showing the overall sequence. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure structure. The main skill is a concise overview with a well-organized table of 8 reference files, each clearly described. The loading checklist with task-based guidance for when to load each file is exemplary. References are one level deep and clearly signaled. | 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.
3110745
Table of Contents
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.