tech-vitest
Vitest-specific testing utilities — vi.mock, vi.fn, fake timers, MSW. Use when writing tests with Vitest, mocking dependencies, or setting up test infrastructure.
70
Quality
61%
Does it follow best practices?
Impact
82%
0.83xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/framework/tech-vitest/SKILL.mdQuality
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 an excellent skill description that follows best practices. It uses third person voice, lists specific Vitest utilities, and includes an explicit 'Use when...' clause with natural trigger terms. The description is concise yet comprehensive, clearly distinguishing itself from other testing framework skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and tools: 'vi.mock, vi.fn, fake timers, MSW' along with clear activities like 'writing tests', 'mocking dependencies', and 'setting up test infrastructure'. | 3 / 3 |
Completeness | Clearly answers both what ('Vitest-specific testing utilities — vi.mock, vi.fn, fake timers, MSW') and when ('Use when writing tests with Vitest, mocking dependencies, or setting up test infrastructure') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Vitest', 'tests', 'mocking', 'vi.mock', 'vi.fn', 'fake timers', 'MSW', 'test infrastructure'. These cover both the framework name and common testing terminology. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive by specifying 'Vitest-specific' and naming Vitest-exclusive APIs (vi.mock, vi.fn). This clearly differentiates from Jest, Mocha, or other testing framework skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a generic template with Vitest keywords inserted. It completely fails to deliver on its description's promise of 'vi.mock, vi.fn, fake timers, MSW' guidance. The content provides no executable code, no concrete examples, and no Vitest-specific workflows—just abstract meta-instructions about how to use skills in general.
Suggestions
Add concrete, executable Vitest code examples showing vi.mock(), vi.fn(), and fake timer usage patterns
Include a quick-start section with copy-paste ready test setup code before referencing external files
Replace generic troubleshooting with Vitest-specific issues (e.g., 'Mock not resetting between tests' → 'Use vi.clearAllMocks() in beforeEach')
Add MSW integration examples as promised in the description, showing request handler setup with Vitest
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but contains boilerplate troubleshooting sections that don't add Vitest-specific value. The examples and workflow sections are generic templates rather than domain-specific guidance. | 2 / 3 |
Actionability | No concrete code examples, commands, or executable guidance for Vitest testing. The skill describes what to do abstractly ('Use tech-vitest guidance') but provides no actual vi.mock, vi.fn, fake timers, or MSW examples despite the description promising these. | 1 / 3 |
Workflow Clarity | The 3-step workflow is extremely generic ('Identify', 'Apply', 'Validate') with no Vitest-specific steps. No concrete validation checkpoints, no examples of test setup sequences, and no guidance on mocking workflows. | 1 / 3 |
Progressive Disclosure | References a rules index file which is appropriate structure, but the main content itself is too thin to warrant the reference. The skill body should contain actionable quick-start content before pointing elsewhere. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 10 / 11 Passed | |
- 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.