CtrlK
BlogDocsLog inGet started
Tessl Logo

vite-plus

Set up, migrate, upgrade, or debug Vite+ tooling and configuration. Use for Vite+ commands, tests, hooks, packaging, and CI; excludes application behavior and release policy.

84

1.35x
Quality

89%

Does it follow best practices?

Impact

81%

1.35x

Average score across 2 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

A well-structured, token-efficient instruction skill that leans on clearly signaled reference files and a real verification sequence. The main gap is the absence of an explicit error-recovery feedback loop for migration/batch operations.

Suggestions

Add an explicit validate -> fix -> re-run retry loop in the Verification section for migration and upgrade paths so failures have a documented recovery path.

Include one or two concrete command snippets (e.g., the exact migrator invocation and a frozen-install command) to lift actionability from mostly-executable to copy-paste ready.

Make the 'pnpm 12 or newer' version target a reference-owned value or note where the canonical pin lives, so the inline version number does not drift silently.

DimensionReasoningScore

Conciseness

The body is dense and lean, assuming Claude's competence throughout: it gives concrete probes ('pnpm exec vp --version', 'pnpm exec vp toolchain --json') without explaining what Vite+ is or how toolchains work.

5 / 5

Actionability

Concrete commands, file paths ('node_modules/vite-plus/docs/', 'vite.config.ts', 'AGENTS.md'), and a 5-step verification list give mostly executable guidance, though it is instruction-style rather than copy-paste code blocks.

4 / 5

Workflow Clarity

The Verification section sequences steps with implicit checkpoints ('Inspect manifests, consolidated config, and lockfile importers after migration'), but it lacks an explicit validate -> fix -> retry feedback loop for destructive migration/batch operations.

4 / 5

Progressive Disclosure

The overview points to nine real one-level-deep reference files (bootstrap, packages, monorepos, commands, testing, hooks, ci-cd, known-issues, examples), each signaled with a concrete load condition, and keeps detail out of SKILL.md.

5 / 5

Total

18

/

20

Passed

Description

92%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.

A strong, tight description that pairs concrete actions with explicit use-conditions and an exclusion boundary. Adding a few synonyms or file-name triggers would push trigger term quality from good to comprehensive.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Set up, migrate, upgrade, or debug') against a named domain ('Vite+ tooling and configuration'), giving comprehensive coverage rather than a single generic verb.

5 / 5

Completeness

Explicitly answers both what ('Set up, migrate, upgrade, or debug Vite+ tooling and configuration') and when ('Use for Vite+ commands, tests, hooks, packaging, and CI'), and adds a concrete exclusion boundary.

5 / 5

Trigger Term Quality

Natural terms users would say ('commands, tests, hooks, packaging, and CI') are present, but it lacks synonyms and concrete file/extension triggers like 'vite.config.ts' or 'vp' that would round out coverage.

4 / 5

Distinctiveness Conflict Risk

The 'Vite+' niche is distinct and the explicit 'excludes application behavior and release policy' boundary sharply lowers the risk of triggering for the wrong skill.

5 / 5

Total

19

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
uinaf/agent-skills
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.