CtrlK
BlogDocsLog inGet started
Tessl Logo

vitest-testing

Modern TypeScript/JavaScript testing with Vitest. Fast unit and integration tests, native ESM support, Vite-powered HMR, and comprehensive mocking. Use for testing TS/JS projects.

78

1.05x
Quality

76%

Does it follow best practices?

Impact

74%

1.05x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/vitest-testing/skills/vitest-testing/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, highly actionable Vitest reference dominated by executable code. Its main weakness is progressive disclosure: all detail lives inline in a single file with no bundle references.

Suggestions

Move the assertions catalog and/or mocking deep-dive into separate reference files (e.g., references/assertions.md, references/mocking.md) and link to them from SKILL.md to reduce inline bulk.

Trim redundant inline comments and the 'Expert knowledge...' intro line that restates the description.

Add a brief verification note in the running-tests section (e.g., check exit code / CI mode) to strengthen workflow clarity.

DimensionReasoningScore

Conciseness

Mostly lean code-first reference with minimal prose and little over-explanation of concepts Claude already knows; a few inline comments and the redundant intro line could be trimmed.

4 / 5

Actionability

Copy-paste ready, executable code and commands across installation, configuration, running, writing tests, assertions, mocking, timers, coverage, and integration testing, covering the common cases.

5 / 5

Workflow Clarity

Content follows a logical install -> configure -> write -> run -> mock -> coverage progression with clear sections, though there are no explicit validation checkpoints (acceptable for a non-destructive reference skill).

4 / 5

Progressive Disclosure

Well-organized with clear section headers, but it is a ~230-line monolithic reference with no bundle files or one-level-deep references to split out detailed material (e.g., assertions or mocking guides).

3 / 5

Total

16

/

20

Passed

Description

75%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A solid, specific description that names the framework and several concrete capabilities plus a use-when clause. It is held back from a 5 by a terse trigger clause and lack of synonym/extension coverage.

Suggestions

Expand the 'Use for...' clause with concrete trigger phrases (e.g., 'Use when writing or running unit/integration tests for TS/JS projects, setting up Vitest, or mocking modules').

Add natural synonyms and file extensions (e.g., '.test.ts', '.spec.ts', 'test files') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Lists several concrete capabilities ('Fast unit and integration tests, native ESM support, Vite-powered HMR, and comprehensive mocking') rather than vague language, though 'comprehensive mocking' is slightly generic, leaving minor coverage gaps.

4 / 5

Completeness

Provides a clear 'what' (modern Vitest testing with named features) and a 'when' ('Use for testing TS/JS projects'), but the trigger clause is terse and could be more explicit.

4 / 5

Trigger Term Quality

Includes natural terms users would say ('TypeScript/JavaScript testing', 'Vitest', 'unit and integration tests', 'mocking', 'TS/JS projects') with good coverage, but misses synonyms and file-extension variants.

4 / 5

Distinctiveness Conflict Risk

Naming the specific framework 'Vitest' gives a clear niche with minimal conflict risk, though 'testing TS/JS projects' could overlap with related testing skills (jest, playwright) noted in See Also.

4 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
secondsky/claude-skills
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.