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 identifies its niche (Vitest testing for Vite projects), lists specific concrete actions, and includes an explicit 'Use when' trigger clause. The inclusion of framework-specific API terms (vi.fn, vi.mock, vitest.config.ts) provides excellent distinctiveness and natural trigger terms that users would actually use.
| 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 in Vite projects with specific API references (vi.fn, vi.mock, vitest.config.ts) that distinguish it from generic testing skills or other test framework skills like Jest or Mocha. | 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 a well-crafted skill that serves as an exemplary overview document. It provides just enough executable content to get started, then cleanly delegates to topic-specific reference files with clear navigation cues. The loading checklist with task-based guidance is a particularly effective pattern for managing token budget.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It doesn't explain what Vitest is beyond a one-line description, assumes Claude knows how testing frameworks work, and every section serves a clear purpose. The 'When to Use' section is brief and useful for routing. | 3 / 3 |
Actionability | Provides fully executable code: npm install command, complete vitest.config.ts, and a working test file with proper imports. The quick start is copy-paste ready and covers the essential setup pattern. | 3 / 3 |
Workflow Clarity | For this skill, the workflow is straightforward (install → configure → write tests), and the quick start presents these steps in clear sequence. The checklist for loading reference files provides an explicit decision workflow. No destructive or batch operations require validation checkpoints. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a concise overview in SKILL.md and well-organized references split by concern (config, test API, mocking, utilities, advanced). The reference table and loading checklist with clear guidance ('DO NOT load all files at once') demonstrate ideal navigation structure. | 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.
3110745
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.