vitest

Use when writing unit/integration tests for Vite projects - configure vitest.config.ts, write test suites with describe/it, create mock implementations with vi.fn and vi.mock, set up code coverage thresholds, and run tests in parallel

1.50x

Quality

93%

Does it follow best practices?

Impact

78%

1.50x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

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

Well-structured, lean, and actionable body that delegates detail to real reference files with clear navigation. The only gap is the absence of an inline test-run/verification step in the Quick Start.

Suggestions

Add a one-line 'Run: npx vitest' step at the end of Quick Start so the install-to-verification sequence is complete and self-contained.

Optionally note where to look when tests fail (e.g. utilities.md for filtering/coverage) to close the feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is lean: a one-line framing sentence, copy-paste install/config/test snippets, a reference table, and a loading checklist, with no padding or explanation of concepts Claude already knows.	5 / 5
Actionability	Provides fully executable, copy-paste-ready guidance ('npm i -D vitest', a complete vitest.config.ts, and a runnable example.test.ts) covering the common getting-started cases.	5 / 5
Workflow Clarity	Quick Start implies a clear install -> configure -> write-test sequence, but no inline 'run tests to verify' step or validation checkpoint is shown; minor gap rather than a destructive/batch workflow so the cap does not apply.	4 / 5
Progressive Disclosure	Clear overview with a task-to-file reference table, an explicit loading checklist, a 'DO NOT load all files at once' directive, and verified one-level-deep references (all five files exist).	5 / 5
	Total	19 / 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, specific description that clearly states capabilities and trigger conditions with concrete API names. Only minor gap is the absence of common synonyms and file extensions in the trigger terms.

Suggestions

Add natural synonyms and file extensions to the trigger clause, e.g. 'testing', 'spec files', or '.test.ts', to broaden keyword coverage.

Consider an explicit file-extension cue like '.test.ts/.spec.ts' so users referencing those files naturally match this skill.

Dimension	Reasoning	Score
Specificity	Lists five concrete actions with specific APIs ('configure vitest.config.ts', 'write test suites with describe/it', 'create mock implementations with vi.fn and vi.mock', 'set up code coverage thresholds', 'run tests in parallel'), matching the comprehensive-coverage anchor.	5 / 5
Completeness	Explicitly states both the 'what' (the five capabilities) and the 'when' ('Use when writing unit/integration tests for Vite projects'), satisfying the top anchor.	5 / 5
Trigger Term Quality	Good natural keywords ('unit/integration tests', 'Vite projects', 'describe/it', 'vi.fn'), but missing common synonyms and file extensions users say such as 'testing', 'spec files', and '.test.ts'.	4 / 5
Distinctiveness Conflict Risk	The 'for Vite projects' qualifier plus vitest-specific APIs (vitest.config.ts, vi.fn, vi.mock) carve a clear niche with minimal overlap against general testing skills.	5 / 5
	Total	19 / 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: 4754673

Reviewed: 9 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.