vite

Expert guidance for Vite development with modern build tooling, HMR, framework integrations, and performance optimization

Quality

69%

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 ./.agents/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.

The body is a strong, actionable Vite reference packed with executable config examples, but it is a monolithic ~350-line document with no progressive disclosure to separate files and no sequenced workflow or validation checkpoints. It works well as a cookbook but not as a navigable, layered skill.

Suggestions

Split large reference areas (Framework Integrations, Plugin Development, SSR/Library Mode) into separate files under references/ and link to them from SKILL.md to enable progressive disclosure.

Remove or tighten the generic 'Key Principles' bullets that restate knowledge Claude already has about Vite.

Add a short sequenced setup workflow with a verification step (e.g. 'run `vite build` then `vite preview` and confirm the bundle') to give the skill a clear procedural spine.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean — section headers plus executable code with minimal prose — but includes some generic principles Claude already knows ('Leverage native ES modules', 'Understand the dev/build differences') and repeats manualChunks in two forms. Not a 5 because of that redundancy and the generic principles section.	4 / 5
Actionability	Nearly every section provides copy-paste-ready, executable TypeScript config covering the common cases (config, aliases, env, HMR, assets, integrations, chunking, proxy, plugins, Vitest, SSR, library mode). Stays above 4 because the bulk is complete and runnable, with only minor illustrative snippets lacking imports.	5 / 5
Workflow Clarity	Content is organized by topic, not as a sequenced multi-step workflow, and contains no validation checkpoints or feedback loops. Scored 3 rather than lower because it is clearly navigable by section, but there is no procedural sequence or verification to push it higher.	3 / 5
Progressive Disclosure	Good section-level structure exists, but the file is ~350 lines with everything inlined and no references to separate files (and no references/, scripts/, or assets/ bundles exist). Content like framework integrations, plugin development, and SSR clearly belongs in separate reference files, so it does not reach 4.	3 / 5
	Total	15 / 20 Passed

Description

66%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 specific and well-targeted to Vite with good trigger keywords, but it omits any explicit 'Use when...' trigger guidance, which caps its completeness. It reads as a feature-area catalog rather than a list of concrete actions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when setting up or configuring a Vite project, debugging HMR, integrating React/Vue/Svelte, or optimizing frontend builds.'

Reframe capability areas as concrete verbs (e.g. 'Configure build tooling, wire up HMR, integrate frameworks, optimize production bundles') to lift specificity.

Include natural synonyms users say (e.g. 'Hot Module Replacement', 'frontend bundler', framework names) to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists several specific capability areas ('modern build tooling, HMR, framework integrations, and performance optimization') rather than a single vague action, though these are feature domains rather than concrete verbs. Not a 5 because none are phrased as concrete actions (extract/fill/merge-style) and 'Expert guidance' is generic.	4 / 5
Completeness	Has a clear 'what' (expert guidance for Vite development across listed areas) but no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric. The 'when' is only weakly implied by the word 'Vite'.	3 / 5
Trigger Term Quality	Includes the natural keyword 'Vite' plus commonly-said terms like 'HMR', 'build tooling', and 'performance optimization'. Not a 5 because synonyms like 'Hot Module Replacement', 'frontend bundler', or framework names (React/Vue/Svelte) that users cite are missing.	4 / 5
Distinctiveness Conflict Risk	'Vite development' is a clear niche unlikely to collide with unrelated skills, with only minor overlap risk against general frontend build-tooling skills. Not a 5 because 'Expert guidance for ... development' is broad enough to brush against adjacent bundler skills.	4 / 5
	Total	15 / 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: debpalash/VoiceStudio
Path: .agents/skills/vite/SKILL.md
Commit: 685ca91

Reviewed: 31 minutes 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.