CtrlK
BlogDocsLog inGet started
Tessl Logo

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, packaging, and hook flows, including Vite+ 0.2.x Vitest-wrapper cleanup.

84

1.40x
Quality

89%

Does it follow best practices?

Impact

80%

1.40x

Average score across 6 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An excellent migration body: concise, highly actionable, with a well-sequenced workflow and concrete validation checkpoints. The one real defect is that the seven referenced `references/*.md` files are missing, so the otherwise well-structured progressive disclosure points to absent targets.

Suggestions

Provide the missing `references/` bundle files (bootstrap.md, packages.md, monorepos.md, ci-cd.md, testing.md, commands.md, known-issues.md) so the signaled one-level-deep navigation actually resolves.

If a reference is not yet written, either omit its link or mark it as forthcoming, rather than linking to a non-existent path.

DimensionReasoningScore

Conciseness

Dense and information-rich with concrete commands, pinning rules, and complete config blocks; it assumes Claude's competence and never pads with "what is Vite" conceptual explanation, so nearly every token earns its place.

3 / 3

Actionability

Provides fully executable, copy-paste-ready guidance — `vp install && vp check && vp test`, `vp migrate --full`, `vp upgrade`, plus complete YAML/TS config blocks and a concrete diff — matching the score-3 anchor.

3 / 3

Workflow Clarity

An 11-step numbered Workflow with explicit validation checkpoints ("Verify with `vp check && vp test` before moving on", a final "End-to-end validation" step), giving a clear sequence with feedback for error recovery.

3 / 3

Progressive Disclosure

The body signals one-level-deep references with clear load conditions (e.g. "Load known-issues.md only on unexpected behavior"), but the referenced `references/` files do not actually exist in the bundle, so the signaled navigation resolves to nothing and is not fully functional.

2 / 3

Total

11

/

12

Passed

Description

85%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, concrete description with an explicit "Use when" trigger and a clearly bounded Vite+ niche. Its only weakness is trigger-term naturalness, which leans toward technical identifiers over the varied phrasings a broad user base would naturally say.

Suggestions

Broaden the trigger phrasing with more natural user-facing terms (e.g. "when moving a repo onto Vite+", "switching from Vitest/pnpm scripts to vp") so it fires on varied ways users describe the need, not just internal identifiers.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across migration surfaces — "standardizing package or monorepo repos", "replacing direct package-manager and Vitest wiring with the Vite+ equivalents" — matching the score-3 anchor for multiple specific concrete actions.

3 / 3

Completeness

Explicitly states what it does ("Migrate or align frontend repositories to the stock Vite+ workflow") and when to use it ("Use when standardizing package or monorepo repos around..."), satisfying both halves with an explicit trigger.

3 / 3

Trigger Term Quality

Has relevant keywords ("standardizing", "Vitest", "package-manager", "monorepo") plus a clear "Use when" clause, but leans on technical identifiers a user would only say if already deep in Vite+; coverage of natural phrasings is partial.

2 / 3

Distinctiveness Conflict Risk

Names a narrow, well-defined niche ("stock Vite+ workflow", "Vite+ native CI, test, packaging, and hook flows") with triggers unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 8 missing

Warning

referenced_paths_exist

Referenced path issues: 16 missing

Warning

Total

14

/

16

Passed

Reviewed

Table of Contents