nuxt-core
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
Does it follow best practices?
Validation for skill structure
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 provides specific capabilities, explicit trigger guidance with a 'Use when:' clause, and comprehensive keywords that users would naturally use. The description is well-structured, uses third person voice, and clearly distinguishes itself as a Nuxt 4-specific skill.
| 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 covering setup, config, 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 files ('nuxt.config.ts'), concepts ('file-based routing', 'middleware'), and specific APIs ('useHead', 'useSeoMeta', 'definePageMeta', 'NuxtLink'). The Keywords section provides comprehensive trigger coverage. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche targeting 'Nuxt 4 core framework fundamentals' specifically. The combination of framework version (Nuxt 4), specific files (nuxt.config.ts, error.vue), and APIs (useHead, useSeoMeta) creates a unique fingerprint unlikely to conflict with other 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 file that demonstrates excellent technical writing. It provides comprehensive Nuxt 4 coverage with executable code, clear directory structures, comparison tables, and explicit anti-patterns. The progressive disclosure is well-implemented with clear pointers to reference files and related skills.
| 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 | Clear sequences are provided where needed (project setup commands, troubleshooting steps). The anti-patterns section explicitly shows wrong vs correct approaches with explanations. Middleware examples include the critical 'return' requirement. | 3 / 3 |
Progressive Disclosure | Excellent structure with a 'When to Load References' section pointing to deeper documentation files. Content is well-organized with clear sections, and appropriately references templates and related skills without nesting references deeply. | 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 — 13 / 16 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 |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 13 / 16 Passed | |
- Reviewed
Table of Contents
Is this your skill?
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.