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 skill description that clearly identifies the specific package, framework, and concrete capabilities. It includes an explicit 'Use when...' trigger clause and uses third-person voice throughout. The specificity of the package name and Nuxt-specific composables make it highly distinctive and easy for Claude to select appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'useUserSession composable', 'server auth helpers', 'route protection', and 'Better Auth plugins integration' — these are concrete, named capabilities. | 3 / 3 |
Completeness | Explicitly answers both what ('provides useUserSession composable, server auth helpers, route protection, and Better Auth plugins integration') and when ('Use when implementing auth in Nuxt apps with @onmax/nuxt-better-auth') with a clear 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'auth', 'Nuxt apps', '@onmax/nuxt-better-auth', 'useUserSession', 'route protection', 'Better Auth'. A user working with this specific package or auth in Nuxt would naturally use these terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a specific package (@onmax/nuxt-better-auth) within a specific framework (Nuxt), making it very unlikely to conflict with generic auth skills or other framework-specific 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 token efficiency and progressive disclosure. The main file serves as an effective index with actionable quick-reference code snippets and clear navigation to detailed reference files. The main weakness is the lack of explicit multi-step workflows with validation checkpoints, particularly for initial setup or common integration scenarios.
Suggestions
Add a brief sequenced setup workflow (e.g., 1. Install module → 2. Configure env vars → 3. Add auth config → 4. Verify with test login) to improve workflow clarity for first-time setup tasks.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. It avoids explaining what auth is or how Nuxt works, assumes Claude's competence, and keeps the main file to ~300 tokens with clear pointers to reference files. The 'Loading Files' checklist with explicit 'DO NOT load all files at once' is a smart token-saving mechanism. | 3 / 3 |
Actionability | The Quick Reference section provides fully executable, copy-paste-ready code snippets for the three most common patterns (client auth, server auth, route protection). The key concepts table gives concrete API signatures. Detailed guidance is deferred to reference files appropriately. | 3 / 3 |
Workflow Clarity | The skill provides clear task-to-file mapping via the checklist, but lacks explicit multi-step workflows with validation checkpoints. For instance, there's no sequenced setup workflow (install → configure → verify auth works → protect routes) which would be valuable for initial setup. The loading checklist is helpful but is more of a navigation aid than a workflow. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a concise overview, well-organized reference table, and clearly signaled one-level-deep references. The task-based checklist for loading files is particularly well done, making it easy to find the right reference for any given task. | 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.
48efc7a
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.