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.
78
66%
Does it follow best practices?
Impact
99%
2.15xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/react-native-skills/SKILL.mdQuality
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 that clearly identifies its domain (React Native/Expo mobile development) and provides explicit trigger guidance. Its main weakness is that the capability descriptions are somewhat categorical rather than listing highly specific concrete actions. Overall it performs well for skill selection purposes.
Suggestions
Add more specific concrete actions such as 'optimize FlatList rendering, configure Reanimated animations, bridge native modules, set up Expo config plugins' 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', 'working with native modules', but these are somewhat general categories rather than multiple specific concrete actions (e.g., doesn't specify FlatList optimization, Reanimated usage, bridging patterns, etc.). | 2 / 3 |
Completeness | Clearly answers both 'what' (best practices for building performant mobile apps, components, list performance, animations, native modules) and 'when' with explicit trigger guidance ('Use when building React Native components...', 'Triggers on tasks involving...'). | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'React Native', 'Expo', 'mobile performance', 'native modules', 'animations', 'list performance', 'native platform APIs'. These are terms developers would naturally use when seeking help with mobile development. | 3 / 3 |
Distinctiveness Conflict Risk | React Native and Expo form a clear niche distinct from general web development, plain React, or other mobile frameworks. The triggers are specific enough to avoid conflicts with generic JavaScript or React skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions as a well-organized table of contents/index for React Native best practices, with clear categorization and priority ordering. However, it provides almost zero actionable content on its own — no code examples, no concrete commands, no specific patterns — making it essentially useless without the referenced rule files. The progressive disclosure structure is excellent, but the overview itself should include at least minimal executable examples for the highest-priority items.
Suggestions
Add at least 2-3 concrete, executable code examples for the CRITICAL priority items (e.g., FlashList usage, memoization pattern) so the skill provides immediate value without requiring file lookups.
Include a brief workflow section showing how to apply these rules when building a new React Native screen or optimizing an existing one (e.g., 'When optimizing a list: 1. Switch to FlashList, 2. Memoize items, 3. Profile with Flipper').
Remove or condense the 'When to Apply' section — Claude already knows when React Native guidelines are relevant from the skill description and context.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably organized but includes some unnecessary framing (e.g., 'Comprehensive best practices', 'When to Apply' section listing obvious triggers). The priority table and quick reference list are efficient, but the overall structure could be tighter. | 2 / 3 |
Actionability | The skill contains no executable code, no concrete commands, and no specific examples. It is entirely an index/catalog of rule names with brief descriptions, deferring all actual guidance to external files. Claude cannot act on any of this without reading those files. | 1 / 3 |
Workflow Clarity | The priority table provides a clear ordering of categories, and the 'How to Use' section explains how to navigate to individual rules. However, there are no multi-step workflows, no validation checkpoints, and no guidance on how to apply these rules in sequence during actual development tasks. | 2 / 3 |
Progressive Disclosure | The content is well-structured as an overview/index that clearly points to individual rule files and a compiled AGENTS.md document. References are one level deep, clearly signaled with file paths, and organized by priority category. | 3 / 3 |
Total | 8 / 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.
- Repository
- vercel-labs/agent-skills
- Commit
73140fc
- 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.