uinaf/vite-plus
Migrate or align frontend repositories to the stock Vite+ workflow. Use when standardizing package or monorepo repos around `vp`, `voidzero-dev/setup-vp`, `vite-plus/test`, and Vite+ native CI, test, and packaging flows, including updating scripts, test config, CI setup, and packaging commands.
97
100%
Does it follow best practices?
Impact
94%
1.46xAverage score across 6 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, well-crafted description that clearly identifies a narrow domain (Vite+ workflow migration), lists specific tools and actions, and provides explicit 'Use when' guidance with concrete trigger terms. The description is concise yet comprehensive, and its highly specific toolchain references make it virtually impossible to confuse with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: migrate/align frontend repos, standardize around specific tools (vp, voidzero-dev/setup-vp, vite-plus/test), replace direct package-manager and Vitest wiring with Vite+ equivalents, handle CI/test/packaging/hook flows. | 3 / 3 |
Completeness | Clearly answers both 'what' (migrate/align frontend repos to Vite+ workflow, replace package-manager and Vitest wiring) and 'when' (explicit 'Use when standardizing package or monorepo repos around vp, voidzero-dev/setup-vp, vite-plus/test, and Vite+ native CI/test/packaging/hook flows'). | 3 / 3 |
Trigger Term Quality | Includes highly specific natural trigger terms users would use: 'Vite+', 'vp', 'voidzero-dev/setup-vp', 'vite-plus/test', 'monorepo', 'Vitest', 'CI', 'packaging', 'hook flows'. These are the exact terms someone working in this ecosystem would mention. | 3 / 3 |
Distinctiveness Conflict Risk | Extremely niche and distinct — targets a very specific toolchain (Vite+, vp, voidzero-dev/setup-vp, vite-plus/test). Unlikely to conflict with general frontend, Vite, or CI skills due to the precise tool references. | 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 high-quality skill that efficiently guides migration to the Vite+ toolchain. It excels at conciseness (no wasted tokens explaining known concepts), provides fully actionable code/config examples, maintains a clear multi-step workflow with validation checkpoints, and uses progressive disclosure effectively by pointing to specific reference files at the right workflow steps. The guardrails section adds valuable safety constraints for common pitfalls.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and assumes Claude's competence throughout. No unnecessary explanations of what Vite, Vitest, or CI are. Every section delivers specific, actionable information without padding. The diff format for package.json scripts is particularly efficient. | 3 / 3 |
Actionability | Provides concrete YAML snippets for CI, executable TypeScript config, diff-format script changes, and specific CLI commands (vp check, vp test, vp build, vp upgrade). The migration targets are precise with exact import paths and command shapes. | 3 / 3 |
Workflow Clarity | The 11-step workflow is clearly sequenced with explicit validation checkpoints (step 5: 'Verify with vp check && vp test before moving on', step 11: full end-to-end validation). It includes feedback loops, conditional loading of references, and clear guardrails for destructive operations like CI changes. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear overview in SKILL.md and well-signaled one-level-deep references to specific topics (bootstrap.md, packages.md, monorepos.md, ci-cd.md, testing.md, commands.md, known-issues.md). The workflow explicitly tells when to load each reference, avoiding unnecessary context loading. | 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.
Reviewed
Table of Contents