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 skill description. It opens with an explicit 'Use when...' trigger clause naming the specific framework and package, then lists four concrete capabilities. The specificity of the package name and Nuxt-specific terminology make it highly distinctive and easy for Claude to match correctly.
| 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 users would say: 'auth', 'Nuxt', '@onmax/nuxt-better-auth', 'useUserSession', 'route protection', 'Better Auth'. These cover the package name, framework, and key concepts a developer would mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — scoped to a specific package (@onmax/nuxt-better-auth) within a specific framework (Nuxt), with named composables and features. Very unlikely to conflict with generic auth or other framework 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 only notable gap is the lack of explicit multi-step workflows with validation checkpoints in the main file, though this may be covered in the reference files.
Suggestions
Consider adding a brief 'Getting Started' workflow sequence (e.g., '1. Install module → 2. Configure nuxt.config.ts → 3. Add BETTER_AUTH_SECRET env var → 4. Verify with useUserSession()') to improve workflow clarity in the main file.
| 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 clearly signals when to load which reference files and provides a task-based checklist, but there's no explicit multi-step workflow with validation checkpoints. For installation or setup flows, the user is directed to reference files without seeing the sequence of steps (install → configure → verify). The main file doesn't outline an end-to-end workflow. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a concise overview, well-organized table of reference files, task-based loading checklist, and one-level-deep references. Content is appropriately split across 8 focused reference files with clear descriptions of what each contains. | 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.
00fb59d
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.