What does this skill do, and when should you use it?
This Agent Skill guides React Native component testing with React Native Testing Library (RNTL) v13 and v14. It covers rendering, screen queries, Jest matchers, userEvent, fireEvent, waitFor, and async testing patterns. It detects the RNTL version from package.json and routes work to the matching reference material. It is suited to developers writing, reviewing, or fixing React Native component tests.
Reads the project package.json to identify @testing-library/react-native v13 or v14, then loads the version-specific API reference; guides AI in producing or editing tests with render, screen queries, userEvent, fireEvent, waitFor, custom wrappers, and RNTL Jest matchers; and flags query-priority rules, async behavior, and common anti-patterns.
- A React Native developer adding component tests can use it to choose version-correct rendering and query patterns.
- A team maintaining a React 18 and RNTL v13 project can use it for synchronous API guidance.
- A team migrating to React 19 and RNTL v14 can use it to handle async rendering and migration differences.
- A reviewer checking files with RNTL imports can use it to assess queries, events, and waitFor usage.
- A developer testing buttons, text inputs, accessibility states, or async results can use it to select suitable queries and Jest matchers.
How do you install this skill?
- No code or tests were executed; the score does not independently validate the documented RNTL APIs.
- Before use, verify the project's actual package.json, React version, test renderer, and installed RNTL version.
- Add source citations, maintenance ownership, a changelog, and CI tests covering the key v13/v14 paths.
- Local filesystem
@testing-library/react-native v13 or v14React 18 for RNTL v13 or React 19+ for RNTL v14
The skill is located at https://github.com/callstackincubator/agent-skills in plugins/vendored/.agents/skills/react-native-testing/SKILL.md. The README says the repository supports Codex bundled plugins through .agents/plugins/marketplace.json, but it does not provide a standalone installation command for this skill.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/callstackincubator/agent-skills.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/plugins/vendored/.agents/skills/react-native-testing" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
Once installed, send your agent any of these to trigger it:
- Use RNTL v14 to write tests for this React Native component
- Review this RNTL test and fix its async query usage.
Install or place the skill in a compatible Agent Skills directory, then invoke it for React Native component-testing tasks. Example prompts: "Use RNTL v14 to write tests for this React Native component" or "Review this RNTL test and fix its async query usage." The project should declare @testing-library/react-native v13 or v14 in package.json.
What are this skill's strengths and limitations?
- Clearly separates RNTL v13 and v14 guidance, including React 18 and React 19+ differences.
- Provides concrete rules for query priority, interactions, async testing, and waitFor.
- Includes reference examples for userEvent, waitFor, custom rendering, and Jest matchers.
- Favors accessibility queries and RNTL matchers over brittle raw prop assertions.
- Covers React Native component testing, not a complete end-to-end or native-module testing strategy.
- The source provides no dedicated test suite, platform support matrix, or list of tested projects for this skill.
- Usage depends on version-specific reference files whose full contents are not included in the supplied material.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| React Native Test Guide this page | 54 · Use with care | ★ 1.7k | 19d ago | MIT |
| Playwright Component Testing ✓ Microsoft · Official | 58 · Recommended | ★ 98k | 13d ago | Apache-2.0 |
| VS Code Chat Customizations Editor Skill ✓ Microsoft · Official | 52 · Use with care | ★ 194k | 13d ago | MIT |
| React Native Library Builder | 50 · Use with care | ★ 1.7k | 19d ago | MIT |
| Expo Skill Eval | 48 · Use with care | ★ 2.9k | 22d ago | MIT |
How did FollowSkills review this skill?
The skill only provides test-writing guidance; it requests no permissions, performs no external actions, and handles no credentials or sensitive data, so its risk surface is low. Points are deducted because data flows, dependency security, user confirmation, rollback, and source verification are not specified; publisher identity is also unverified.
Version detection, v13/v14 routing, query guidance, and async rules are relatively coherent and supported by multiple reference files. Points are deducted because this static review did not execute tests, and the skill lacks project-level reproduction, abnormal-input handling, and diagnosable failure feedback; some behavior depends on actual project configuration.
The audience, React Native component-testing scenarios, trigger terms, and broad coverage are clear, with separate RNTL v13 and v14 guidance. Points are deducted because non-fit scenarios, input/output boundaries, and Chinese-language guidance are not explicit. Core functionality does not depend on unreachable overseas services, so no additional mainland-network deduction is warranted.
The documentation uses a useful layered structure of main guidance, version-specific references, and anti-patterns, with many examples, limitation notes, and MIT license context. Points are deducted because the skill itself lacks installation notes, version history, changelog, named maintenance responsibility, and a clear update path.
It covers common queries, interactions, assertions, async patterns, and custom rendering, with examples that are directly adaptable to tests and therefore provide clear practical value. Points are deducted because there is no committed representative test suite or execution evidence, and version or project-configuration differences still require manual checking.
Versioned reference files and concrete API signatures make key recommendations somewhat auditable. Points are deducted because there are no third-party sources, CI results, committed tests, or independent reproduction evidence, so static review cannot confirm the accuracy of the API and migration claims.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →