CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

82%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

64%

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, highly actionable React Native/Expo skill with excellent concrete code examples and clear anti-patterns. Its main weaknesses are moderate verbosity (duplicated guidance between Critical Rules and Constraints sections, some obvious advice in Core Principles) and a workflow that lacks explicit validation checkpoints. The progressive disclosure structure is well-designed in concept but the main file is heavy with inline content.

Suggestions

Consolidate the 'Constraints' MUST DO/MUST NOT DO section with the 'Critical Rules' section to eliminate duplication — most items appear in both.

Trim the 'Core Principles' section to remove generic advice Claude already follows (e.g., 'understand before implementing', 'surgical changes') and keep only React Native-specific principles.

Add explicit validation checkpoints to the workflow — e.g., 'Run `npx expo start` and verify no TypeScript errors', 'Check Perf Monitor shows <16ms frame times', with recovery steps if checks fail.

DimensionReasoningScore

Conciseness

The skill is fairly comprehensive but includes some unnecessary explanation (e.g., 'Core Principles' section with general advice like 'understand before implementing' that Claude already knows). The technology stack table with version numbers is useful but the 'Key architectural facts' section mixes genuinely novel info (shared value .get()/.set()) with things Claude likely knows. The MUST DO/MUST NOT DO section largely duplicates the Critical Rules section. Could be tightened by ~30%.

2 / 3

Actionability

Excellent actionability throughout — provides executable code examples for every major pattern (LegendList usage, NativeTabs, Reanimated animated styles, expo-image, styling patterns). Includes concrete anti-patterns with CRASH/SAFE labels. The code is copy-paste ready with proper imports and TypeScript.

3 / 3

Workflow Clarity

The workflow section (Setup → Structure → Implement → Optimize → Test) provides a clear sequence but lacks explicit validation checkpoints or feedback loops. The 'Test' step says 'test on both platforms' and 'check list scroll performance' but doesn't specify how to validate or what to do if issues are found. For a skill involving complex multi-step mobile development with potential crashes, the absence of verification steps (e.g., build verification, runtime error checking) is a gap.

2 / 3

Progressive Disclosure

The Reference Guide table is well-structured with clear 'Load When' triggers pointing to 5 reference files. However, no bundle files were provided, so we cannot verify these references exist. The main SKILL.md itself is quite long (~250+ lines) and inlines substantial content (Critical Rules, Constraints) that could potentially be split into reference files. The inline content is useful but the balance between overview and detail leans toward monolithic.

2 / 3

Total

9

/

12

Passed

Description

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 key criteria. It provides specific capabilities, comprehensive trigger terms covering natural user language, explicit 'Use when' and 'Do NOT use for' clauses, and clear distinctiveness from related but different skills. The only minor note is the use of 'Senior' which is slightly anthropomorphizing but doesn't materially harm the description's effectiveness.

DimensionReasoningScore

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' (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: '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 help with mobile development.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with clear niche in React Native/Expo mobile development. The explicit exclusions ('Do NOT use for Flutter, web-only React, or backend Node.js tasks') further reduce conflict risk with adjacent skills.

3 / 3

Total

12

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
tech-leads-club/agent-skills
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.