javascript-testing-patterns

Implement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development. Use when writing JavaScript/TypeScript tests, setting up test infrastructure, or implementing TDD/BDD workflows.

Quality

66%

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 ./skills/javascript-testing-patterns/SKILL.md

Quality

Content

40%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.

The body is lean and well-sectioned but offers almost no executable guidance — the Instructions are abstract meta-steps and all detailed patterns are deferred to a resource file that is missing from the bundle. This makes the skill largely non-actionable as written.

Suggestions

Add at least one concrete, copy-paste-ready testing example inline (e.g., a minimal Jest/Vitest test block) so the skill is actionable without the missing resource.

Either provide `resources/implementation-playbook.md` in the bundle or remove the reference to it; a dangling path breaks the promised progressive-disclosure navigation.

Replace the generic Instructions bullets with a real sequenced workflow with explicit validation checkpoints (e.g., run tests → read failures → fix → re-run until green).

Dimension	Reasoning	Score
Conciseness	The body is short and assumes Claude's competence without explaining basic concepts, but the opening sentence restate the description and the 'Do not use this skill when' bullets ('The task is unrelated to javascript testing patterns') are tautological padding, keeping it just below anchor 5.	4 / 5
Actionability	Instructions are abstract meta-directives ('Apply relevant best practices and validate outcomes', 'Provide actionable steps and verification') with no concrete code, commands, or testing patterns, and the only detailed resource referenced does not exist in the bundle — minimal concrete guidance as in anchor 2.	2 / 5
Workflow Clarity	A rough four-step sequence exists (clarify → apply/validate → provide steps → optionally open playbook) but steps are generic meta-instructions with no concrete commands or explicit validation checkpoints, matching anchor 2's 'rough sequence, many gaps, validation absent' rather than the better-defined anchor 3.	2 / 5
Progressive Disclosure	The single referenced file `resources/implementation-playbook.md` is a dangling reference — no resources/ directory or file exists in the bundle — so the one-level-deep navigation it promises leads nowhere, which is worse than the merely-buried references of anchor 2 and far from the well-signaled, resolvable references of anchor 4-5.	2 / 5
	Total	10 / 20 Passed

Description

92%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 description that states concrete capabilities, names specific frameworks, and provides an explicit 'Use when' trigger clause with natural phrasing. The only minor gap is the absence of file-extension synonyms like .test.js that users sometimes mention.

Dimension	Reasoning	Score
Specificity	Names concrete actions across the testing spectrum — 'unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development' — plus specific frameworks (Jest, Vitest, Testing Library), giving comprehensive coverage rather than the 1-2 actions of anchor 3.	5 / 5
Completeness	Explicitly answers both 'what' (implement testing strategies for unit/integration/E2E with mocking, fixtures, TDD) and 'when' ('Use when writing JavaScript/TypeScript tests, setting up test infrastructure, or implementing TDD/BDD workflows') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural-phrase coverage ('writing JavaScript/TypeScript tests', 'setting up test infrastructure', 'TDD/BDD workflows') plus framework names, but misses common synonyms and file extensions like .test.js/.spec.ts that anchor 5 requires.	4 / 5
Distinctiveness Conflict Risk	Scoped narrowly to JS/TS testing with named frameworks and specific trigger contexts, creating a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	19 / 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: rmyndharis/antigravity-skills
Path: skills/javascript-testing-patterns/SKILL.md
Commit: 3eff4af

Reviewed: 24 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.