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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

92%

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

An action-dense, mostly lean reference with executable examples and a well-sequenced TDD workflow. The main weakness is progressive disclosure: a large monolithic body with no skill-owned reference files, where several detailed sections could be extracted into clearly signaled one-level-deep references.

Suggestions

Extract the MSW setup block, coverage configuration, and the Examples section into separate reference files (e.g., references/msw.md, references/coverage.md, references/examples.md) and link to them from the body with clearly signaled one-level-deep pointers.

Move the per-runner test commands and coverage threshold tables into a references/commands.md file, keeping SKILL.md as a concise overview that points to detail.

Verify any referenced bundle paths resolve to real files; currently no references/ or scripts/ directory exists, so inline-only detail prevents the file-split structure the rubric rewards.

Dimension	Reasoning	Score
Conciseness	Dense, lean content using tables (Library Choice, Query Priority, Coverage Targets, Test Commands) and complete code; it assumes Claude's competence and never pads with basics like 'what React is' or 'how a library works'. Not a 2 because there is no unnecessary explanatory bloat to tighten — every section delivers actionable patterns.	3 / 3
Actionability	Provides fully executable, copy-paste-ready code for MSW setup, userEvent, renderHook, axe assertions, plus specific commands like 'vitest run --coverage'. Not a 2 because guidance is concrete and complete rather than pseudocode or abstract direction.	3 / 3
Workflow Clarity	The TDD workflow is explicitly sequenced (RED → GREEN → REFACTOR → REPEAT) with a validation checkpoint ('Verify it fails for the right reason'), and feedback loops appear via 'onUnhandledRequest: error' and 'mockRestore' in a finally block. Not a 2 because checkpoints are explicit, not merely implicit.	3 / 3
Progressive Disclosure	Sections are well-organized and cross-link to sibling skills ('../accessibility/SKILL.md', '../e2e-testing/SKILL.md'), but everything is inline in a single ~420-line SKILL.md with no reference files of its own; MSW setup, coverage config, and the Examples section read as content that should be split out. Not a 3 because content is not appropriately split into one-level-deep reference files; not a 1 because headings and signaled cross-links give clear in-file navigation.	2 / 3
	Total	11 / 12 Passed

Description

100%

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 specific, well-triggered description in third person that answers both what and when while carving out a distinct React-testing niche. No first/second-person voice, no vague fluff, and the explicit 'Use when' clause satisfies completeness at the top of the scale.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'React component testing', 'MSW for network mocking', 'accessibility assertions with axe', 'decision boundary between component tests and Playwright/Cypress end-to-end runs' — rather than vague domain mention.	3 / 3
Completeness	Explicitly answers what ('React component testing with...') and when ('Use when writing or fixing tests for React components, hooks, or pages'), satisfying both halves with an explicit trigger clause.	3 / 3
Trigger Term Quality	The 'Use when writing or fixing tests for React components, hooks, or pages' clause plus named tools (RTL, Vitest/Jest, MSW, axe, Playwright/Cypress) mirrors natural user phrasing with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Scoped to React component testing with named libraries and an explicit E2E decision boundary, giving it a clear niche unlikely to trigger for sibling skills like e2e-testing.	3 / 3
	Total	12 / 12 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 7 suspicious	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Commit: 4130457

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.