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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill vitest-test-creatorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, functioning more as a label than a useful skill description. It lacks any concrete actions, natural trigger terms, or guidance on when to use the skill. The only distinguishing element is the 'Vitest' name, but without describing what the skill actually does, Claude cannot make informed decisions about when to select it.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Creates Vitest test files, generates unit tests with mocks and assertions, sets up test suites with describe/it blocks'
Include a 'Use when...' clause with natural trigger terms like 'write vitest tests', 'unit test', 'test coverage', '.test.ts', 'spec file', 'testing React components'
Replace the duplicate trigger term with varied natural language users would actually say when needing test creation help
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Vitest Test Creator') and category ('Test Automation') without describing any concrete actions. No specific capabilities like 'creates unit tests', 'generates test suites', or 'mocks dependencies' are mentioned. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'vitest test creator' repeated twice, which is unlikely to match natural user language. Missing common variations like 'write tests', 'unit tests', 'test file', 'spec', '.test.ts', or 'testing'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Vitest' specifically does provide some distinction from generic testing skills, but 'Test Automation' is broad and could overlap with Jest, Mocha, or other testing framework skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual Vitest-specific knowledge. It contains only generic marketing-style descriptions without any executable code, concrete examples, configuration guidance, or actionable instructions for creating Vitest tests.
Suggestions
Add executable Vitest test examples showing basic test structure, assertions, and common patterns (e.g., describe/it blocks, expect matchers)
Include concrete configuration snippets for vitest.config.ts with common options like coverage, test environment, and path aliases
Provide specific mocking examples using vi.mock(), vi.fn(), and vi.spyOn() with realistic use cases
Add a workflow section with steps for creating tests: setup -> write test -> run with coverage -> validate results
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actionable information. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no Vitest-specific commands, no configuration snippets, no actual test patterns. The content describes what the skill supposedly does rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequences, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no links to examples, configuration files, or advanced topics. It mentions 'Related Skills' but provides no actual navigation. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.