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.
75
62%
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), provides explicit trigger guidance with both 'Use when' and 'Triggers on' clauses, and is distinctive enough to avoid conflicts with other skills. The main weakness is that the capability descriptions are somewhat categorical rather than listing specific concrete actions, which slightly reduces specificity.
Suggestions
Add more specific concrete actions such as 'optimize FlatList rendering, configure Reanimated animations, bridge native modules, set up Expo config plugins' to increase 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 with React Native/Expo) and 'when' (explicit 'Use when...' clause covering components, list performance, animations, native modules, plus a 'Triggers on...' clause with additional terms). | 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 app development. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to React Native and Expo mobile development, which is a distinct niche. The specific mention of native modules, Expo, and mobile performance makes it unlikely to conflict with general React web development or other frontend skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
35%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 for React Native best practices, but it lacks any actionable content of its own—no code examples, no concrete instructions, no executable guidance. It relies entirely on referenced rule files that aren't provided in the bundle, making it a directory rather than a skill. The categorization and prioritization are strengths, but the absence of any substantive inline content significantly limits its utility.
Suggestions
Add at least 2-3 inline code examples for the highest-priority rules (e.g., FlashList usage for list-performance-virtualize, transform/opacity animation for animation-gpu-properties) so the skill has standalone actionable value.
Remove or condense the 'When to Apply' and 'Each rule file contains' sections—Claude can infer when React Native rules apply and what rule files contain.
Include at least one concrete workflow (e.g., 'Optimizing a slow list: 1. Replace FlatList with FlashList, 2. Memoize items, 3. Profile with Flipper, 4. Verify blank area metrics') with validation steps.
Provide the referenced bundle files (rule .md files or AGENTS.md) or inline the most critical rules to ensure the skill is usable in isolation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably organized but includes some unnecessary framing (e.g., 'Comprehensive best practices' intro, 'When to Apply' section that restates obvious triggers). The priority table and quick reference lists are efficient, but the overall structure could be tighter—the 'How to Use' and 'Each rule file contains' sections explain things Claude can infer. | 2 / 3 |
Actionability | The skill provides no executable code, no concrete examples, and no specific commands. It is essentially a table of contents pointing to rule files that aren't provided. There's nothing copy-paste ready or directly actionable—it describes rather than instructs. | 1 / 3 |
Workflow Clarity | The priority table provides a clear sequence of what matters most, and the categorization is logical. However, there are no actual workflow steps, no validation checkpoints, and no guidance on how to apply these rules in practice during development. For a reference/catalog skill this is acceptable but not exemplary. | 2 / 3 |
Progressive Disclosure | The skill references individual rule files (e.g., 'rules/list-performance-virtualize.md') and a compiled 'AGENTS.md', which is good progressive disclosure structure. However, no bundle files are provided, so we can't verify these references exist. The SKILL.md itself is mostly a catalog with no substantive quick-start content—it's almost entirely pointers without enough standalone value. | 2 / 3 |
Total | 7 / 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
4ec6f84
- 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.