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

86%

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 concise, highly actionable single-file reference with executable commands, complete code examples, and a well-sequenced workflow featuring explicit validation and feedback loops. The only gap is the absence of progressive file splitting for a skill of this length.

Dimension	Reasoning	Score
Conciseness	The body is lean and code-forward with no concept over-explanation, but carries minor redundancy (coverage commands appear in both the Commands and Workflow sections) that keeps it just below the "every token earns its place" bar of anchor 5.	4 / 5
Actionability	Provides fully executable, copy-paste-ready vitest commands and complete TypeScript examples (module mocks, spies, fake timers, full config) that cover the common testing cases, matching the anchor-5 example.	5 / 5
Workflow Clarity	The six-step Workflow includes explicit validation checkpoints and feedback loops (run tests and fix failures; re-run coverage and add targeted tests until thresholds pass), matching anchor 5; testing is non-destructive so the cap-3 rule does not apply.	5 / 5
Progressive Disclosure	Content is well-organized into clear sections with one clearly-signaled external reference (testing-config.md), but for a 157-line skill all reference material is inlined rather than split into separate bundle files, a minor organization gap versus anchor 5.	4 / 5
	Total	18 / 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 strong, third-person description that pairs a concrete capability list with an explicit multi-trigger "Use when" clause. It is specific and complete, with only minor distinctiveness overlap against other JS test runners.

Dimension	Reasoning	Score
Specificity	Names the Vitest domain and four concrete capability areas ("testing patterns, commands, mocking (vi.mock), and coverage") with a specific named API, sitting above the 1-2 actions of anchor 3 but short of comprehensive coverage (no snapshots, fixtures, or parallelism).	4 / 5
Completeness	Clearly states what the skill does ("Vitest unit and integration testing patterns, commands, mocking (vi.mock), and coverage") and gives an explicit "Use when..." clause with three concrete trigger phrases, matching the anchor-5 example structure.	5 / 5
Trigger Term Quality	Includes the natural file-extension trigger ".test.ts files" plus "configuring the test runner" and "coverage thresholds", giving good keyword coverage, but misses common synonyms like "unit tests" or "vitest tests" that anchor 5 expects.	4 / 5
Distinctiveness Conflict Risk	The Vitest name and vi.mock API carve a distinct niche, but the ".test.ts files" and "test runner" triggers overlap with closely related Jest-style skills, so minor overlap risk keeps it at 4 rather than 5.	4 / 5
	Total	17 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: monkilabs/opencastle
Path: src/orchestrator/plugins/vitest/SKILL.md
Commit: fa0c341

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