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.
100
100%
Does it follow best practices?
Impact
100%
1.72xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that concisely covers specific capabilities, includes natural trigger terms users would use, explicitly states both what the skill does and when to use it, and occupies a clear niche. It uses proper third-person voice and avoids vague language or buzzwords.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions/domains: 'build tool configuration', 'plugin API', 'SSR', and 'Vite 8 Rolldown migration'. These are distinct, concrete capabilities rather than vague abstractions. | 3 / 3 |
Completeness | Clearly answers both 'what' (Vite build tool configuration, plugin API, SSR, Rolldown migration) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios (working with Vite projects, vite.config.ts, Vite plugins, building libraries/SSR apps). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Vite', 'vite.config.ts', 'Vite plugins', 'SSR', 'building libraries', 'Rolldown', 'Vite projects'. These cover common variations of how users would reference Vite-related work. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche around Vite specifically. The mention of 'vite.config.ts', 'Vite plugins', 'Rolldown migration' makes it very unlikely to conflict with generic build tool or bundler skills (e.g., webpack, esbuild). | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that serves as an effective overview and navigation hub for Vite configuration. It's concise, actionable with real code examples, and uses progressive disclosure effectively through organized reference tables. The content assumes Claude's competence and every section earns its place.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. The brief intro establishes Vite 8/Rolldown context without explaining what a build tool is. Tables are compact, code examples are minimal but complete, and no unnecessary explanations are included. | 3 / 3 |
Actionability | Provides executable CLI commands, a complete copy-paste-ready vite.config.ts example, specific plugin package names, and clear preferences (TypeScript, ESM). The common config example covers the most frequent use cases concretely. | 3 / 3 |
Workflow Clarity | For a configuration/reference skill like this, there isn't a multi-step destructive workflow requiring validation checkpoints. The CLI commands are clearly listed in logical order (dev → build → preview → SSR build), and the config example is unambiguous. This is appropriate for the skill's nature. | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview and well-organized tables pointing to one-level-deep reference files. Topics are logically grouped (Core, Build & SSR, Advanced), references are clearly signaled with descriptive links, and cross-skill references provide additional navigation. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- onmax/nuxt-skills
- Commit
3110745
- Reviewed
Table of Contents
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.