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.
77
96%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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 users would actually say, and includes an explicit 'Use when' clause with concrete triggers. It is clearly scoped to Vitest, minimizing conflict risk with other testing or coding 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'. | 3 / 3 |
Completeness | Clearly answers both what ('Vitest unit and integration testing patterns, commands, mocking, and coverage') and when ('Use when writing .test.ts files, configuring the test runner, or adding coverage thresholds') with explicit trigger guidance. | 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'. These cover common variations of how users would describe testing needs. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Vitest specifically, with distinct triggers like 'vi.mock', '.test.ts', and 'Vitest' that distinguish it from other testing frameworks (Jest, Mocha, etc.) or general coding skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
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. It excels at conciseness (no unnecessary explanations), actionability (all examples are executable), and workflow clarity (clear sequence with validation loops). The only minor weakness is that the content is somewhat long for a single file, though the inline approach is justified given no bundle files are available.
| 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 provides concrete, useful information without padding. | 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. The examples cover real-world patterns (module mocking, spies, fake timers) with complete import statements and assertions. | 3 / 3 |
Workflow Clarity | The workflow section provides a clear 6-step sequence with explicit validation checkpoints: step 3 runs tests and fixes failures, step 4 provides a feedback loop with verbose reporting for debugging, and step 5 includes a coverage validation loop (inspect → add tests → re-run until thresholds pass). | 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 content is fairly long with all patterns inline (mocking, timers, configuration, workflow) — some of these could be split into separate reference files. Without bundle files to offload to, this is reasonable but not ideal. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
100%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
cc13aaf
- Reviewed
Table of Contents
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.