Nuxt 4 core framework fundamentals: project setup, configuration, routing, SEO, error handling, and directory structure. Use when: creating new Nuxt 4 projects, configuring nuxt.config.ts, setting up routing and middleware, implementing SEO with useHead/useSeoMeta, handling errors with error.vue and NuxtErrorBoundary, or understanding Nuxt 4 directory structure. Keywords: Nuxt 4, nuxt.config.ts, file-based routing, pages directory, definePageMeta, useHead, useSeoMeta, error.vue, NuxtErrorBoundary, middleware, navigateTo, NuxtLink, app directory, runtime config
98
100%
Does it follow best practices?
Impact
99%
1.50xAverage 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 an excellent skill description that follows best practices. It uses third person voice, provides specific concrete actions, includes an explicit 'Use when:' clause with detailed scenarios, and offers comprehensive keyword coverage. The description clearly distinguishes itself as Nuxt 4-specific with version and API-specific terminology.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'project setup, configuration, routing, SEO, error handling, and directory structure' with detailed examples like 'configuring nuxt.config.ts', 'implementing SEO with useHead/useSeoMeta', 'handling errors with error.vue and NuxtErrorBoundary'. | 3 / 3 |
Completeness | Clearly answers both what ('core framework fundamentals: project setup, configuration, routing, SEO, error handling') AND when with explicit 'Use when:' clause listing specific scenarios like 'creating new Nuxt 4 projects', 'configuring nuxt.config.ts', 'implementing SEO'. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say including framework name 'Nuxt 4', config file 'nuxt.config.ts', specific APIs 'useHead', 'useSeoMeta', 'definePageMeta', components 'NuxtLink', 'NuxtErrorBoundary', and concepts 'file-based routing', 'pages directory', 'middleware'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche targeting 'Nuxt 4' specifically, with version-specific triggers and framework-specific terminology that would not conflict with general Vue, React, or other framework skills. | 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 document that efficiently covers Nuxt 4 fundamentals with excellent organization. It provides actionable, executable code examples throughout while maintaining conciseness. The progressive disclosure is well-implemented with clear signposting to reference documents, and the anti-patterns section adds significant value by showing common mistakes with corrections.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables for version requirements, code blocks for examples, and avoiding explanations of concepts Claude already knows. Every section provides actionable information without padding. | 3 / 3 |
Actionability | Provides fully executable code examples throughout - from project creation commands to complete component implementations. Code is copy-paste ready with proper TypeScript typing and real-world patterns. | 3 / 3 |
Workflow Clarity | Multi-step processes are clearly sequenced (e.g., project setup commands, middleware implementation flow). The troubleshooting section provides clear validation steps, and anti-patterns section explicitly shows wrong vs correct approaches with explanations. | 3 / 3 |
Progressive Disclosure | Excellent structure with a 'When to Load References' section that clearly signals when to access deeper documentation. Content is appropriately split with references to related skills and templates directory for additional resources. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (581 lines); consider splitting into references/ and linking | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
90d6bd7
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.