react-native-expert
Builds, optimizes, and debugs cross-platform mobile applications with React Native and Expo. Implements navigation hierarchies (tabs, stacks, drawers), configures native modules, optimizes FlatList rendering with memo and useCallback, and handles platform-specific code for iOS and Android. Use when building a React Native or Expo mobile app, setting up navigation, integrating native modules, improving scroll performance, handling SafeArea or keyboard input, or configuring Expo SDK projects.
72
88%
Does it follow best practices?
Impact
—
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 hits all the marks. It provides specific concrete actions, comprehensive trigger terms that developers would naturally use, explicit 'Use when' guidance, and a clearly defined niche in React Native/Expo development. It uses proper third-person voice throughout and avoids vague language or buzzwords.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: builds/optimizes/debugs apps, implements navigation hierarchies (with specific types), configures native modules, optimizes FlatList rendering with memo and useCallback, handles platform-specific code for iOS and Android. | 3 / 3 |
Completeness | Clearly answers both 'what' (builds, optimizes, debugs React Native/Expo apps with specific capabilities) and 'when' with an explicit 'Use when...' clause listing multiple trigger scenarios like building an app, setting up navigation, integrating native modules, improving scroll performance, etc. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'React Native', 'Expo', 'navigation', 'tabs', 'stacks', 'drawers', 'FlatList', 'iOS', 'Android', 'SafeArea', 'keyboard input', 'Expo SDK', 'native modules', 'scroll performance'. These are all terms a developer would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche in React Native and Expo mobile development. The specific mention of React Native-specific concepts (FlatList, SafeArea, Expo SDK, native modules) makes it very unlikely to conflict with general web development or other mobile framework skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%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 React Native skill with strong actionability through executable code examples and clear workflow with validation checkpoints and error recovery paths. The main weaknesses are moderate verbosity (the three full code examples inline make the file long) and incomplete progressive disclosure since the referenced bundle files don't exist. The constraint lists and error recovery section add genuine value.
Suggestions
Move the full code examples into a referenced file (e.g., references/code-examples.md) and keep only a minimal snippet inline to improve conciseness and progressive disclosure.
Provide the five referenced files (expo-router.md, platform-handling.md, etc.) in the bundle to fulfill the progressive disclosure promise of the reference table.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but has some unnecessary framing ('Senior mobile engineer building production-ready cross-platform applications') and the code examples, while useful, are lengthy. The MUST DO/MUST NOT DO lists contain some items Claude would already know (e.g., 'Ignore memory leaks from subscriptions'). The Knowledge Reference line at the end is a bare list that earns its place, but the output format section restates what's already implied by the examples. | 2 / 3 |
Actionability | Provides fully executable, copy-paste-ready TypeScript code examples for three common patterns (FlatList optimization, KeyboardAvoidingView, Platform-specific styling). Concrete commands are given for setup (`npx expo doctor`), error recovery (`npx expo start --clear`), and builds. The constraints are specific and actionable. | 3 / 3 |
Workflow Clarity | The core workflow has a clear 5-step sequence with explicit validation checkpoints (run `npx expo doctor`, verify on simulators, profile with Flipper). The error recovery section provides specific feedback loops for Metro, iOS, and Android build failures with concrete resolution steps. This covers destructive/complex operations well. | 3 / 3 |
Progressive Disclosure | The reference table with 'Load When' guidance is well-structured and clearly signaled, but no bundle files are provided, meaning all five referenced files (expo-router.md, platform-handling.md, etc.) are missing. The inline code examples are substantial and could arguably be moved to reference files, making the SKILL.md leaner. The structure is good in concept but incomplete in practice. | 2 / 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
- jeffallan/claude-skills
- Commit
e8be415
- 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.