vite

Vite build tool configuration, plugin API, SSR, and Vite 8 Rolldown migration. Use when working with Vite projects, vite.config.ts, Vite plugins, or building libraries/SSR apps with Vite.

Quality

78%

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/vite/SKILL.md

Quality

Content

72%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 tight, well-structured reference skill that keeps the SKILL.md body as an overview and pushes detail into verified one-level-deep reference files. Its main limitation is the absence of an explicit sequenced workflow with checkpoints, which is only partially applicable to a knowledge-style skill.

Suggestions

Trim the introductory 'Vite is a next-generation frontend build tool...' sentence to a one-line version-context note, since Claude already knows what Vite is.

Add a short inline example for the most common plugin-API or config task so the body is actionable without forcing a file hop for the primary use case.

If a typical Vite task has a natural sequence (e.g., configure -> build -> verify), sketch it as numbered steps with a verification checkpoint to raise workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is lean — tables, a compact config snippet, a CLI block, and a plugin list with almost no padded prose — but the introductory 'Vite is a next-generation frontend build tool...' line restates broadly known context that could be trimmed.	4 / 5
Actionability	Provides executable CLI commands and a copy-paste-ready defineConfig TS block, while delegating the deeper how-to (config options, plugin API hooks) to referenced files rather than showing it inline, leaving minor gaps.	4 / 5
Workflow Clarity	Content is organized into a navigable topical sequence (Core, Build & SSR, Advanced, Quick Reference) but there is no explicit multi-step workflow with validation checkpoints, which fits a reference skill but sits at the midpoint anchor.	3 / 5
Progressive Disclosure	The body is a clear overview that signals one-level-deep references via markdown-linked tables, all six referenced files exist in references/, and detail is appropriately split out, matching the top anchor.	5 / 5
	Total	16 / 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 well-constructed description that clearly states capabilities and provides explicit, natural trigger phrases with a concrete config-file reference. It is near the top of the scale, held back only by slightly generic action wording and minor synonym coverage.

Dimension	Reasoning	Score
Specificity	The phrase 'Vite build tool configuration, plugin API, SSR, and Vite 8 Rolldown migration' names the domain plus several specific capability areas, but 'configuration' is a somewhat generic action and HMR/dev-server are absent, leaving minor gaps versus comprehensive coverage.	4 / 5
Completeness	It explicitly answers both 'what' (configuration, plugin API, SSR, Rolldown migration) and 'when' via the concrete 'Use when working with Vite projects, vite.config.ts, Vite plugins...' trigger clause, matching the top anchor.	5 / 5
Trigger Term Quality	Includes natural user-facing terms like 'Vite projects', 'vite.config.ts', 'Vite plugins', and 'building libraries/SSR apps with Vite' with good keyword coverage, but lacks synonyms or broader variations that would warrant a 5.	4 / 5
Distinctiveness Conflict Risk	The Vite-specific triggers (vite.config.ts, Vite plugins) carve a clear niche with minimal conflict, but a generic frontend-build-tool skill could still overlap on broad build/SSR phrasing.	4 / 5
	Total	17 / 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/vite/SKILL.md
Commit: bc438e5

Reviewed: 5 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.