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.
92
92%
Does it follow best practices?
Impact
90%
1.26xAverage score across 6 eval scenarios
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 mobile development. The description is well-structured, uses third person voice throughout, and balances detail with conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: builds/optimizes/debugs cross-platform mobile apps, implements navigation hierarchies (tabs, stacks, drawers), 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 a React Native 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', 'native modules', 'FlatList', 'scroll performance', 'SafeArea', 'keyboard input', 'Expo SDK', 'iOS', 'Android', 'mobile app'. These are all terms developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche in React Native and Expo mobile development. The specific technology stack (React Native, Expo, FlatList, SafeArea) and platform mentions (iOS, Android) make it very unlikely to conflict with general web development or other framework skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%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, clear workflow sequencing with validation checkpoints, and excellent progressive disclosure via the reference table. The main weakness is that the inline code examples are somewhat lengthy for patterns Claude likely already knows (KeyboardAvoidingView, Platform.select), which inflates the token cost without proportional value. The constraints and error recovery sections add genuine value.
Suggestions
Trim the KeyboardAvoidingView and Platform-specific examples to minimal snippets showing only the non-obvious patterns (e.g., the behavior prop selection and Platform.select shadow pattern), or move full examples to a reference file.
Remove obvious constraints like 'Ignore memory leaks from subscriptions' and 'Skip platform-specific testing' that Claude would already know to avoid.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some redundancy. The three code examples are quite lengthy and could be trimmed—the LoginForm and StatusChip examples demonstrate basic React Native patterns Claude already knows well. The constraints section has some obvious items (e.g., 'don't ignore memory leaks'). | 2 / 3 |
Actionability | Provides fully executable TypeScript code examples with proper imports, types, and StyleSheet definitions. Commands are specific (e.g., `npx expo start --clear`, `npx expo run:ios`), and the error recovery section gives concrete troubleshooting steps. | 3 / 3 |
Workflow Clarity | The core workflow has clear sequencing with explicit validation checkpoints (run `npx expo doctor`, check Metro output, profile with Flipper). The error recovery section provides concrete feedback loops for common failure modes (Metro errors, iOS/Android build failures, native module issues). | 3 / 3 |
Progressive Disclosure | Excellent use of a reference table with clear 'Load When' conditions for five separate topic files. The main skill serves as a concise overview with actionable content, deferring detailed guidance to one-level-deep reference files. | 3 / 3 |
Total | 11 / 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.
3d95bb1
Table of Contents
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.