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.

1.72x

Quality

83%

Does it follow best practices?

Impact

100%

1.72x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

78%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 a well-structured, token-efficient overview that points to real one-level-deep reference files and supplies executable CLI/config examples; its only weakness is mild time-sensitivity handling around Vite 8 version markers.

Suggestions

Move Vite 8 / Rolldown version markers into an explicit 'Current version' or 'Migration / old patterns' section so time-sensitive info does not dilute the concise overview.

Add one short worked example (e.g. a minimal plugin skeleton or SSR middleware snippet) to lift actionability from strong to fully copy-paste-ready across common cases.

Consider a brief 'Validation' note (e.g. running `vite build` then `vite preview`) so the build workflow has an explicit verification checkpoint.

Dimension	Reasoning	Score
Conciseness	Lean table-driven overview with compact CLI and config blocks and no padding of concepts Claude already knows; minor deduction for time-sensitive version info ('Vite 8 beta', '2026.1.31') placed outside a deprecated/old-patterns section.	4 / 5
Actionability	Provides executable CLI commands, a complete copy-paste defineConfig example, and concrete plugin package names; the topic tables are navigation pointers rather than instructions, leaving minor gaps.	4 / 5
Workflow Clarity	A multi-topic reference skill with clear organization and unambiguous single-action CLI/config guidance; it lacks an explicit multi-step workflow with validation checkpoints, but no destructive or batch operations are present to cap the score.	4 / 5
Progressive Disclosure	Clear overview body with well-signaled one-level-deep references (all six referenced files verified present) plus a Cross-Skill References section; content is appropriately split for easy navigation.	5 / 5
	Total	17 / 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.

The description is strong: it states concrete capabilities and pairs them with an explicit 'Use when' clause carrying concrete triggers, distinguishing the skill clearly from sibling vue/testing/library skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete capabilities ('build tool configuration, plugin API, SSR, and Vite 8 Rolldown migration') but stops short of the fully comprehensive multi-action anchor-5 example.	4 / 5
Completeness	Explicitly answers both what ('Vite build tool configuration, plugin API, SSR...') and when ('Use when working with Vite projects, vite.config.ts, Vite plugins...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural-term coverage ('Vite projects, vite.config.ts, Vite plugins, building libraries/SSR apps') including the distinctive config filename, though a few common synonyms are absent.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear Vite-specific niche with distinctive triggers like vite.config.ts and Vite plugins, yielding minimal conflict risk with sibling 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/vite/SKILL.md
Commit: 4754673

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