Use when working on Nuxt 4+ projects - provides server routes, file-based routing, middleware patterns, Nuxt-specific composables, and configuration with latest docs. Covers h3 v1 helpers (validation, WebSocket, SSE) and nitropack v2 patterns. Updated for Nuxt 4.3+.
100
100%
Does it follow best practices?
Impact
100%
1.51xAverage 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 its domain (Nuxt 4+ projects), lists specific capabilities (server routes, file-based routing, middleware, composables, h3 helpers, nitropack patterns), and opens with an explicit 'Use when' trigger clause. The version specificity (Nuxt 4.3+, h3 v1, nitropack v2) makes it highly distinctive and unlikely to conflict with other skills. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and capabilities: server routes, file-based routing, middleware patterns, Nuxt-specific composables, configuration, h3 v1 helpers (validation, WebSocket, SSE), and nitropack v2 patterns. These are concrete, identifiable features. | 3 / 3 |
Completeness | Explicitly answers both 'what' (server routes, file-based routing, middleware patterns, composables, configuration, h3 helpers, nitropack patterns) and 'when' ('Use when working on Nuxt 4+ projects') with a clear trigger clause at the start. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Nuxt 4+', 'server routes', 'file-based routing', 'middleware', 'composables', 'h3', 'nitropack', 'WebSocket', 'SSE', 'validation'. These cover the terms a developer working with Nuxt would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Nuxt 4+ specifically, with version-specific details (h3 v1, nitropack v2, Nuxt 4.3+). Unlikely to conflict with generic Vue, Node.js, or other framework skills due to the precise framework and version targeting. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill file that serves as an efficient index/router for Nuxt 4+ development guidance. It excels at progressive disclosure with clearly signaled references, provides a concrete quick-start example, and respects token budget by keeping the main file minimal while pointing to detailed sub-files. The migration table and conditional loading checklist add significant practical value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and well-organized. It avoids explaining what Nuxt is or how frameworks work, assumes Claude's competence, and keeps the main file to ~300 tokens with clear pointers to sub-files. The token efficiency note at the bottom is a nice touch. | 3 / 3 |
Actionability | Provides a concrete, executable Quick Start example with a real server route using Zod validation. The checklist of when to load each reference file gives specific, actionable guidance. The migration table provides concrete old-vs-new mappings. | 3 / 3 |
Workflow Clarity | For a skill that serves as a routing/index file, the workflow is clear: identify your task, load the relevant reference file, follow the patterns. The checklist format with conditional loading instructions provides an unambiguous decision process. This is not a destructive/batch operation skill, so validation checkpoints aren't required. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a concise overview, well-signaled one-level-deep references to specific sub-files, clear cross-references to other skills (vue, nuxt-ui, nuxthub, etc.), and explicit instructions to load only relevant files. Navigation is easy and well-organized. | 3 / 3 |
Total | 12 / 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.