Name: testing
Rating: 69.6 (1 reviews)
Author: redis

testing

Unit/integration testing standards for RedisInsight using Jest and Testing Library: test structure, the `renderComponent` helper, faker for test data, mocking patterns, and `waitFor` instead of fixed time waits. Use when writing or modifying any `*.spec.ts` or `*.spec.tsx` file, when adding component or slice tests, when debugging flaky tests, or when the user mentions jest, testing library, faker, or test patterns.

Quality

85%

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

75%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 highly actionable reference skill with executable code and clear organization across all testing layers. Its main weakness is redundancy across example patterns and full inlining of content that could be split into reference files.

Suggestions

Consolidate the repeated renderComponent and faker factory examples into a single canonical snippet referenced elsewhere, removing the duplicated fixed-timeout section.

Extract the per-context patterns (frontend/backend/E2E factory definitions and service/controller boilerplate) into a references/ file and link to it from SKILL.md to reduce token load.

Add an explicit validation/verification checkpoint (e.g., run the spec and confirm it passes deterministically before committing) as a final step in the workflow.

Dimension	Reasoning	Score
Conciseness	Mostly efficient prose with little concept padding, but noticeable redundancy (renderComponent shown three times, faker factory pattern shown four times, fixed-timeout guidance duplicated across two sections) that could be tightened, fitting the mostly-efficient-but-could-be-tighter anchor 3.	3 / 5
Actionability	Provides fully executable, copy-paste-ready code with imports and exact run commands across frontend, backend, and E2E contexts, matching the fully-executable anchor 5.	5 / 5
Workflow Clarity	Logically organized standards skill with a verification checklist; not a destructive multi-step process so the cap-3 rule does not apply, but it lacks an explicit sequenced procedure with validation feedback loops, landing at clear-organization anchor 4.	4 / 5
Progressive Disclosure	Well-organized with clear section headers and no nested references, but all content is inlined in one ~510-line file with no bundle files or external references, and substantial repeated patterns could have been split out, fitting good-structure anchor 4.	4 / 5
	Total	16 / 20 Passed

Description

96%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 concretely lists capabilities and provides explicit, multi-condition 'Use when' triggers including file extensions and tool names. Its only weakness is the slightly generic 'test patterns' phrase, which adds minor overlap risk.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete capabilities (test structure, renderComponent helper, faker for test data, mocking patterns, waitFor over fixed waits), matching the comprehensive-coverage anchor 5.	5 / 5
Completeness	Explicitly answers both 'what' (testing standards and listed capabilities) and 'when' (writing/modifying spec files, adding tests, debugging flaky tests, mentioning the tools) with concrete trigger phrases, matching anchor 5.	5 / 5
Trigger Term Quality	Includes natural user phrases and file extensions (.spec.ts/.spec.tsx) plus tool names users actually mention (jest, testing library, faker, flaky tests), giving comprehensive keyword coverage with synonyms and extensions.	5 / 5
Distinctiveness Conflict Risk	Clear niche tied to RedisInsight Jest/Testing Library with distinct file-pattern triggers; the broad phrase 'test patterns' introduces minor overlap risk with general testing skills, keeping it just below 5.	4 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (511 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: redis/RedisInsight
Path: .ai/skills/testing/SKILL.md
Commit: 6029714

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.