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".
Install with Tessl CLI
npx tessl i github:callstack/react-native-testing-library --skill react-native-testing100
Does it follow best practices?
Validation for skill structure
Discovery
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.
This is an exemplary skill description that excels across all dimensions. It provides specific API coverage, clear version differentiation, explicit trigger conditions, and a well-defined niche that distinguishes it from general testing or web React testing skills. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and APIs: 'render, screen, queries (getBy/getAllBy/queryBy/findBy), Jest matchers, userEvent, fireEvent, waitFor, and async patterns.' Also specifies version differences (v13 sync vs v14 async). | 3 / 3 |
Completeness | Clearly answers both what ('Write tests using RNTL...Covers: render, screen, queries...') AND when ('Use when writing, reviewing, or fixing React Native component tests. Triggers on: test files...'). Has explicit 'Use when' and 'Triggers on' clauses. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'testing library', 'write tests', 'component tests', 'RNTL', 'test files for React Native components', and 'RNTL imports'. Includes both technical and conversational triggers. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche targeting React Native Testing Library specifically, with version-specific details (v13/v14) and explicit package name (@testing-library/react-native). Unlikely to conflict with general testing or web React testing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill file that efficiently delivers actionable testing guidance for React Native Testing Library. It respects Claude's intelligence by using tables and code examples rather than verbose explanations, provides version-specific references appropriately, and includes clear rules that prevent common mistakes. The progressive disclosure to version-specific API references is well-executed.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables for quick reference, avoiding explanations of basic concepts Claude already knows, and every section provides actionable information without padding. | 3 / 3 |
Actionability | Provides fully executable code examples for userEvent, fireEvent, waitFor, and custom render patterns. The query variants table and matcher reference are copy-paste ready with clear usage guidance. | 3 / 3 |
Workflow Clarity | Clear version detection workflow at the start, explicit rules numbered 1-11 for test writing, and the waitFor section shows correct vs better patterns with clear sequencing. The skill is primarily reference-based rather than multi-step procedural, but the guidance is unambiguous. | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview in the main file and clear one-level-deep references to version-specific API docs (v13, v14) and anti-patterns. Navigation is well-signaled with descriptive links. | 3 / 3 |
Total | 12 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.