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

88%

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

Quality

Content

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

A highly actionable, well-structured skill body with executable commands, complete code examples, and a workflow featuring explicit fix-and-retry and coverage-threshold feedback loops. Minor room to trim the verbose coverage workflow step and to split detailed sections into reference files for progressive disclosure.

Suggestions

Tighten workflow step 5 — pick one reporter command per environment instead of enumerating CI/local JSON/text variants and both output paths.

Consider moving the extended mocking (module/spy/timer) and coverage-threshold detail into a references/ file, keeping SKILL.md as a leaner overview with one-level-deep pointers.

Dimension	Reasoning	Score
Conciseness	The body is lean — commands, executable code, and a config block with no explanations of concepts Claude already knows — but workflow step 5 is wordy (enumerating CI/local reporter variants and both output formats) and could be trimmed, matching 'efficient; minor instances that could be trimmed'.	4 / 5
Actionability	Every section is copy-paste ready: a full command cheat-sheet, complete runnable test/mocking/timer examples with imports, and a full vitest.config.ts including coverage thresholds — fully executable guidance covering the common cases.	5 / 5
Workflow Clarity	The six-step workflow is clearly sequenced with explicit validation and feedback loops: run the specific file and fix failures, use '--reporter=verbose' to inspect, and re-run coverage 'until thresholds pass'.	5 / 5
Progressive Disclosure	No bundle files exist, and the single external pointer ('.opencastle/stack/testing-config.md') is clearly signaled at the top; the body is well-sectioned but ~160 lines all inline — mocking and coverage detail could live in reference files, leaving minor organization gaps.	4 / 5
	Total	18 / 20 Passed

Description

88%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 description that clearly states capabilities and explicit 'Use when' triggers with concrete terms including a file extension. Its only weaknesses are a few missing natural synonyms and slight overlap risk with other test-framework skills.

Suggestions

Add natural trigger synonyms users commonly say, such as 'unit tests', 'integration tests', or 'test coverage', to the 'Use when' clause.

Disambiguate from other test frameworks by anchoring triggers more firmly on Vitest-specific terms (e.g., 'Use when the project uses Vitest' or mentioning vitest.config.ts).

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete capabilities — 'unit and integration testing patterns, commands, mocking (vi.mock), and coverage' — covering the full domain of the skill comprehensively, matching the anchor for multiple specific concrete actions.	5 / 5
Completeness	It explicitly answers both what it does ('Vitest unit and integration testing patterns, commands, mocking (vi.mock), and coverage') and when to use it ('Use when writing .test.ts files, configuring the test runner, or adding coverage thresholds') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural-term coverage including the file extension '.test.ts files', 'configuring the test runner', 'adding coverage thresholds', and 'vi.mock', but a few common variations users would say are missing (e.g., 'unit tests', 'integration tests', 'test coverage', 'spying').	4 / 5
Distinctiveness Conflict Risk	Naming Vitest, vi.mock, and .test.ts gives it a clear niche with minimal conflict risk, but generic trigger phrases like 'writing .test.ts files' and 'configuring the test runner' could also fire for a competing framework skill (e.g., Jest), so minor overlap risk remains.	4 / 5
	Total	18 / 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: monkilabs/opencastle
Path: src/orchestrator/plugins/vitest/SKILL.md
Commit: c0f4566

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.