CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

76

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong, well-disciplined SKILL.md body: executable code and commands, a validated workflow with error-recovery loops, and clean progressive disclosure to real reference files. The only meaningful deduction is the unpinned-to-context version list in 'Knowledge Reference', which is time-sensitive and slightly redundant with the Constraints checklist.

Suggestions

Move the version list ('React Native 0.73+, Expo SDK 50+, React Navigation 7, Reanimated 3') into a dedicated compatibility note or the relevant reference files, so stale version numbers don't penalize the evergreen main file.

Trim the MUST DO items that the code examples already demonstrate (e.g. 'Implement memo + useCallback for list items') to just the checklist items that add new information.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no concept explanations, terse workflow steps, well-chosen code. However, the 'Knowledge Reference' section pins time-sensitive version numbers ('React Native 0.73+, Expo SDK 50+, Expo Router, React Navigation 7, Reanimated 3') outside any deprecated/old-patterns section, and the Constraints checklist partially restates what the code examples demonstrate. Not 5 because of these minor trim opportunities; not 3 because there is no real padding or over-explanation.

4 / 5

Actionability

Fully executable throughout: exact commands ('npx expo doctor', 'npx expo start --clear', 'npx expo run:ios', 'adb logcat', 'npx expo install <module>') and three complete, copy-paste-ready TypeScript examples covering the most common cases (optimized FlatList, KeyboardAvoidingView form, Platform.select styling). Matches anchor 5 — specific examples cover the common cases.

5 / 5

Workflow Clarity

The 5-step Core Workflow is clearly sequenced with explicit validation checkpoints in every risky step ('run npx expo doctor to verify environment... fix any reported issues before proceeding', 'verify on iOS simulator and Android emulator; check Metro bundler output for errors before moving on'), and the Error Recovery section provides concrete error→fix→rebuild feedback loops. Matches anchor 5.

5 / 5

Progressive Disclosure

The Reference Guide table (Topic / Reference / Load When) gives clear, one-level-deep navigation to five reference files, all of which exist in ./references/ (expo-router.md, platform-handling.md, list-optimization.md, storage-hooks.md, project-structure.md). The main file stays an overview with key examples while detail is appropriately split out — matches anchor 5.

5 / 5

Total

19

/

20

Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An excellent description: third-person voice, dense with concrete capabilities, and an explicit 'Use when...' clause covering the natural trigger scenarios. The only weakness is slight overlap risk between generic trailing triggers ('setting up navigation', 'improving scroll performance') and closely related web-React skills.

Suggestions

Qualify the generic tail triggers with the mobile context, e.g. 'setting up mobile navigation (tabs, stacks, drawers)' or 'improving FlatList scroll performance', so they cannot fire for web React work.

Add file-extension or project markers users naturally mention (e.g. 'app.json', 'expo.config', '.tsx RN components') to sharpen distinctiveness against a sibling react-expert skill.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions with comprehensive coverage: '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.' It exceeds anchor 4 because there are no notable gaps in capability coverage.

5 / 5

Completeness

Explicitly answers both what ('Builds, optimizes, and debugs cross-platform mobile applications... Implements navigation hierarchies...') and when ('Use when building a React Native or Expo mobile app, setting up navigation, integrating native modules, improving scroll performance...'), matching the anchor-5 example structure exactly.

5 / 5

Trigger Term Quality

Covers the natural terms a user would actually say — 'React Native', 'Expo', 'mobile app', 'navigation', 'native modules', 'scroll performance', 'SafeArea', 'keyboard input', 'iOS', 'Android', 'Expo SDK' — including specific API names like FlatList that serve as synonyms. Not anchor 4 because no common natural phrasing is missing.

5 / 5

Distinctiveness Conflict Risk

Clear niche (React Native/Expo mobile development) with mostly distinct triggers, but tail triggers like 'setting up navigation' and 'improving scroll performance' could overlap with a sibling react-expert or web React skill without the RN context. Not 5 due to this minor overlap risk with closely related skills; not 3 because the core domain and triggers are unambiguous.

4 / 5

Total

19

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Jeffallan/claude-skills

Path

skills/react-native-expert/SKILL.md

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.