react-native-expert
Senior React Native and Expo engineer for building production-ready cross-platform mobile apps. Use when building React Native components, implementing navigation with Expo Router, optimizing list and scroll performance, working with animations via Reanimated, handling platform-specific code (iOS/Android), integrating native modules, or structuring Expo projects. Triggers on React Native, Expo, mobile app, iOS app, Android app, cross-platform, native module, FlatList, FlashList, LegendList, Reanimated, Expo Router, mobile performance, app store. Do NOT use for Flutter, web-only React, or backend Node.js tasks.
89
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 an excellent skill description that covers all key dimensions thoroughly. It provides specific capabilities, comprehensive trigger terms, explicit 'Use when' and 'Do NOT use for' clauses, and clear domain boundaries. The only minor note is the use of 'Senior React Native and Expo engineer' which is slightly persona-like rather than purely action-oriented, but it doesn't use first or second person voice.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: building React Native components, implementing navigation with Expo Router, optimizing list and scroll performance, working with animations via Reanimated, handling platform-specific code, integrating native modules, and structuring Expo projects. | 3 / 3 |
Completeness | Clearly answers both 'what' (senior React Native/Expo engineer for building production-ready cross-platform mobile apps with specific capabilities listed) and 'when' (explicit 'Use when...' clause with detailed trigger scenarios, plus a 'Triggers on' list and a 'Do NOT use for' exclusion clause). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say, including 'React Native', 'Expo', 'mobile app', 'iOS app', 'Android app', 'cross-platform', 'FlatList', 'FlashList', 'Reanimated', 'Expo Router', 'mobile performance', 'app store'. These are terms users would naturally use when requesting mobile development help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche in React Native/Expo mobile development. The explicit exclusion of Flutter, web-only React, and backend Node.js tasks further reduces conflict risk with adjacent skills. | 3 / 3 |
Total | 12 / 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 strong, well-structured skill that provides highly actionable guidance for React Native/Expo development with excellent progressive disclosure through reference files. Its main weaknesses are some redundancy between the Critical Rules and MUST DO/MUST NOT DO sections, and a workflow that lacks explicit validation checkpoints between steps. The technology stack table and code examples are current and practical.
Suggestions
Remove or consolidate the MUST DO/MUST NOT DO section with the Critical Rules section to eliminate redundancy and save tokens
Add explicit validation/verification checkpoints to the workflow (e.g., 'Run TypeScript check after implementation', 'Verify Perf Monitor shows <16ms frames before proceeding')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive and mostly efficient, but includes some unnecessary explanatory text (e.g., 'Core Principles' section with general engineering advice Claude already knows like 'understand before implementing' and 'simplicity first'). The technology stack table with version numbers is useful but some entries like 'Latest' add little value. The MUST DO/MUST NOT DO section largely duplicates rules already stated in Critical Rules. | 2 / 3 |
Actionability | Excellent actionability throughout — provides executable code examples for lists (LegendList), navigation (NativeTabs), animations (useAnimatedStyle), images (expo-image), styling patterns, and crash-prevention patterns. The code is copy-paste ready with clear correct/incorrect comparisons. Specific library choices and API calls are named explicitly. | 3 / 3 |
Workflow Clarity | The workflow section (Setup → Structure → Implement → Optimize → Test) provides a clear sequence but lacks explicit validation checkpoints or feedback loops. Testing is mentioned but there's no 'validate then fix' cycle. For a skill involving complex multi-step mobile development with potential crashes and platform-specific issues, the absence of verification steps between stages caps this at 2. | 2 / 3 |
Progressive Disclosure | Excellent progressive disclosure with a clear reference table mapping topics to specific files with explicit 'Load When' triggers. The main skill contains critical rules inline (appropriate since they 'always apply') while deferring detailed catalogs (35+ performance rules, router patterns, project structure) to reference files. Navigation is one level deep and clearly signaled. | 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.
- Repository
- tech-leads-club/agent-skills
- Commit
81e7e0d
- 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.