CtrlK
BlogDocsLog inGet started
Tessl Logo

react-native

React Native patterns for mobile app development with Expo and bare workflow. Trigger: When building mobile apps, working with React Native components, using Expo, React Navigation, or NativeWind.

64

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./community/react-native/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 highly actionable patterns catalog with copy-paste-ready code for the common React Native cases. Its weaknesses are token efficiency (padded explanatory comments) and a lack of progressive disclosure, with everything inlined rather than split into referenced files.

Suggestions

Trim obvious-knowledge comments in the Anti-Patterns section (e.g. why inline styles or TouchableOpacity are bad) and keep only the corrective pattern.

Move the longer code examples (e.g. Expo Router layout, Zustand store) into a references/ file and link to them from a concise overview, improving progressive disclosure and token budget.

Add a short 'validate/build' checkpoint note (e.g. run `npx expo start` to verify) so the patterns imply a feedback loop rather than only presenting static snippets.

DimensionReasoningScore

Conciseness

Mostly efficient with valuable code, but includes over-explanatory comments Claude does not need ('inline styles are hard to maintain and don't memoize', 'TouchableOpacity is legacy'); some sections could be tightened.

3 / 5

Actionability

Fully executable, copy-paste-ready code across navigation, hooks, styling, safe-area, and state management, plus concrete commands in the Quick Reference table covering common cases.

5 / 5

Workflow Clarity

This is a patterns/catalog rather than a multi-step workflow; sections are organized but there is no sequenced process with validation checkpoints, and no feedback loops are demonstrated.

3 / 5

Progressive Disclosure

Clear section headers provide structure, but all 362 lines live inline in SKILL.md with no one-level-deep references to separate files; substantial code examples could be externalized.

3 / 5

Total

14

/

20

Passed

Description

87%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.

A strong, well-scoped description that states concrete capabilities and provides an explicit trigger clause covering the main React Native tooling. It is clearly distinguishable from generic web React skills and answers both what and when.

DimensionReasoningScore

Specificity

Names the domain ('React Native patterns for mobile app development') and lists several concrete capabilities (Expo, bare workflow, React Navigation, NativeWind, native modules/linking, platform-specific code), with only minor gaps in coverage.

4 / 5

Completeness

Explicitly answers both what ('React Native patterns for mobile app development with Expo and bare workflow') and when via a dedicated 'Trigger:' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural terms users would say ('building mobile apps', 'React Native', 'Expo', 'React Navigation', 'NativeWind'); good coverage though a few synonyms (e.g. 'RN') are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear React Native mobile niche with Expo/NativeWind/React Navigation triggers that are unlikely to fire for unrelated skills, giving minimal conflict risk.

5 / 5

Total

18

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Gentleman-Programming/Gentleman-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.