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

92%

Does it follow best practices?

Impact

78%

1.50x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

85%

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

A well-structured, executable quick-start with excellent progressive disclosure and one-level-deep real references. The main weakness is redundancy between the Reference Files table, the Loading Files checkbox list, and the When-to-Use bullets.

Suggestions

Consolidate the Reference Files table and the Loading Files checkbox list — both restate the same five task-to-file mappings. Keep the load-decision checkboxes (which add the 'DO NOT load all at once' guard) and drop the redundant table to save tokens.

Trim or remove the 'When to Use' bullet list, which duplicates the frontmatter description's triggers and adds little new information.

Fold the one-line 'Vite-native testing framework with Jest-compatible API.' context into the description so the body can open directly with Quick Start.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept bloat, but the Reference Files table and the Loading Files checkbox list restate the same five task-to-file mappings, and the 'When to Use' bullets duplicate the frontmatter description — it could be tightened.	2 / 3
Actionability	Provides copy-paste-ready, fully executable artifacts: 'npm i -D vitest', a complete vitest.config.ts, and a runnable example.test.ts with describe/it/expect.	3 / 3
Workflow Clarity	As a reference-style skill with no destructive or batch operations, the single 'pick the relevant reference file and load it' action is unambiguous and well-organized via the Loading Files decision list, satisfying the simple-skill allowance.	3 / 3
Progressive Disclosure	Overview body points to five real one-level-deep reference files (config.md, test-api.md, mocking.md, utilities.md, advanced.md, all present in ./references/), clearly signaled by task-to-file table and load-decision checkboxes with an explicit 'DO NOT load all at once' guard.	3 / 3
	Total	11 / 12 Passed

Description

100%

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 description: third-person gerund form, explicit 'Use when' trigger, concrete multi-action capability list, and a clearly bounded Vite-specific niche. No vague fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — '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' — matching the multi-action anchor.	3 / 3
Completeness	Explicit 'Use when writing unit/integration tests for Vite projects' trigger answers 'when', and the enumerated capabilities answer 'what', satisfying both halves.	3 / 3
Trigger Term Quality	Covers natural terms a user would say ('unit/integration tests', 'Vite projects', 'code coverage', 'mock') plus API-level terms (vi.fn, vi.mock, describe/it) that practitioners actually utter.	3 / 3
Distinctiveness Conflict Risk	Vite-specific scoping with vitest.config.ts and vi.fn/vi.mock signals carve a clear niche unlikely to trigger generic jest or test-runner skills.	3 / 3
	Total	12 / 12 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
Commit: a212359

Reviewed: 1 day 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.