CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nuxt-production

| Nuxt 4 production optimization: hydration, performance, testing with Vitest, deployment to Cloudflare/Vercel/Netlify, and v4 migration. Use when: debugging hydration mismatches, optimizing performance and Core Web Vitals, writing tests with Vitest, deploying to Cloudflare Pages/Workers/Vercel/Netlify, or migrating from Nuxt 3 to Nuxt 4.

Quality

76%

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-production/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 highly actionable, code-dense body with excellent reference signaling via the 'When to Load References' section and a well-sequenced migration guide. Its weaknesses are redundancy (hydration, lazy hydration, and version-feature content repeated across sections), inline duplication of material that also lives in the reference files, and absent validation checkpoints in the migration, deployment, and destructive-cleanup workflows.

Suggestions

Consolidate the three repeated hydration-mismatch treatments (cause table, 'Non-Deterministic SSR' anti-pattern, and Troubleshooting) into one section and point to references/hydration.md, removing the duplicated lazy-hydration demo in the v4.1 features block since it reappears under Performance Optimization.

Add validation checkpoints to the multi-step workflows: after each migration step include a verification command (e.g., 'bun run build' or 'bun vitest run'), and add a post-deploy smoke check before the destructive 'rm -rf .nuxt .output node_modules/.vite' cleanup.

Slim the inline deployment and testing sections to the quick-start essentials (one preset example, one test example) and defer full configs — wrangler.toml bindings, NuxtHub setup, e2e tests — to the existing reference files, so SKILL.md reads as an overview rather than duplicating them.

DimensionReasoningScore

Conciseness

The body is mostly dense code and tables with little concept-explanation fluff, but it duplicates content: hydration mismatch causes appear in three places (the cause table, the 'Non-Deterministic SSR' anti-pattern, and Troubleshooting), lazy hydration is demonstrated twice (v4.1 features and Performance), and 'What's New' repeats the performance section. This matches 'mostly efficient but could be tightened' rather than the minor-trimming of anchor 4.

3 / 5

Actionability

Provides extensive copy-paste-ready guidance: full vitest.config.ts, wrangler.toml with D1/KV bindings, routeRules caching config, mountSuspended test examples, and concrete migration commands. Minor gaps keep it from 5: the lazy-loading script block declares 'const HeavyChart' twice (would fail if pasted verbatim), and wrangler.toml uses 'xxx-xxx-xxx' placeholder IDs.

4 / 5

Workflow Clarity

The migration section has a clear 5-step sequence and troubleshooting gives per-symptom checklists, but no validation checkpoints exist anywhere: no 'run build/tests after each migration step', no post-deploy verification, and the destructive 'rm -rf .nuxt .output node_modules/.vite' cleanup has no verify step. This matches 'sequence present but checkpoints missing or implicit' rather than anchor 4's 'most checkpoints present'.

3 / 5

Progressive Disclosure

The 'When to Load References' section gives excellent per-file trigger lists, and all four referenced files (hydration.md, performance.md, testing-vitest.md, deployment-cloudflare.md) exist one level deep with real content. However, the body inlines full treatment of the same topics (complete hydration fix patterns, full Vitest setup, every deployment preset config) that duplicates the reference files, which is more than minor misplacement — yet the signaling is far clearer than anchor 3's 'references not clearly signaled', so it sits above the midpoint.

4 / 5

Total

14

/

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 that clearly states what the skill covers and provides an explicit, multi-trigger 'Use when:' clause with natural keywords and platform synonyms. Its main weakness is that the 'what' enumerates topic domains rather than concrete actions, and it has some overlap risk with closely related Nuxt sibling skills.

DimensionReasoningScore

Specificity

Names the domain and several specific capability areas ("hydration, performance, testing with Vitest, deployment to Cloudflare/Vercel/Netlify, and v4 migration") but these are topic areas rather than concrete actions like 'extract text' or 'fill forms', and per-area depth is thin, matching the anchor for several specific actions with minor gaps rather than comprehensive concrete actions.

4 / 5

Completeness

Explicitly answers both: a clear 'what' ("Nuxt 4 production optimization: hydration, performance, testing with Vitest, deployment...") and an explicit 'Use when:' clause with five concrete trigger phrases, mirroring the anchor-5 example structure. The 'when' is fully explicit, not merely present as at anchor 4.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ("debugging hydration mismatches", "Core Web Vitals", "Cloudflare Pages/Workers", "Nuxt 3 to Nuxt 4") with platform synonyms, but misses common variations like 'hydration error', 'SSR', or 'lazy loading'. This sits between good coverage and comprehensive synonym coverage, noticeably above the midpoint.

4 / 5

Distinctiveness Conflict Risk

Has a clear Nuxt 4 production niche with distinct deployment/migration/hydration triggers, but overlaps with the sibling skills the body itself names (nuxt-core, nuxt-data, nuxt-server) on hydration and testing topics. Distinct enough to avoid the overlap risk of anchor 3, but not the minimal-conflict clarity of anchor 5.

4 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository

secondsky/claude-skills

Path

plugins/nuxt-v4/skills/nuxt-production/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.