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:secondsky/claude-skills --skill react-native-skills82
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/skillValidation 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 excellent completeness and distinctiveness. 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 the specificity.
Suggestions
Replace general categories with specific concrete actions (e.g., 'configure FlatList virtualization, implement Reanimated animations, set up native module bridges' 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 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...' 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 skill serves well as an index/navigation document for React Native best practices, with excellent organization and progressive disclosure. However, it functions more as a table of contents than a standalone skill - the actual actionable guidance lives in referenced files. Adding at least one or two inline code examples for the most critical rules would significantly improve immediate actionability.
Suggestions
Add 1-2 inline executable code examples for the highest-priority rules (e.g., FlashList usage pattern) so Claude has immediately actionable guidance without needing to read external files
Include a brief workflow section describing how to apply these rules during development (e.g., 'When building a new list component: 1. Start with FlashList, 2. Memoize items, 3. Test with large datasets')
| 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 explain basics like what FlashList or Reanimated are. | 3 / 3 |
Actionability | While the skill provides a comprehensive index of rules with clear naming conventions, it lacks executable code examples directly in the SKILL.md. The actual actionable guidance is deferred to external rule files rather than being immediately usable. | 2 / 3 |
Workflow Clarity | The 'When to Apply' section provides context for usage, and the priority table gives clear sequencing of concerns. 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
87%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 14 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 14 / 16 Passed | |
- 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.