CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/vitest/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 exemplary progressive-disclosure index — every reference is real, clearly signaled, and one level deep — but it front-loads introductory/marketing content Claude doesn't need and offers no inline quick-start code or command, leaving the most common first task (write and run a basic test) without immediate actionable guidance.

Suggestions

Replace the intro paragraph and 'Key Features' bullet list (and the dated 'based on Vitest 5.x (beta), generated at 2026-06-22' note) with a single line of scope; the reference tables already convey the capability map.

Add a minimal quick-start snippet before the tables — e.g., a two-line example test and the `npx vitest` run command — so the most common task has copy-paste-ready guidance without opening a reference.

Mark an entry point in the tables (e.g., a 'Start here: core-test-api, core-config' note) so a first-time reader knows which references to load first.

DimensionReasoningScore

Conciseness

The body spends its first half on material Claude already knows — 'Vitest is a next-generation testing framework... It provides a Jest-compatible API with native ESM, TypeScript, and JSX support' and a marketing-style 'Key Features' bullet list ('Smart watch mode', 'Multi-threaded workers') that duplicates the reference tables' signal. The time-sensitive note 'based on Vitest 5.x (beta), generated at 2026-06-22' is not in a deprecation/old-patterns section. This fits anchor 3 ('mostly efficient but includes some unnecessary explanation') — not 2, since the tables themselves are lean and there is no tutorial-style padding.

3 / 5

Actionability

The body is a pure index: the topic-to-file mapping ('Mocking | ... | features-mocking.md') is concrete guidance for finding details, but there is no executable content anywhere in the body — no minimal test snippet, no `npx vitest` command, no quick-start example. This matches anchor 3 ('some concrete guidance but incomplete... missing key details') rather than 4, because the common entry case (write/run a first test) has nothing copy-paste ready inline.

3 / 5

Workflow Clarity

As a navigation skill the single action — locate the right reference — is unambiguous: three clearly labeled category tables (Core, Features, Advanced) with one row per topic and its reference link, and each of the 19 linked files exists and is one level deep. It falls short of 5 because there is no entry-point guidance (no 'start with core-test-api / core-config' ordering) and no quick-start section to orient a first-time task.

4 / 5

Progressive Disclosure

The SKILL.md is a concise overview and all detail lives in 19 real, verified reference files, each linked with a descriptive label in organized tables, exactly one level deep (references contain no further references/) and split by topic area. This matches anchor 5 ('clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation').

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.

A well-constructed description that clearly states both capability and explicit usage triggers with concrete, natural terminology. Its only weaknesses are minor: slightly incomplete action coverage and a few missing trigger synonyms, plus a small overlap risk on the generic 'writing tests' trigger.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'writing tests, mocking, configuring coverage, or working with test filtering and fixtures' — grounded in a named domain (Vitest/Vite/Jest-compatible API), but coverage has gaps (no snapshot testing, assertions, or CLI/running of tests). It matches anchor 4 ('several specific actions; minor gaps') rather than 5, and is clearly above anchor 3 because more than 1-2 actions are named.

4 / 5

Completeness

It explicitly answers both questions: 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 multiple concrete trigger phrases, matching the anchor-5 example pattern. Not 4, because the 'when' clause is already explicit and specific rather than improvable-but-present.

5 / 5

Trigger Term Quality

Natural user phrases are well covered: 'writing tests', 'mocking', 'coverage', 'test filtering', 'fixtures', plus 'unit testing' and 'Jest-compatible' in the framing sentence. A few common variations are missing (e.g., 'snapshots', 'run tests', 'jest migration'), which fits anchor 4 ('good keyword coverage; a few natural terms missing') rather than anchor 5's comprehensive synonym/extension coverage.

4 / 5

Distinctiveness Conflict Risk

The skill occupies a clear niche (Vitest/Vite) with distinct tooling names, but the generic trigger 'Use when writing tests' could overlap with a general Jest or other testing skill. This is anchor 4 ('mostly distinct; minor overlap risk with closely related skills'), not 5, because a bare 'writing tests' request doesn't unambiguously mean Vitest.

4 / 5

Total

17

/

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

compozy/compozy

Path

.agents/skills/vitest/SKILL.md

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.