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

71%

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

Fix and improve this skill with Tessl

tessl review fix ./.cursor/skills/generate-tests/SKILL.md

Quality

Content

61%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 reasonably well-organized, actionable skill body with concrete commands and a usable template, but it relies on generic testing checklists for padding and lacks an explicit verify-and-iterate checkpoint in its workflow. The code template also uses placeholders that keep it from being fully copy-paste ready.

Suggestions

Tighten the 'What to Test' and 'Accessibility Testing' lists, which overlap and restate testing basics Claude already knows; keep only Spark-specific reminders to improve conciseness.

Add an explicit validation checkpoint after 'Run Tests', e.g. 'Confirm all tests pass; if any fail, fix the component or test and re-run npm run test:run', to make the workflow's verify/feedback loop explicit.

Replace the placeholders in the code template (getByRole('...'), {...defaultProps}, '// Accessibility tests') with a concrete runnable example for a real Spark component so the guidance is copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient (file location, setup, run commands are tight), but the 'What to Test' and 'Accessibility Testing' sections restate generic testing basics Claude already knows ('Component renders correctly', 'Verify proper ARIA attributes'). Not a 4 because this generic checklist padding is noticeable; not a 2 because there is no severe concept over-explanation.	3 / 5
Actionability	Concrete executable guidance is present: real npm commands (test:ui, test:run, test:coverage), the file-naming convention, and a full import/template scaffold. Not a 5 because the code example uses placeholders (getByRole('...'), {...defaultProps}, '// Accessibility tests') that prevent it being copy-paste ready; not a 3 because it is a real template with concrete commands rather than pseudocode.	4 / 5
Workflow Clarity	Six numbered steps give a clear sequence (location, setup, structure, what to test, accessibility, run), but step 6 only lists run commands without an explicit verification checkpoint or fix-retry feedback loop. Not a 4 because 'confirm tests pass / fix failures and re-run' is implicit rather than stated; not a 2 because the sequence itself is coherent and well-ordered.	3 / 5
Progressive Disclosure	Good section structure (When to Use, Instructions, Examples) with a one-level reference to existing test files in packages/components/src/*/ComponentName.test.tsx and no nested references. Not a 5 because the Examples pointer is terse and everything is inline with no overview/detail split; not a 3 because structure is genuinely well organized, not buried or mis-placed.	4 / 5
	Total	14 / 20 Passed

Description

82%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 strong, well-structured description that clearly states both the capability and explicit trigger conditions in third person. Its only weakness is that the 'what' describes a single action rather than enumerating several concrete capabilities.

Dimension	Reasoning	Score
Specificity	It names the domain ('Spark UI component unit tests') and tooling (Vitest, React Testing Library) but describes essentially one action ('Generate comprehensive unit tests') rather than multiple distinct concrete actions; 'comprehensive' is mild fluff. Not a 4 because it does not list several specific actions, and not a 2 because the scope and tooling are concrete.	3 / 5
Completeness	It explicitly answers both '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') with concrete trigger phrases. Matches the top anchor and uses third-person voice throughout.	5 / 5
Trigger Term Quality	Natural trigger phrases are present ('add tests', 'improve test coverage', 'test a specific component', 'unit tests'), matching what a user would actually say. Not a 5 because synonyms like 'testing' and the file extension (.test.tsx) are absent; not a 3 because coverage is clearly good rather than partial.	4 / 5
Distinctiveness Conflict Risk	The 'Spark UI component' niche plus Vitest/React Testing Library tooling and test-specific triggers give it a clear, distinct niche with minimal overlap risk against other skills. Not lower because no generic phrasing that would invite conflict.	5 / 5
	Total	17 / 20 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: ae95bee

Reviewed: 1 day 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.