react-native-expert
Use when building cross-platform mobile applications with React Native or Expo. Invoke for navigation patterns, platform-specific code, native modules, FlatList optimization.
Install with Tessl CLI
npx tessl i github:jeffallan/claude-skills --skill react-native-expertOverall
score
81%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 with excellent trigger terms and clear when-to-use guidance. The main weakness is that it lists topic areas rather than concrete actions - it tells you what domains it covers but not what specific tasks it can perform (e.g., 'configure navigation stacks', 'write platform-specific components').
Suggestions
Replace topic categories with concrete action phrases: instead of 'navigation patterns', use 'configure React Navigation stacks, implement deep linking'
Add more specific actions for each area mentioned: 'optimize FlatList rendering performance, implement native module bridges, handle platform-specific styling'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (React Native/Expo mobile apps) and mentions some specific areas (navigation patterns, platform-specific code, native modules, FlatList optimization), but these are more like topic categories than concrete actions. Missing action verbs like 'build', 'configure', 'optimize'. | 2 / 3 |
Completeness | Explicitly answers both what (building cross-platform mobile apps, navigation, platform-specific code, native modules, FlatList optimization) and when ('Use when building cross-platform mobile applications', 'Invoke for...'). Has clear trigger guidance. | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'React Native', 'Expo', 'mobile applications', 'navigation', 'native modules', 'FlatList'. These are terms developers naturally use when working in this space. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche targeting React Native/Expo specifically. The combination of 'React Native', 'Expo', 'native modules', and 'FlatList' creates a distinct fingerprint unlikely to conflict with general JavaScript or web development skills. | 3 / 3 |
Total | 11 / 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 skill is well-organized with excellent progressive disclosure and token efficiency. The constraints are specific and valuable for mobile development. However, it lacks executable code examples that would make the guidance immediately actionable, and the workflow could benefit from explicit validation checkpoints for platform testing.
Suggestions
Add executable code examples for key patterns like FlatList optimization with memo/useCallback, showing the correct implementation vs. anti-patterns
Include a concrete KeyboardAvoidingView example with platform-specific behavior prop
Add validation checkpoints to the workflow, such as 'Test on iOS simulator -> Fix issues -> Test on Android emulator -> Test on real devices'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of basic concepts Claude already knows. Every section serves a purpose with no padding or unnecessary context about what React Native is. | 3 / 3 |
Actionability | Provides clear constraints and guidelines but lacks executable code examples. The MUST DO/MUST NOT DO sections are specific but would benefit from concrete code snippets showing correct implementations. | 2 / 3 |
Workflow Clarity | The 5-step core workflow is listed but lacks validation checkpoints and feedback loops. For mobile development involving platform-specific testing and optimization, explicit verification steps would strengthen this. | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear reference table pointing to topic-specific files one level deep. The 'Load When' column provides clear navigation signals for when to access each reference. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
Total | 12 / 16 Passed | |
- 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.