javascript-testing-patterns

Comprehensive guide for implementing robust testing strategies in JavaScript/TypeScript applications using modern testing frameworks and best practices.

Quality

27%

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

The canonical home for this skill is javascript-testing-patterns in rmyndharis/antigravity-skills

Quality

Content

18%Scale 1-5

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

This skill is essentially a hollow stub that provides no actionable content. It lists broad use cases and generic instructions ('Apply relevant best practices') without any concrete code, commands, examples, or specific testing patterns. It defers all substance to a referenced file that doesn't exist in the bundle, leaving Claude with nothing executable to work with.

Suggestions

Add concrete, executable code examples for at least the most common testing patterns (e.g., a Jest unit test, a mock setup, a React component test) directly in the SKILL.md.

Replace the generic instruction bullets ('Apply relevant best practices and validate outcomes') with specific, sequenced steps for common testing workflows, including validation checkpoints.

Either provide the referenced `resources/implementation-playbook.md` bundle file or inline the essential content so the skill is self-contained.

Remove the 'Do not use this skill when' section as it adds no value, and trim the 'Use this skill when' list to focus on the most important scenarios.

Dimension	Reasoning	Score
Conciseness	The 'Use this skill when' and 'Do not use this skill when' sections are somewhat padded and generic. The instructions section contains vague platitudes ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices') that don't add value. However, it's not excessively verbose overall.	3 / 5
Actionability	The skill provides zero concrete code, commands, or specific examples. Every instruction is abstract and vague ('Apply relevant best practices and validate outcomes', 'Provide actionable steps and verification'). It defers entirely to a referenced file that doesn't exist in the bundle, leaving Claude with no executable guidance.	1 / 5
Workflow Clarity	There is no meaningful workflow defined. The four bullet points in Instructions are generic platitudes with no sequencing, no specific steps, and no validation checkpoints. There is no guidance on how to actually set up tests, write them, or verify results.	1 / 5
Progressive Disclosure	The skill references `resources/implementation-playbook.md` for detailed patterns, which is a reasonable disclosure strategy in principle. However, no bundle files are provided, meaning the reference leads nowhere. The SKILL.md itself contains almost no substantive content, making it an empty shell rather than a useful overview.	2 / 5
	Total	7 / 20 Passed

Description

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

The description identifies the domain (JavaScript/TypeScript testing) but relies heavily on vague, buzzword-laden language like 'robust testing strategies', 'modern testing frameworks', and 'best practices' without specifying concrete actions or when the skill should be selected. It lacks a 'Use when...' clause and misses natural trigger terms users would actually say when needing testing help.

Suggestions

Replace vague phrases like 'robust testing strategies' and 'best practices' with concrete actions such as 'write unit tests, configure Jest/Vitest, mock dependencies, set up test coverage'.

Add an explicit 'Use when...' clause with natural trigger phrases like 'Use when the user asks about writing tests, setting up a test framework, mocking, test coverage, or debugging failing tests in JS/TS projects'.

Include specific framework names and file extensions (e.g., Jest, Vitest, Mocha, .test.ts, .spec.js) to improve trigger term quality and distinctiveness.

Dimension	Reasoning	Score
Specificity	Names the domain (testing in JavaScript/TypeScript) but actions are vague — 'implementing robust testing strategies' and 'best practices' are abstract rather than concrete actions like 'write unit tests', 'mock dependencies', or 'configure test runners'.	2 / 5
Completeness	Provides a vague 'what' (implementing testing strategies) but has no 'when' clause or trigger guidance. The absence of a 'Use when...' clause caps this at 3 per the rubric, and the weak 'what' brings it down to 2.	2 / 5
Trigger Term Quality	Includes relevant keywords like 'testing', 'JavaScript', 'TypeScript', and 'testing frameworks', but misses natural user terms like 'unit test', 'Jest', 'Vitest', 'test coverage', 'mocking', 'integration test', or 'spec files'.	3 / 5
Distinctiveness Conflict Risk	Somewhat specific to JS/TS testing, but 'testing strategies' and 'best practices' are broad enough to overlap with general coding skills, code review skills, or CI/CD skills. The lack of specific framework names or concrete testing actions increases overlap risk.	3 / 5
	Total	10 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/javascript-testing-patterns/SKILL.md
Commit: 57c135b

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