nuxt

Nuxt full-stack Vue framework with SSR, auto-imports, and file-based routing. Use when working with Nuxt apps, server routes, useFetch, middleware, or hybrid rendering.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/nuxt/SKILL.md

Quality

Content

71%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.

An exemplary progressive-disclosure hub: a lean, well-organized index that defers detail to 17 one-level-deep reference files plus a valuable version-specific note. Its one weakness is that the body itself carries almost no actionable guidance, relying entirely on the references for executable detail.

Suggestions

Add a short 'Quick start' or 'Common task' section with 1-2 concrete code snippets (e.g., a minimal nuxt.config.ts, a useFetch example, a server route) so the body is actionable without forcing a reference hop for the most frequent cases.

Surface the single most important gotcha from the references inline (e.g., the app/ srcDir move is already noted — consider similarly inlining the one-line SSR hydration rule) to raise actionability without breaking the lean index.

Consider a one-line orientation sentence under each table group stating the decision the reader is making (e.g., 'Pick a rendering mode per route') to turn the index into light guidance rather than a pure catalog.

Dimension	Reasoning	Score
Conciseness	The body is a lean overview — one intro sentence, a genuinely useful Nuxt 4 srcDir note, and topic tables acting as a pure index — with no padding and no explanation of concepts Claude already knows, so every token earns its place.	5 / 5
Actionability	The body itself provides no code, commands, or concrete executable steps — it is a high-level index ('See [references/...]') with one actionable note, leaving the specific steps to execute in the referenced files.	2 / 5
Workflow Clarity	As a single-purpose reference index under ~50 lines with no destructive or batch operations, it is clearly and well-organized; the simple-skill exception applies, though there is no multi-step sequence to validate.	4 / 5
Progressive Disclosure	Clear overview with well-signaled one-level-deep references — every table row links to a real file in references/ (all 17 confirmed present), content is appropriately split, and navigation is trivial.	5 / 5
	Total	16 / 20 Passed

Description

87%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, concise description that clearly states what the skill covers and when to use it with concrete Nuxt-specific trigger terms. Minor room for improvement only in adding a few more synonyms (e.g., Vue, SSR) to the trigger clause.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete capabilities — 'SSR, auto-imports, and file-based routing' — giving specific feature coverage rather than generic language, though these are framework characteristics rather than discrete actions, leaving minor gaps versus a fully comprehensive action list.	4 / 5
Completeness	It explicitly answers both 'what' ('Nuxt full-stack Vue framework with SSR, auto-imports, and file-based routing') and 'when' ('Use when working with Nuxt apps, server routes, useFetch, middleware, or hybrid rendering') with concrete trigger phrases.	5 / 5
Trigger Term Quality	The when-clause 'Use when working with Nuxt apps, server routes, useFetch, middleware, or hybrid rendering' supplies natural developer keywords a user would actually say, but omits common synonyms such as 'Vue' or 'SSR' in the trigger phrase.	4 / 5
Distinctiveness Conflict Risk	'Nuxt' is a specific named framework with distinct triggers (useFetch, server routes, hybrid rendering), giving it a clear niche and minimal conflict risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: onmax/nuxt-skills
Path: skills/nuxt/SKILL.md
Commit: bc438e5

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.