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.
87
81%
Does it follow best practices?
Impact
99%
1.65xAverage score across 3 eval scenarios
Passed
No known issues
Quality
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 strong trigger terms and completeness. It clearly identifies when to use the skill and targets a specific technology niche. The main weakness is that the capabilities could be more concrete - listing specific actions like 'configure Metro bundler', 'implement gesture handlers', or 'optimize FlatList rendering' would strengthen specificity.
Suggestions
Replace general action categories with specific concrete actions (e.g., 'configure FlatList virtualization, implement Reanimated animations, bridge native modules' instead of 'optimizing list performance, implementing animations')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (React Native/Expo) and mentions some actions like 'building components', 'optimizing list performance', 'implementing animations', and 'working with native modules', but these are somewhat general categories rather than multiple specific concrete actions like 'create FlatList with virtualization' or 'configure Reanimated gestures'. | 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...' plus explicit 'Triggers on' clause). Has explicit trigger guidance. | 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 naturally use when working in this space. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on React Native/Expo mobile development. The combination of 'React Native', 'Expo', 'native modules', and 'mobile performance' creates a distinct trigger profile 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 is a well-structured index/navigation skill that efficiently organizes React Native best practices into prioritized categories with clear references to detailed rule files. Its main weakness is the lack of inline executable examples - users must navigate to external files for actual code guidance. The progressive disclosure and organization are excellent, but actionability suffers from being purely referential.
Suggestions
Add 1-2 inline code examples for the most critical patterns (e.g., FlashList usage, GPU animation properties) so the skill provides immediate value without requiring file navigation
Include a brief 'Common mistakes to avoid' section with concrete anti-patterns and fixes for the highest-priority categories
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and well-organized, using tables and bullet lists efficiently. It assumes Claude's competence with React Native concepts and doesn't waste tokens explaining what React Native or Expo are. | 3 / 3 |
Actionability | While the skill provides a comprehensive index of rules with clear naming conventions, it lacks executable code examples in the main file. The actual actionable guidance is deferred to external rule files, making this more of a navigation document than directly actionable content. | 2 / 3 |
Workflow Clarity | The priority table provides good sequencing for which concerns to address first, but there are no explicit validation steps or feedback loops for implementing these patterns. For a reference/index skill this is acceptable but not exemplary. | 2 / 3 |
Progressive Disclosure | Excellent structure with 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. Navigation is intuitive and appropriately layered. | 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.
90d6bd7
Table of Contents
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.