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
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 essentially a title and category label with no substantive content. It fails to describe what the skill actually does, provides no natural trigger terms beyond the skill's own name repeated, and lacks any 'Use when...' guidance. It would be nearly indistinguishable from other testing skills in a large skill library.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates Vitest unit tests, creates test suites with mocks and assertions, scaffolds .test.ts files for components and utilities.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to write tests, create unit tests, add test coverage, or mentions Vitest, .test.ts, or spec files.'
Remove the redundant duplicate trigger term and replace with varied natural language terms users would actually say, such as 'unit test', 'test file', 'write tests', 'vitest config', 'test coverage'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Vitest Test Creator') and category ('Test Automation') but lists no concrete actions like 'generates unit tests', 'creates test suites', 'mocks dependencies', etc. It is essentially a title repeated with no substantive capability information. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the vague label 'Test Automation' and has no explicit 'when to use' guidance. There is no 'Use when...' clause or equivalent trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'vitest test creator' repeated twice. It misses natural user phrases like 'write tests', 'unit test', 'vitest', 'test file', 'spec', '.test.ts', 'testing', or 'coverage'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Vitest' specifically does narrow the domain compared to generic testing skills, which provides some distinctiveness. However, the lack of concrete actions and the broad 'Test Automation' category label could still cause overlap with other testing-related skills. | 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 an empty template with no substantive content. It contains no actual guidance on creating Vitest tests—no code examples, no API references, no configuration patterns, no mocking strategies, and no workflow steps. It merely restates the skill name repeatedly in generic boilerplate sections.
Suggestions
Add executable Vitest test examples showing common patterns (unit test, mocked dependency, async test) with copy-paste ready code using `describe`, `it`, `expect`, `vi.mock`, etc.
Include a concrete workflow: 1) scaffold test file, 2) write tests, 3) run `npx vitest run`, 4) check output, 5) fix failures—with validation at each step.
Add a Quick Start section with a minimal `vitest.config.ts` and a sample test file that actually runs.
Remove all generic boilerplate sections (Purpose, When to Use, Example Triggers) that provide no actionable information and replace with real technical content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'vitest test creator' excessively, and contains zero substantive information about how to actually create Vitest tests. | 1 / 3 |
Actionability | There are no concrete code examples, no executable commands, no specific Vitest API usage, no configuration snippets—nothing actionable whatsoever. Every section is vague and abstract. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequences, no validation checkpoints. The 'step-by-step guidance' mentioned in Capabilities is never actually provided. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative page with no references to detailed materials, no links to examples or configuration files, and no meaningful structure beyond generic headings. | 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
3076d78
- 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.