vitest-test-creator
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.mdQuality
Discovery
7%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 description is severely underdeveloped, functioning more as a label than a useful skill description. It provides no information about what actions the skill performs, lacks natural trigger terms users would say, and has no guidance for when Claude should select it. The only redeeming quality is the specific mention of 'Vitest' which provides minimal distinctiveness.
Suggestions
Add specific actions the skill performs, e.g., 'Creates Vitest test files with describe/it blocks, generates assertions, sets up mocks and spies, configures test suites'
Add a 'Use when...' clause with natural trigger terms like 'write vitest tests', 'unit tests', 'test file', '.test.ts', 'spec', 'testing with vitest'
Include file extensions and common phrases users say: '.test.ts', '.spec.ts', 'add tests for', 'test coverage', 'mock dependencies'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Vitest Test Creator') and category ('Test Automation') but provides no concrete actions. It doesn't explain what the skill actually does - no mention of creating tests, writing assertions, mocking, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and has no 'Use when...' clause or equivalent guidance for when Claude should select this skill. Both the what and when are essentially missing. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('vitest test creator' listed twice) and overly specific. Missing natural user phrases like 'write tests', 'unit tests', 'test file', 'testing', '.test.ts', or 'spec file' that users would actually say. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Vitest' specifically does provide some distinctiveness from generic testing skills or Jest-specific skills. However, the lack of detail about what makes this different from other test creation tools limits its distinctiveness. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%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 placeholder template with no actual instructional content. It describes what a Vitest test creator skill would do but provides zero actionable guidance, code examples, or Vitest-specific information. The entire content could be replaced with a single sentence: 'This skill helps with Vitest testing.'
Suggestions
Add executable Vitest test examples showing basic test structure, assertions, and common patterns (e.g., `describe`, `it`, `expect` blocks)
Include concrete code for mocking with Vitest's `vi.mock()` and `vi.fn()` functions
Provide a quick-start workflow: 1) Create test file, 2) Write test cases, 3) Run with `npx vitest`, 4) Check coverage
Remove all meta-description content ('This skill provides...', 'When to Use...') and replace with actual Vitest testing guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about Vitest. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude already understands. | 1 / 3 |
Actionability | No concrete code, commands, or executable examples are provided. The skill describes what it does abstractly ('provides step-by-step guidance') but never actually provides any guidance, test patterns, or Vitest-specific syntax. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The content only describes trigger conditions and vague capabilities without any actual sequence of actions for creating Vitest tests. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no structure pointing to actual content. There are no references to detailed materials, examples, or related documentation. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
0c08951
- 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.