Vitest Test Creator - Auto-activating skill for Test Automation. Triggers on: vitest test creator, vitest test creator Part of the Test Automation skill category.
36
Quality
3%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/09-test-automation/vitest-test-creator/SKILL.mdVitest project setup and configuration
Vitest in package.json
100%
100%
Test script configured
100%
100%
Vitest config file present
100%
100%
Imports from vitest
100%
100%
describe() blocks used
100%
100%
it() or test() used
100%
100%
expect() assertions present
100%
100%
Descriptive test names
100%
100%
Multiple functions tested
100%
100%
Arrange/act/assert structure
100%
100%
No placeholder code
100%
100%
Without context: $0.4670 · 1m 57s · 25 turns · 26 in / 6,896 out tokens
With context: $0.5874 · 2m 24s · 30 turns · 61 in / 8,038 out tokens
Unit testing with mocking
Imports from vitest
100%
100%
Mock created for dependency
100%
100%
Mock return value configured
100%
100%
No real network calls
100%
100%
describe() blocks used
100%
100%
it() or test() used
100%
100%
Happy path tested
100%
100%
Error/edge case tested
100%
100%
Mock reset/cleanup
100%
100%
Assertions verify behavior
100%
100%
Production-ready code
100%
100%
Without context: $0.3423 · 1m 39s · 19 turns · 18 in / 5,633 out tokens
With context: $0.5527 · 2m 4s · 28 turns · 318 in / 7,098 out tokens
Integration testing with vitest
Imports from vitest
100%
100%
Multi-module interaction tested
100%
100%
External I/O is the only mock boundary
100%
100%
describe() blocks used
100%
100%
it() or test() used
100%
100%
Complete workflow covered
100%
100%
Error scenario tested
100%
100%
Assertions on observable outcomes
100%
100%
Descriptive test names
100%
100%
Production-ready code
100%
100%
Without context: $0.3812 · 1m 37s · 23 turns · 24 in / 5,088 out tokens
With context: $0.4551 · 1m 45s · 27 turns · 22 in / 5,976 out tokens
0c08951
Table of Contents
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.