vitest

Vitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/vitest/SKILL.md

Quality

Content

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

The body is an efficient, well-structured navigation hub that excels at progressive disclosure — every reference is real, one level deep, and clearly signaled. Its weakness is that all executable guidance lives in the reference files, so the body itself offers no code or sequenced workflow.

Suggestions

Add a brief Quick Start snippet (e.g., a minimal test file and the `vitest` run command) inline so the body is actionable without requiring a reference hop for the most common case.

Move the 'Vitest 5.x (beta), generated at 2026-06-22' version/date note into a dedicated Versioning or Deprecated section so time-sensitive information does not dilute the concise overview.

For common multi-step flows (e.g., configure coverage then run filtered tests), include a short sequenced checklist in the body with a validation step so workflow clarity is not entirely delegated to references.

Dimension	Reasoning	Score
Conciseness	The body is a lean index of overview, feature bullets, and three reference tables with little padding, but the blockquote version note ('Vitest 5.x (beta), generated at 2026-06-22') is time-sensitive information placed outside a deprecated/old-patterns section, a minor over-explanation that could be trimmed.	4 / 5
Actionability	The body offers concrete navigation — each table row pairs a topic, a one-line description, and a real reference link — but contains no executable code or commands inline, delegating all hands-on guidance to the reference files, which leaves key execution details out of the written body.	3 / 5
Workflow Clarity	Content is organized into clear Core/Features/Advanced categories that aid discovery, but there is no sequenced multi-step process or validation checkpoints in the body; the skill is a reference catalog rather than a workflow, so it sits at the midpoint.	3 / 5
Progressive Disclosure	A clear overview points to well-signaled, one-level-deep references organized into three themed tables, and all 19 referenced files exist in references/, yielding easy navigation with no nested indirection.	5 / 5
	Total	15 / 20 Passed

Description

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

The description is strong: it states both what the skill does and when to use it with concrete, natural-sounding trigger phrases tied to a clearly named framework. Minor gaps in capability coverage and a slight overlap risk with generic Jest testing skills prevent a perfect score.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'writing tests, mocking, configuring coverage, ... test filtering and fixtures' — but omits other capabilities present in the body (snapshots, type testing, benchmarking), leaving minor coverage gaps that keep it below a 5.	4 / 5
Completeness	Explicitly states what ('Vitest fast unit testing framework powered by Vite with Jest-compatible API') and when ('Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Natural phrases like 'writing tests', 'mocking', 'configuring coverage', and 'test filtering' are terms users would actually say, but it lacks common synonyms (unit tests, assertions, spec files, .test.ts), so it is not comprehensive enough for a 5.	4 / 5
Distinctiveness Conflict Risk	The 'Vitest ... powered by Vite' framing carves a clear niche, but the 'Jest-compatible API' claim and generic 'writing tests' trigger create minor overlap risk with a generic Jest testing skill, keeping it just below a 5.	4 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

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: onmax/nuxt-skills
Path: skills/vitest/SKILL.md
Commit: bc438e5

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.