CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/nuxt-v4/skills/nuxt-core/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, highly actionable Nuxt 4 reference with executable code throughout, clear sectioning, and a useful troubleshooting section. Its main weaknesses are dead progressive-disclosure references (the advertised reference files and templates/ are absent from the bundle), a dated version table that belongs in a reference file, and a non-compiling duplicate-declaration example.

Suggestions

Create the advertised bundle files (references/configuration-deep.md, references/routing-advanced.md, references/plugins-architecture.md, and templates/) or remove the 'When to Load References' and 'Templates Available' sections — currently they point at files that do not exist.

Move the time-sensitive version-requirements table and last-verified date into a reference file (or a version/compatibility section clearly marked as dated) and trim the inline body accordingly.

Fix the Dynamic Routes example so 'const userId' is declared once (use the computed form only), making every code sample copy-paste executable.

DimensionReasoningScore

Conciseness

The body is code-dominant and mostly lean, but it opens with a time-sensitive version-requirements table ('nuxt 4.0.0 / 4.2.x', 'Last Updated: 2025-12-28') that the guidelines explicitly penalize outside a deprecated/old-patterns section, includes a Secure Installation section that immediately delegates to another skill, and repeats the runtime-config rule in both Configuration and Anti-Patterns. This matches 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the minor-trim level of 4.

3 / 5

Actionability

Nearly everything is copy-paste ready: concrete commands ('bunx nuxi@latest init my-app', 'bunx nuxi typecheck') and complete code for config, middleware, SEO, and error handling. It falls short of 5 because the Dynamic Routes example declares 'const userId = route.params.id' and then 'const userId = computed(() => route.params.id)' in the same script block — a redeclaration that fails to compile, so not every example is executable as written.

4 / 5

Workflow Clarity

A logical progression (Quick Reference commands → config → routing → SEO → error handling) with a dedicated Troubleshooting section giving error-recovery guidance per symptom, and 'bunx nuxi typecheck' as a validation checkpoint. Not a 5 because there are no explicit validate-then-proceed feedback loops (the reference nature of the skill means steps are parallel topics rather than a gated sequence), and not a 3 because checkpoints and recovery paths are present.

4 / 5

Progressive Disclosure

The body has a well-written 'When to Load References' section pointing to 'references/configuration-deep.md', 'references/routing-advanced.md', and 'references/plugins-architecture.md', plus a 'templates/' directory — but none of these files exist in the bundle (no references/, scripts/, or assets/ directories are present). The advertised disclosure targets are dead, and the ~560-line body inlines the advanced configuration/routing/plugin detail that those missing files were meant to hold, matching anchor 2's 'content that clearly belongs in separate files is inlined'. It is not a 3 because the failure is not merely imperfect signaling — the referenced structure simply does not exist.

2 / 5

Total

13

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it pairs a concrete capability list with an explicit multi-scenario 'Use when:' clause full of framework-specific trigger terms. It sits just below top marks on specificity and trigger coverage because the 'what' is expressed as topic areas rather than discrete actions, and a few natural Nuxt terms are absent.

DimensionReasoningScore

Specificity

The description lists several specific areas ('project setup, configuration, routing, SEO, error handling, and directory structure') and names concrete artifacts ('nuxt.config.ts', 'useHead/useSeoMeta', 'error.vue', 'NuxtErrorBoundary'). It falls short of a 5 because the 'what' is framed as topic areas rather than a comprehensive list of concrete actions like the anchor's 'Extract text, fill forms, merge documents'.

4 / 5

Completeness

It clearly answers 'what' ('Nuxt 4 core framework fundamentals: project setup, configuration, routing, SEO, error handling, and directory structure') and 'when' with an explicit 'Use when:' clause followed by six concrete trigger scenarios. This matches the anchor-5 example structure of concrete what + explicit when; it is not a 4 because the 'when' is already highly specific and multi-trigger.

5 / 5

Trigger Term Quality

Natural trigger phrases are present and specific: 'creating new Nuxt 4 projects', 'configuring nuxt.config.ts', 'setting up routing and middleware', 'implementing SEO', 'handling errors with error.vue'. A few natural terms a user might say are missing from the description itself (e.g. 'layouts', 'NuxtLink', 'SSR', 'app directory'), matching anchor 4's 'good keyword coverage; a few natural terms missing' rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

'Nuxt 4 core framework fundamentals' carves a clear niche with distinct triggers (nuxt.config.ts, file-based routing, error.vue). Minor overlap risk remains with the sibling skills the body itself names (nuxt-server's middleware/API territory, nuxt-data's composables), e.g. 'setting up routing and middleware' could co-trigger with nuxt-server — matching anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

17

/

20

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

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (594 lines); consider splitting into references/ and linking

Warning

metadata_field

'metadata' should map string keys to string values

Warning

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

13

/

16

Passed

Repository

secondsky/claude-skills

Path

plugins/nuxt-v4/skills/nuxt-core/SKILL.md

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.