vercel-react-native-skills
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
Install with Tessl CLI
npx tessl i github:vercel-labs/agent-skills --skill vercel-react-native-skills87
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 99%
↑ 2.15xAgent success when using this skill
Validation for skill structure
Discovery
89%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 a solid skill description with explicit 'Use when' and 'Triggers on' clauses that clearly define when Claude should select this skill. The trigger terms are natural and comprehensive for the React Native/Expo domain. The main weakness is that the capabilities could be more specific with concrete actions rather than general categories.
Suggestions
Add more specific concrete actions like 'configure FlatList virtualization', 'set up Reanimated animations', 'integrate native iOS/Android modules' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (React Native/Expo) and mentions some actions like 'building components', 'optimizing list performance', 'implementing animations', but these are somewhat general categories rather than multiple specific concrete actions like 'create FlatList with virtualization' or 'configure Reanimated worklets'. | 2 / 3 |
Completeness | Clearly answers both what ('React Native and Expo best practices for building performant mobile apps') and when ('Use when building React Native components, optimizing list performance...') with explicit trigger guidance including a 'Triggers on' clause. | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'React Native', 'Expo', 'mobile performance', 'native modules', 'native platform APIs', 'animations'. These are terms developers naturally use when working on mobile apps. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on React Native/Expo mobile development. The triggers are distinct enough (React Native, Expo, native modules, mobile performance) that it's unlikely to conflict with general React web skills or other mobile frameworks. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill serves as an effective index/reference document for React Native best practices with excellent organization and progressive disclosure. Its main weakness is the lack of inline executable examples - it functions more as a table of contents than a standalone actionable guide. The content assumes users will navigate to referenced files for actual implementation details.
Suggestions
Add 1-2 inline code examples for the most critical rules (e.g., FlashList usage, animation with transform/opacity) to make the skill immediately actionable without requiring file navigation
Include a brief workflow section describing how to apply these rules during development (e.g., 'When building a new list component: 1. Check list-performance rules, 2. Verify with FlashList profiler, 3. Run performance tests')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables and bullet lists to organize information without explaining concepts Claude already knows. No unnecessary padding or verbose explanations of React Native basics. | 3 / 3 |
Actionability | Provides a well-organized reference of rules with clear naming conventions and file paths, but lacks executable code examples directly in the skill. Users must navigate to separate rule files for actual implementation guidance. | 2 / 3 |
Workflow Clarity | The 'When to Apply' section provides clear triggers, and the priority table sequences categories well. However, there's no explicit workflow for how to apply these rules during development or validation steps to verify correct implementation. | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear overview, priority-ordered categories, quick reference lists, and well-signaled one-level-deep references to individual rule files and the full AGENTS.md document. | 3 / 3 |
Total | 10 / 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.