vitest-testing

Vitest unit and integration testing patterns, commands, mocking (vi.mock), and coverage. Use when writing .test.ts files, configuring the test runner, or adding coverage thresholds.

Quality

96%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

92%

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

This is a high-quality skill that provides comprehensive, actionable Vitest testing guidance with executable code examples covering all major patterns (unit tests, mocking, timers, configuration). The workflow section includes proper validation and feedback loops. The only minor weakness is that the content is somewhat lengthy for a single file, though the clear section headers and single external reference partially mitigate this.

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. It jumps straight into commands, code examples, and configuration without explaining what Vitest is or how testing works conceptually. Every section earns its place with concrete, non-redundant information.	3 / 3
Actionability	All code examples are fully executable and copy-paste ready — from CLI commands to test structure, mocking patterns, timer mocking, and configuration. Specific imports are shown, and examples cover real-world patterns (spies, module mocks, fake timers).	3 / 3
Workflow Clarity	The workflow section provides a clear 6-step sequence with explicit validation checkpoints: run tests, fix failures, use verbose reporter to inspect, re-run coverage until thresholds pass. The feedback loop (step 4 and step 5's 're-run until thresholds pass') is well-defined for a non-destructive testing workflow.	3 / 3
Progressive Disclosure	There is a reference to a project-specific config file (testing-config.md) at the top, which is good. However, the skill is fairly long (~150 lines) with full configuration and multiple mocking patterns inline that could potentially be split into referenced files. The structure is well-organized with clear headers, but it's borderline monolithic for a single file.	2 / 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.

This is a strong skill description that concisely covers specific capabilities (testing patterns, mocking with vi.mock, coverage), uses natural trigger terms a developer would use, and includes an explicit 'Use when...' clause with clear trigger scenarios. The Vitest-specific terminology makes it highly distinctive and unlikely to conflict with other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'unit and integration testing patterns', 'commands', 'mocking (vi.mock)', 'coverage', 'writing .test.ts files', 'configuring the test runner', 'adding coverage thresholds'. These are concrete, actionable capabilities.	3 / 3
Completeness	Clearly answers both 'what' (Vitest testing patterns, commands, mocking, coverage) and 'when' with an explicit 'Use when...' clause specifying three trigger scenarios: writing .test.ts files, configuring the test runner, or adding coverage thresholds.	3 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'Vitest', 'unit', 'integration testing', 'mocking', 'vi.mock', 'coverage', '.test.ts', 'test runner', 'coverage thresholds'. Good coverage of terms a developer would naturally use when needing this skill.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive due to the specific framework name 'Vitest', the specific API 'vi.mock', and the file extension '.test.ts'. Unlikely to conflict with other testing skills (e.g., Jest, Mocha) or general coding 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: monkilabs/opencastle
Commit: 7a69a05

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