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.
74
59%
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 is distinctive enough to avoid conflicts with other skills. 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 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 naturally use when seeking help with mobile development. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to React Native and Expo mobile development, which is a distinct niche. The specific mention of React Native, Expo, native modules, and mobile performance makes it unlikely to conflict with general React web skills or other frameworks. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
29%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 but lacks any actionable content on its own. It provides no executable code, concrete examples, or specific guidance—everything is deferred to external rule files. While the progressive disclosure and organization are strong, the skill body itself teaches Claude nothing it can directly act on without reading dozens of additional files.
Suggestions
Add at least 2-3 concrete, executable code examples for the highest-priority rules (e.g., FlashList usage, Reanimated animation pattern) directly in the skill body so Claude has immediately actionable guidance.
Include a brief workflow section describing how to apply these rules during development (e.g., 'When building a new list component: 1. Use FlashList, 2. Memoize items, 3. Verify with performance profiler').
For each category, include at least one inline before/after code snippet showing the incorrect vs correct pattern, rather than only listing rule names.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably organized but includes some unnecessary framing (e.g., 'Comprehensive best practices', 'When to Apply' section listing things Claude can infer from context). 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 essentially a table of contents pointing to other files, with only rule names and vague category descriptions. There is no actionable guidance that Claude could directly apply. | 1 / 3 |
Workflow Clarity | There is no workflow, no sequencing of steps, and no validation checkpoints. The content is a catalog/index rather than a process guide. Even for a reference skill, there's no guidance on how to apply these rules in practice or in what order during development. | 1 / 3 |
Progressive Disclosure | The content is well-structured as an overview with clear one-level-deep references to individual rule files and a compiled AGENTS.md. The priority table, categorized quick reference, and file path examples make navigation straightforward. | 3 / 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
88da5ff
- 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.