CtrlK
BlogDocsLog inGet started
Tessl Logo

react-native-patterns

React Native and Expo app patterns — Expo Router navigation, state separation (server/client/route/form), TanStack Query data fetching with Zod, performant lists, NativeWind/StyleSheet styling, native APIs, and secure storage. Use when building or editing React Native / Expo screens, components, navigation, or data layers.

68

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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 complete, executable code and clear validation-aware examples, weakened mainly by a monolithic single-file structure with no progressive disclosure and a time-sensitive version claim that hurts conciseness. Workflow clarity is adequate for a catalog but lacks explicit feedback loops.

Suggestions

Split detailed code examples into reference files under references/ (e.g., navigation.md, data-fetching.md, native-apis.md) and keep SKILL.md as a lean overview with well-signaled one-level-deep links, to improve progressive_disclosure.

Move or soften the time-sensitive 'mandatory from SDK 55+' version claim — place version guidance in a clearly marked compatibility/notes section or drop the hard version number to improve conciseness.

Add an explicit validate→fix→retry feedback loop for at least one fragile operation (e.g., route-param or API-response validation with a recovery path) to raise workflow_clarity.

DimensionReasoningScore

Conciseness

The body is mostly lean and code-dense without explaining concepts Claude already knows, but it carries a time-sensitive version claim ('mandatory from SDK 55+') and runs ~320 lines fully inline, so it could be tightened. It is not level 3 because the version-bound statement and overall inline volume mean not every token earns its place.

2 / 3

Actionability

Provides fully executable, copy-paste-ready code throughout — useQuery/useMutation, FlatList, a complete useCurrentLocation hook, a full OrdersScreen, and a React Hook Form + Zod form. It is not level 2 because the examples are complete and runnable rather than pseudocode or missing key details.

3 / 3

Workflow Clarity

Pattern sequences show validation checkpoints (Zod at route/API boundaries, explicit loading/error/empty states), but there is no validate→fix→retry feedback loop and the skill is a patterns catalog rather than a sequenced fragile workflow. It is not level 3 because explicit error-recovery feedback loops and checklists for complex processes are absent.

2 / 3

Progressive Disclosure

Sections are well-organized (Core Concepts, Code Examples, Anti-Patterns, Best Practices) but the skill is a single ~320-line monolithic file with no bundle references, so detail that could be split out is inline. It is not level 1 because organization is clear with headers, not a wall of text, and not level 3 because there are no one-level-deep reference files to navigate to.

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.

A strong, third-person description that explicitly states concrete capabilities and an explicit 'Use when' trigger, with natural keywords and a clear mobile niche distinct from web React. No meaningful weaknesses; voice is imperative/third-person so no specificity penalty applies.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'Expo Router navigation, state separation (server/client/route/form), TanStack Query data fetching with Zod, performant lists, NativeWind/StyleSheet styling, native APIs, and secure storage' — matching the anchor for several specific concrete actions. It is not level 2 because the action list is comprehensive rather than naming only a domain and some actions.

3 / 3

Completeness

Explicitly answers both what ('React Native and Expo app patterns — ...') and when ('Use when building or editing React Native / Expo screens, components, navigation, or data layers'). It is not level 2 because the trigger clause is explicit, not merely implied.

3 / 3

Trigger Term Quality

Uses natural terms users would actually say — 'React Native', 'Expo', 'screens', 'components', 'navigation', 'data layers' — giving good coverage rather than just some relevant keywords. It is not level 2 because common phrasings a user would utter are well represented, not partially missing.

3 / 3

Distinctiveness Conflict Risk

Carves out a clear mobile RN/Expo niche distinct from web React, with triggers unlikely to fire for unrelated skills. It is not level 2 because the niche and triggers are specific enough to avoid meaningful overlap with sibling web skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
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.