Use when writing unit/integration tests for Vite projects - configure vitest.config.ts, write test suites with describe/it, create mock implementations with vi.fn and vi.mock, set up code coverage thresholds, and run tests in parallel
95
100%
Does it follow best practices?
Impact
78%
1.50xAverage score across 3 eval scenarios
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 clearly defines its scope (Vitest testing for Vite projects), lists specific concrete actions, includes a clear 'Use when' trigger clause, and uses terminology that is both natural and distinctive. The description is concise yet comprehensive, covering configuration, test writing, mocking, coverage, and execution.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: configure vitest.config.ts, write test suites with describe/it, create mock implementations with vi.fn and vi.mock, set up code coverage thresholds, and run tests in parallel. | 3 / 3 |
Completeness | Explicitly answers both what (configure vitest, write test suites, create mocks, set up coverage, run tests in parallel) and when ('Use when writing unit/integration tests for Vite projects') with a clear 'Use when' clause at the start. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'unit tests', 'integration tests', 'Vite', 'vitest', 'mock', 'vi.fn', 'vi.mock', 'code coverage', 'describe/it', 'vitest.config.ts'. These cover both high-level concepts and specific API terms users would mention. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Vitest and Vite projects specifically, with distinct triggers like 'vitest.config.ts', 'vi.fn', 'vi.mock' that would not overlap with Jest, Mocha, or other testing framework skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill file that serves as a clean entry point for Vitest usage. It provides just enough executable content to get started while clearly directing to specific reference files based on task context. The loading checklist with task-based guidance is particularly well-designed for helping Claude select only relevant context.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. No unnecessary explanations of what Vitest is beyond a one-line description. Every section serves a clear purpose, and there's no padding or explanation of concepts Claude already knows. | 3 / 3 |
Actionability | Provides fully executable code for installation, configuration (vitest.config.ts), and a complete test example. The quick start is copy-paste ready and covers the essential setup steps. | 3 / 3 |
Workflow Clarity | For a skill that serves as an overview/entry point, the workflow is clear: install → configure → write tests → consult reference files for specific tasks. The 'Loading Files' checklist provides excellent task-based guidance for which references to consult. This is not a destructive/batch operation skill, so validation checkpoints aren't required. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a concise overview, quick start, and well-organized one-level-deep references. The reference table and task-based loading checklist make navigation easy, and the explicit instruction to not load all files at once is a smart constraint. | 3 / 3 |
Total | 12 / 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.
48efc7a
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.