react-testing

React component testing with React Testing Library, Vitest/Jest, MSW for network mocking, accessibility assertions with axe, and the decision boundary between component tests and Playwright/Cypress end-to-end runs. Use when writing or fixing tests for React components, hooks, or pages.

Quality

87%

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

78%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, well-organized React testing reference rich in executable examples. Its main gaps are mild verbosity on concepts Claude already knows and a monolithic single-file structure that does not leverage progressive disclosure via separate reference files.

Suggestions

Trim concept restatements Claude already knows (the 'A test should / should NOT' list and the RED/GREEN/REFACTOR TDD block) to tighten conciseness.

Split the larger inlined blocks — full MSW setup, coverage thresholds config, and the worked Examples section — into separate reference files referenced one level deep from SKILL.md to improve progressive disclosure.

Add a brief validate-fix-retry feedback loop for the flakiness-prone flows already hinted at (e.g., the QueryClient-instantiation and console.error-spy notes) to lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	Mostly lean executable patterns with little concept-padding, but sections like 'A test should / A test should NOT' and the RED/GREEN/REFACTOR TDD block restate concepts Claude already knows and could be trimmed.	4 / 5
Actionability	Dense with copy-paste-ready executable code — MSW setup, renderWithProviders, renderHook, axe assertions, vitest/jest config and commands — covering the common cases comprehensively.	5 / 5
Workflow Clarity	Provides clear sequences where they matter (TDD RED/GREEN/REFACTOR, the RTL-vs-Playwright-vs-E2E decision boundary, error-boundary suppress/restore), but the skill is primarily a pattern catalogue rather than one coherently sequenced workflow with explicit validate-fix-retry feedback loops.	4 / 5
Progressive Disclosure	Well-sectioned with clear headers and outbound links to sibling skills, but everything (full MSW setup, coverage config, multiple worked examples) is inlined in one ~400-line file with no bundle files split out one level deep.	3 / 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, specific description that names concrete tools and actions and provides an explicit 'Use when' trigger clause. Its only weakness is adjacency to other testing skills, which carries minor conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions and tools — 'React Testing Library, Vitest/Jest, MSW for network mocking, accessibility assertions with axe' plus 'the decision boundary between component tests and Playwright/Cypress end-to-end runs' — giving comprehensive coverage of the niche.	5 / 5
Completeness	Explicitly answers both 'what' (component testing, network mocking, a11y assertions, E2E decision boundary) and 'when' via the concrete 'Use when writing or fixing tests for React components, hooks, or pages' clause.	5 / 5
Trigger Term Quality	Includes natural user phrases like 'writing or fixing tests for React components, hooks, or pages' alongside tool names and synonyms (Vitest/Jest), covering the common ways users request React testing help.	5 / 5
Distinctiveness Conflict Risk	Carves a clear React component-testing niche and even frames the RTL-vs-Playwright/Cypress boundary, but it sits adjacent to sibling testing skills (e2e-testing, tdd-workflow) creating minor overlap risk.	4 / 5
	Total	19 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
relative_links	Relative link issues: 7 suspicious	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Path: skills/react-testing/SKILL.md
Commit: d8409a4

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.