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.

79

1.05x
Quality

77%

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

65%Weight 40%Scale 1-3

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

A highly actionable Vitest cheat sheet with strong executable examples, but it is a monolithic file that restates some basic matchers Claude already knows and lacks an explicitly sequenced workflow. Splitting reference material into bundled files and trimming common-knowledge matchers would raise quality.

Suggestions

Trim the generic assertions catalog (toBe/toEqual/toBeTruthy/etc.) to only Vitest-specific or non-obvious matchers, since Claude already knows these from Jest.

Move the detailed mocking, assertions, and coverage references into bundled files under references/ (e.g. MOCKING.md, ASSERTIONS.md) and link to them one level deep, keeping SKILL.md a concise overview.

Add a short explicitly sequenced workflow (install → write test → run with `bun test --run` → check coverage against thresholds) with a validation checkpoint so the core loop is unambiguous.

DimensionReasoningScore

Conciseness

The body is mostly lean code-with-headers, but the generic assertions catalog (toBe, toEqual, toBeTruthy, etc.) and basic mocking patterns restate matchers Claude already knows from Jest, so it could be tightened.

2 / 3

Actionability

It provides copy-paste-ready executable code and concrete commands throughout — vitest.config.ts, `bun test --run`, `vi.mock`, supertest integration — with specific flags and the helpful verbose/tree reporter note.

3 / 3

Workflow Clarity

Sections imply an install → configure → run flow, but there is no explicitly sequenced workflow with validation checkpoints or feedback loops; for a reference skill this is acceptable but not exemplary.

2 / 3

Progressive Disclosure

It is well-organized into clear sections but is a ~240-line monolith with no bundle files; content like the assertions catalog and mocking guide could be split into one-level-deep reference files.

2 / 3

Total

9

/

12

Passed

Description

90%Weight 40%Scale 1-3

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 concise, well-structured description that states capabilities and gives an explicit use-trigger, with good natural keyword coverage and a clear niche. Its only weakness is feature-flavored phrasing with light adjectival padding rather than crisp action verbs.

DimensionReasoningScore

Specificity

It lists several concrete capabilities ('Fast unit and integration tests, native ESM support, Vite-powered HMR, and comprehensive mocking'), but these are feature claims with adjective fluff rather than crisp action verbs, so it sits below the multi-action anchor.

2 / 3

Completeness

It answers both 'what' (TS/JS testing with Vitest, mocking, ESM, HMR) and 'when' via the explicit trigger 'Use for testing TS/JS projects.', satisfying the what-and-when anchor.

3 / 3

Trigger Term Quality

Natural terms a user would say are well covered — 'testing', 'TypeScript/JavaScript', 'TS/JS projects', 'Vitest', 'unit and integration tests' — and 'Use for testing TS/JS projects' reads like a phrase a user would actually utter.

3 / 3

Distinctiveness Conflict Risk

Naming Vitest and scoping to unit/integration testing (vs. the See Also E2E/mutation skills) gives it a clear niche unlikely to trigger for the wrong skill.

3 / 3

Total

11

/

12

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.