Tessl • The management layer for AI agent skills

SkillPublic

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

89%

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

Quality

Content

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

The body is an exemplary progressive-disclosure index: lean, version-scoped, and organized into navigable tables whose links all resolve to real one-level-deep reference files. Its only weakness is actionability — the body itself contains no code or commands, so every task requires a reference-file hop before anything executable is in hand.

Suggestions

Add a minimal quick-start snippet inline (e.g., a basic useFetch call or a nuxt.config.ts route-rules example) so the most common tasks have immediately executable guidance without loading a reference file.

State the usage pattern explicitly in one line (e.g., "Locate your task in the tables below, then read the linked reference before acting") so the routing workflow is instructed rather than implied.

Cross-link or order the two data-fetching rows (core-data-fetching vs best-practices-data-fetching) to indicate which an agent should consult first for a given question.

Dimension	Reasoning	Score
Conciseness	The ~50-line body is lean and assumes Claude's competence: no generic explanation of Vue or SSR, and the blockquotes carry only high-value version-specific deltas Claude won't know ("server utilities import from `nuxt/server`", "Nuxt 5 requires Node `22.19`/`24.11`+"). The version stamp is scoping metadata, not date-conditional instructions, so the time-sensitivity penalty does not apply.	5 / 5
Actionability	The body contains no inline code or commands — all executable material lives in the reference files. It does offer concrete routing (per-row API names like "useFetch, useAsyncData, $fetch, typed routes, createUseFetch factories") and immediately applicable directives ("import from `nuxt/server`", "use `~~`/`@@` for the root"), but common tasks have no executable example without first loading a reference. Falls between anchor 3 and anchor 4: more concrete than high-level hints, but short of 'mostly executable guidance with concrete code or commands'.	3 / 5
Workflow Clarity	This is a simple single-action skill (match the task to a table row, then read the linked reference) and that action is unambiguous: five clearly categorized sections with descriptive rows. Overlapping rows ("Data Fetching" vs "Data Fetching Patterns") are disambiguated by their descriptions. No destructive or batch operations, so no validation cap applies.	5 / 5
Progressive Disclosure	A clean overview with well-signaled one-level-deep references: all 18 linked files exist in references/, none of them contain nested .md references (verified), and content is appropriately split across categorized tables. Matches the anchor-5 structure of clear overview plus clearly labeled per-topic files.	5 / 5
	Total	18 / 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 description: it identifies the domain with concrete feature areas and pairs a clear 'what' with an explicit, trigger-rich 'Use when' clause in third person. Trigger coverage is good but could add a few more natural Nuxt terms (composables, nuxt.config, modules) for full breadth.

Dimension	Reasoning	Score
Specificity	Enumerates several specific technical areas — "SSR, auto-imports, and file-based routing" plus "server routes, useFetch, middleware, or hybrid rendering" — though they are phrased as framework features rather than actions. Above anchor 3 (which covers only 1-2 concrete items) but below anchor 5 because coverage has minor gaps (no mention of modules, nuxt.config, deployment, or state management).	4 / 5
Completeness	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, matching the anchor-5 pattern. Not anchor 4, since the 'when' clause is already explicit and specific rather than improvable.	5 / 5
Trigger Term Quality	"Nuxt apps", "server routes", "useFetch", "middleware", and "hybrid rendering" are natural phrases users would say when needing this skill. Below anchor 5 because a few common natural terms are missing (composables, nuxt.config, modules, Nitro, deployment).	4 / 5
Distinctiveness Conflict Risk	"Nuxt" and "useFetch" are distinctive niche triggers that clearly separate this from generic Vue or web-framework skills; conflict risk is minimal. Terms like "middleware" are generic in isolation but are anchored by the explicit Nuxt framing.	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
Revision: 2e74504

Reviewed: 3 days ago

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.

nuxt

Table of Contents

Is this your skill?