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%
1.65xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/react-native-skills/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, and occupies a distinct niche. Its main weakness is that the capability descriptions are somewhat categorical rather than listing highly specific concrete actions, which keeps specificity from reaching the top score.
Suggestions
Add more specific concrete actions such as 'optimize FlatList/SectionList rendering, configure Reanimated animations, bridge native modules, manage 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, components, list performance, animations, native modules) and 'when' with explicit triggers ('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 app development. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to React Native and Expo mobile development, which is a distinct niche. The combination of 'React Native', 'Expo', 'native modules', and 'mobile performance' makes it unlikely to conflict with general web development or other framework 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 provides almost no actionable content on its own. It lacks any executable code examples, concrete commands, or specific implementation guidance—everything is deferred to external rule files that are not included in the bundle. The priority categorization is useful but insufficient to make this skill independently valuable.
Suggestions
Add at least one concrete, executable code example for the highest-priority category (e.g., FlashList usage for list-performance-virtualize) directly in the SKILL.md so it has standalone value.
Include a brief workflow section showing how to apply these rules when building a new React Native component (e.g., 'When creating a list component: 1. Use FlashList, 2. Memoize items, 3. Stabilize callbacks').
Trim the 'When to Apply' section—Claude can infer when React Native guidelines apply from context. Replace it with a concrete quick-start example.
Provide the bundle files (rule markdown files) or inline the most critical 2-3 rules so the skill is not entirely dependent on external references that may not exist.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably organized but includes some unnecessary framing (e.g., 'Comprehensive best practices for React Native and Expo applications') and the 'When to Apply' section largely restates what Claude would already infer. The priority table and quick reference lists are efficient, but the overall structure could be tighter. | 2 / 3 |
Actionability | The skill provides no executable code, no concrete commands, and no specific examples. It is entirely an index/catalog of rule names with brief descriptions. All actual guidance is deferred to external rule files that are not provided in the bundle, making this essentially a table of contents with no actionable content on its own. | 1 / 3 |
Workflow Clarity | The priority table provides a clear sequencing of what matters most, and the 'How to Use' section gives a basic workflow for navigating rules. However, there are no validation steps, no feedback loops, and no guidance on how to apply multiple rules together or resolve conflicts between them. | 2 / 3 |
Progressive Disclosure | The skill attempts progressive disclosure by referencing individual rule files and a compiled AGENTS.md, with one-level-deep references. However, no bundle files are provided, so the referenced files (rules/*.md, AGENTS.md) cannot be verified. The SKILL.md itself is almost entirely an index with very little standalone value, meaning too much content is deferred rather than appropriately split. | 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
- secondsky/claude-skills
- Commit
5e92b71
- 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.