CtrlK
BlogDocsLog inGet started
Tessl Logo

react-native-testing

Write tests using React Native Testing Library (RNTL) v13 and v14 (`@testing-library/react-native`). Use when writing, reviewing, or fixing React Native component tests. Covers: render, screen, queries (getBy/getAllBy/queryBy/findBy), Jest matchers, userEvent, fireEvent, waitFor, and async patterns. Supports v13 (React 18, sync render) and v14 (React 19+, async render). Triggers on: test files for React Native components, RNTL imports, mentions of "testing library", "write tests", "component tests", or "RNTL".

93

1.70x
Quality

91%

Does it follow best practices?

Impact

94%

1.70x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

93%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 tight, highly actionable reference skill with excellent progressive disclosure and almost no padding. The main improvement would be adding an explicit numbered test-writing workflow with a verify step.

Suggestions

Add a short numbered 'Writing a test' workflow (detect version -> render -> query -> assert -> run test) with an explicit verify/run checkpoint to lift workflow clarity.

Make the version-detection step show the exact package.json lookup command so the entry point is fully copy-pasteable.

DimensionReasoningScore

Conciseness

Lean and table-driven with no padding; it avoids explaining what React Native or testing libraries are, and the one prose note (training-data may be outdated) earns its place for a version-sensitive API.

5 / 5

Actionability

Fully executable, copy-paste-ready examples (userEvent.setup, fireEvent, render with wrapper, waitFor) plus concrete matcher and query tables cover the common cases directly.

5 / 5

Workflow Clarity

Version Detection gives a clear decision branch (check package.json then load v13/v14 reference) and the Rules act as a checklist, but there is no end-to-end numbered 'write a test' sequence with an explicit run-and-verify checkpoint.

4 / 5

Progressive Disclosure

SKILL.md is an overview with well-signaled one-level-deep references (api-reference-v13.md, api-reference-v14.md, anti-patterns.md), all real files listed in a References section with descriptions; bulk detail is appropriately split out.

5 / 5

Total

19

/

20

Passed

Description

88%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 clearly states capabilities and trigger conditions with good keyword coverage and a distinct RN-testing niche. The only gap is the absence of file-extension triggers and slight generic-trigger overlap with web RTL.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and APIs ("Write tests", "render, screen, queries ... Jest matchers, userEvent, fireEvent, waitFor, and async patterns") with comprehensive coverage of the testing workflow, matching the 'multiple specific concrete actions' anchor.

5 / 5

Completeness

Explicitly answers both what ("Write tests using React Native Testing Library v13 and v14") and when ("Use when writing, reviewing, or fixing React Native component tests" plus a concrete "Triggers on" clause), matching the top anchor.

5 / 5

Trigger Term Quality

Good natural keyword coverage including synonyms ("RNTL", "testing library", "write tests", "component tests"), but no file extensions (e.g. .test.tsx) which the top anchor expects, placing it just below comprehensive.

4 / 5

Distinctiveness Conflict Risk

Clear RN-specific niche with version-specific triggers, but the generic "mentions of testing library" trigger creates minor overlap risk with a closely related web React Testing Library skill.

4 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
callstack/react-native-testing-library
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.