uinaf/viteplus
Migrate or align frontend repositories to the stock VitePlus workflow. Use when standardizing package or monorepo repos around `vp`, `voidzero-dev/setup-vp`, `vite-plus/test`, and VitePlus-native CI, test, and packaging flows, including updating scripts, test config, CI setup, and packaging commands.
98
100%
Does it follow best practices?
Impact
97%
1.73xAverage 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 skill description that clearly defines a narrow domain (VitePlus workflow migration), lists specific tools and actions, and provides explicit trigger guidance. It uses proper third-person voice and includes enough technical specificity to be easily distinguishable from other skills while remaining comprehensible to users working in this ecosystem.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: migrate/align frontend repos, standardize around specific tools (vp, setup-vp, vite-plus/test), replace direct package-manager and Vitest wiring with VitePlus equivalents, handle CI, test, packaging, and hook flows. | 3 / 3 |
Completeness | Clearly answers both 'what' (migrate/align frontend repos to VitePlus workflow, replace direct 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 VitePlus-native CI/test/packaging/hook flows'). | 3 / 3 |
Trigger Term Quality | Includes highly specific natural keywords users would say: 'VitePlus', 'vp', 'voidzero-dev/setup-vp', 'vite-plus/test', 'CI', 'Vitest', 'monorepo', 'package-manager', 'hooks'. These are the exact terms someone working in this ecosystem would use. | 3 / 3 |
Distinctiveness Conflict Risk | Extremely niche and specific to VitePlus migration workflows with distinct tool names (vp, voidzero-dev/setup-vp, vite-plus/test). Very unlikely to conflict with other skills due to the highly specialized domain and unique trigger terms. | 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 communicates a complex multi-step migration workflow. It excels at progressive disclosure by directing Claude to load specific reference files only when needed, provides concrete executable examples (YAML, TypeScript, diff), and includes clear validation checkpoints throughout the workflow. The guardrails and known caveats sections add practical safety without bloat.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It assumes Claude understands package managers, CI, Vitest, and build tooling without explaining basics. Every section delivers actionable migration targets or concrete commands without padding. | 3 / 3 |
Actionability | Provides fully concrete guidance: exact CLI commands (`vp check && vp test`), copy-paste YAML for CI, a real `vite.config.ts` example, and a diff showing package.json script migration. The workflow steps are specific and executable. | 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: end-to-end validation). It includes feedback-loop thinking (confirm before proceeding) and guardrails for destructive operations (don't delete release workflows). | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview in the main file 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 Claude 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