CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

70

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is react-testing in affaan-m/ECC

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 thorough, highly actionable skill body packed with executable code examples and clear guidance across the React testing domain. The main weakness is conciseness, where some explanatory prose and inlined reference-style content could be trimmed or split out.

Suggestions

Tighten prose in the 'Core Principle', 'When NOT to Use Snapshot Tests', and 'Anti-Patterns' sections to direct statements without rationale padding Claude already knows.

Consider moving the MSW setup details and coverage-target tables into a reference file in ./references/ and linking to it, keeping SKILL.md as a tighter overview.

Add common testing synonyms ('unit test', 'spec', 'test suite') to the description trigger phrases for better recall.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence throughout — no padding explaining what React Testing Library or testing concepts are — though some prose around decision boundaries and anti-patterns could be tightened further.

4 / 5

Actionability

Fully executable, copy-paste-ready code throughout: MSW server setup, userEvent interaction, renderHook, axe assertions, coverage config, and concrete test commands covering the common cases.

5 / 5

Workflow Clarity

The TDD section sequences RED/GREEN/REFACTOR with an explicit 'Verify it fails for the right reason' checkpoint and coverage thresholds validate progress; not a destructive or batch operation, so a full validate-fix-retry loop is not required.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with one-level-deep cross-skill references (accessibility, e2e-testing); no bundle files exist, and the substantial inline content is appropriately structured though much of it could live in separate reference files.

4 / 5

Total

17

/

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, specific description that names concrete tools and capabilities while explicitly stating activation triggers. Minor gap is the absence of common testing synonyms like 'unit test' or 'spec'.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities with named tools — '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' — giving comprehensive coverage of actions rather than vague language.

5 / 5

Completeness

Explicitly answers both what ('React component testing with...') and when ('Use when writing or fixing tests for React components, hooks, or pages') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases a user would say ('writing or fixing tests for React components, hooks, or pages') but omits common synonyms like 'unit test', 'spec', or 'test suite' that users also say.

4 / 5

Distinctiveness Conflict Risk

Carves a clear React-component-testing niche and even calls out the boundary against Playwright/Cypress E2E, minimizing overlap with adjacent testing skills.

5 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.