vitest-testing
Modern TypeScript/JavaScript testing with Vitest. Fast unit and integration tests, native ESM support, Vite-powered HMR, and comprehensive mocking. Use for testing TS/JS projects.
65
57%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/vitest-testing/skills/vitest-testing/SKILL.mdQuality
Discovery
50%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies the tool (Vitest) and lists some of its features, but reads more like a marketing blurb for Vitest than an actionable skill description. The 'Use for' clause is too broad to serve as an effective trigger, and the listed capabilities are mostly Vitest features rather than concrete actions the skill performs (e.g., 'write test files', 'configure vitest.config.ts', 'set up mocks').
Suggestions
Expand the 'Use for' clause into a proper 'Use when...' with specific triggers, e.g., 'Use when the user asks to write tests with Vitest, configure vitest.config.ts, create unit or integration tests, or set up mocks in a Vite-based project.'
Replace feature marketing language ('Fast', 'Vite-powered HMR', 'native ESM support') with concrete actions the skill performs, e.g., 'Writes unit and integration tests, configures test setup files, creates mocks and spies, generates coverage reports.'
Add more natural trigger terms users might say, such as 'test suite', 'spec file', 'describe block', 'test coverage', or file extensions like '.test.ts' / '.spec.ts'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (TypeScript/JavaScript testing with Vitest) and mentions some capabilities (unit and integration tests, ESM support, HMR, mocking), but several of these are feature descriptions of Vitest rather than concrete actions the skill performs (e.g., 'fill forms', 'merge documents' style actions are absent). | 2 / 3 |
Completeness | The 'what' is reasonably covered (testing with Vitest, unit/integration tests, mocking). There is a 'Use for' clause but it's extremely vague ('testing TS/JS projects') — it doesn't provide explicit trigger conditions like 'when the user mentions Vitest, wants to write tests, or needs to set up a test suite'. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Vitest', 'TypeScript', 'JavaScript', 'testing', 'unit', 'integration tests', 'mocking', and 'TS/JS'. However, it misses common variations users might say like 'test runner', 'test suite', 'spec files', '.test.ts', 'describe/it blocks', or 'coverage'. | 2 / 3 |
Distinctiveness Conflict Risk | Mentioning 'Vitest' specifically helps distinguish it from Jest or other testing frameworks, but the broad 'testing TS/JS projects' trigger could overlap with skills for Jest, Mocha, or other test runners. The distinction could be sharper. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid reference-style skill with excellent actionability - all code examples are executable and well-structured. However, it leans toward being a comprehensive cheat sheet rather than a focused skill, including assertion references and basic patterns Claude already knows. It would benefit from trimming known-to-Claude content and adding a clearer end-to-end workflow with validation steps.
Suggestions
Trim the assertions section significantly - Claude already knows standard Jest/Vitest matchers. Keep only Vitest-specific or unusual patterns.
Add a brief end-to-end workflow section (e.g., '1. Install → 2. Configure → 3. Write first test → 4. Run and verify → 5. Add coverage') with explicit validation checkpoints.
Move the detailed assertions reference and mocking patterns into a separate REFERENCE.md file, keeping SKILL.md as a leaner overview with links.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good code examples, but includes some unnecessary padding like 'Expert knowledge for testing JavaScript/TypeScript projects using Vitest - a blazingly fast testing framework powered by Vite' and a comprehensive assertions reference section that Claude already knows well. The assertions cheat sheet and some of the basic test structure examples are things Claude inherently understands. | 2 / 3 |
Actionability | All code examples are fully executable and copy-paste ready, from configuration to test writing to mocking to coverage commands. The bash commands are specific and the TypeScript examples are complete with proper imports. | 3 / 3 |
Workflow Clarity | The skill presents individual topics clearly but lacks a cohesive workflow sequence for setting up and running a test suite end-to-end. There are no validation checkpoints - for example, no guidance on verifying the config works, no error recovery steps if tests fail, and no explicit sequence tying installation → configuration → writing tests → running tests → checking coverage together. | 2 / 3 |
Progressive Disclosure | The content has good section headers and a 'See Also' section referencing related skills, but the main body is quite long and monolithic. The assertions reference and some of the mocking details could be split into separate reference files, with the SKILL.md serving as a leaner overview pointing to them. | 2 / 3 |
Total | 9 / 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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- Repository
- secondsky/claude-skills
- Commit
88da5ff
- 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.