generate-tests

Generate comprehensive unit tests for a Spark UI component using Vitest and React Testing Library. Use when the user wants to add tests, improve test coverage, or test a specific component.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

72%

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

A compact, well-organized skill body that avoids over-explaining known concepts and navigates cleanly. It is held back by a code template that relies on placeholders rather than fully executable examples and by the absence of an explicit verify-and-fix loop around running the tests.

Suggestions

Replace the placeholder query and empty accessibility comment in the code template with a concrete, runnable assertion so the example is copy-paste ready.

Add an explicit validation checkpoint after "Run Tests": instruct to confirm all tests pass, read any failures, fix the component or test, and re-run until green.

Optionally expand the capability statement so the "What to Test" guidance maps to a couple of concrete, named test cases rather than generic bullets.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it states file location, libraries, a code skeleton, what-to-test bullets, and run commands without explaining what Vitest or React Testing Library are, so every section earns its place.	3 / 3
Actionability	The npm commands and file-location rule are concrete, but the primary code example is a non-executable template ("screen.getByRole('...')" placeholder and an empty "// Accessibility tests" comment) rather than the copy-paste-ready code the score-3 anchor expects.	2 / 3
Workflow Clarity	The numbered instructions give a usable sequence but lack an explicit validation checkpoint — "Run Tests" lists commands yet never says to confirm all tests pass and fix failures before finishing, fitting the score-2 anchor of steps present but checkpoints implicit.	2 / 3
Progressive Disclosure	Content is organized into clearly labeled sections (When to Use, Instructions, Examples) with a single one-level reference to existing test files in the codebase and no nested or monolithic structure, satisfying the well-organized-sections bar for a compact skill.	3 / 3
	Total	10 / 12 Passed

Description

90%

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 well-formed, third-person description that cleanly answers both what the skill does and when to invoke it, with strong natural trigger terms and a distinct niche. Its only weakness is that the capability statement is a single action rather than a list of several concrete actions.

Dimension	Reasoning	Score
Specificity	"Generate comprehensive unit tests for a Spark UI component using Vitest and React Testing Library" names the domain and tooling but describes essentially one capability rather than the multiple distinct concrete actions (e.g. extract/fill/merge) that the score-3 anchor requires.	2 / 3
Completeness	It clearly answers both halves: what ("Generate comprehensive unit tests for a Spark UI component using Vitest and React Testing Library") and when ("Use when the user wants to add tests, improve test coverage, or test a specific component"), matching the score-3 anchor with an explicit Use-when trigger.	3 / 3
Trigger Term Quality	Natural user-facing terms are well covered — "add tests", "improve test coverage", "test a specific component", and the explicit keyword list "test", "testing", or "test coverage" are all things a user would naturally say.	3 / 3
Distinctiveness Conflict Risk	The narrow Spark UI component + Vitest/RTL niche with dedicated testing triggers is clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: leboncoin/spark-web
Path: .cursor/skills/generate-tests/SKILL.md
Commit: 9f4792e

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.