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
89
86%
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 clearly defines its scope (Nuxt 4 core fundamentals), lists specific capabilities, provides explicit trigger guidance via a 'Use when' clause, and includes a comprehensive keywords section. The description uses proper third-person voice and covers both high-level concepts and specific API/file references, making it highly effective for skill selection among many options.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: project setup, configuration, routing, SEO, error handling, and directory structure. The 'Use when' clause further enumerates specific tasks like configuring nuxt.config.ts, setting up routing and middleware, implementing SEO with useHead/useSeoMeta. | 3 / 3 |
Completeness | Clearly answers both 'what' (Nuxt 4 core framework fundamentals covering setup, config, routing, SEO, error handling, directory structure) and 'when' with an explicit 'Use when:' clause listing specific trigger scenarios. Also includes a dedicated Keywords section. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say, including framework name ('Nuxt 4'), specific file names ('nuxt.config.ts', 'error.vue'), API names ('useHead', 'useSeoMeta', 'definePageMeta', 'navigateTo'), component names ('NuxtErrorBoundary', 'NuxtLink'), and concepts ('file-based routing', 'middleware', 'runtime config'). | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Nuxt 4 specifically. The specific API names, file names, and component names (useHead, useSeoMeta, NuxtErrorBoundary, nuxt.config.ts) make it very unlikely to conflict with other framework skills like Vue, React, or even general Node.js skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong Nuxt 4 fundamentals skill with excellent actionability and progressive disclosure. Code examples are complete, executable, and cover the key patterns including important anti-patterns. The main weaknesses are moderate verbosity (the directory structure listing and version table could be trimmed) and lack of explicit multi-step workflows with validation checkpoints for operations like project setup or production builds.
Suggestions
Trim the directory structure section — Claude can infer what 'assets/' and 'plugins/' contain; focus annotations only on Nuxt 4-specific changes like the app/ srcDir shift.
Add a sequenced project setup workflow with validation steps (e.g., 1. Init → 2. Verify dev server starts → 3. Configure nuxt.config.ts → 4. Run typecheck) to improve workflow clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is generally well-structured but includes some content Claude already knows (e.g., basic Vue template syntax, what directories are for). The version requirements table and some inline comments add bulk. However, most content earns its place with Nuxt 4-specific patterns and anti-patterns. | 2 / 3 |
Actionability | Excellent actionability throughout — every section includes fully executable, copy-paste-ready code examples with proper TypeScript typing. Commands are specific (using bun), code blocks are complete Vue SFCs or config files, and anti-patterns show both wrong and correct approaches side by side. | 3 / 3 |
Workflow Clarity | The skill covers individual tasks well but lacks explicit multi-step workflows with validation checkpoints. Project setup is just a single command without a sequenced workflow. The troubleshooting section helps but there are no feedback loops for operations like build/deploy. For a fundamentals skill this is acceptable but not exemplary. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear 'When to Load References' section pointing to specific reference files with explicit trigger conditions. The skill serves as a well-organized overview with pointers to deep-dive documents (configuration-deep.md, routing-advanced.md, plugins-architecture.md), templates directory, and related skills. | 3 / 3 |
Total | 10 / 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 | |
- Repository
- secondsky/claude-skills
- Commit
88da5ff
- 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.