react-native-architecture

Build production React Native apps with Expo, navigation, native modules, offline sync, and cross-platform patterns. Use when developing mobile apps, implementing native integrations, or architecting React Native projects.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/frontend-mobile-development/skills/react-native-architecture/SKILL.md

The canonical home for this skill is react-native-architecture in wshobson/agents

Quality

Content

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

The content is highly actionable with complete, executable code for every pattern, but it is token-heavy because large code blocks and configuration live entirely in the body with no progressive disclosure to reference files, and it lacks an ordered build/deploy workflow with validation checkpoints.

Suggestions

Move the largest code patterns (auth flow, offline React Query, native modules) and eas.json into separate reference files under references/ and link to them from SKILL.md so the main file is a lean overview.

Add a numbered end-to-end workflow for shipping (scaffold -> configure env/secure store -> build with EAS -> verify on device -> submit) with explicit validation checkpoints before destructive or store-facing steps.

Trim boilerplate comments and self-evident code (Stack.Screen declarations, StyleSheet entries) that Claude can already produce, keeping only the non-obvious Expo-specific idioms.

Dimension	Reasoning	Score
Conciseness	The body inlines ~600 lines of full code across six patterns plus an eas.json and a comparison table, much of it boilerplate Claude already knows (Stack layouts, StyleSheet.create, FlashList props); it is noticeably verbose with several padded sections rather than lean overview material.	2 / 5
Actionability	Every pattern is backed by complete, copy-paste-ready TypeScript that covers the common cases (auth guard, offline React Query, haptics, biometrics, push notifications, animated Button), matching the fully executable 5 anchor.	5 / 5
Workflow Clarity	Patterns are presented as isolated code blocks with section headings but no sequenced multi-step build flow and no validation checkpoints for risky operations like EAS builds, store submission, or secure token handling, leaving checkpoints implicit.	3 / 5
Progressive Disclosure	There is reasonable section structure, but no references/ scripts/ or assets/ bundle exists, so everything (large code patterns, eas.json, best practices) is inlined in SKILL.md rather than split into one-level-deep reference files that would aid navigation.	3 / 5
	Total	13 / 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-formed description that clearly states capabilities and provides explicit, natural trigger guidance, cleanly answering both what and when. Minor gains are possible by converting capability categories into discrete action verbs and adding a few common synonyms.

Dimension	Reasoning	Score
Specificity	The description names the domain plus several concrete capability areas ('navigation, native modules, offline sync, and cross-platform patterns'), but these read as category labels rather than discrete enumerated actions, so it stops short of the comprehensive multi-action listing of a 5.	4 / 5
Completeness	It explicitly answers both halves: the 'what' ('Build production React Native apps with Expo...') and the 'when' via a concrete 'Use when...' clause listing multiple trigger scenarios, matching the 5 anchor's explicit two-part structure.	5 / 5
Trigger Term Quality	It surfaces natural phrases users actually say ('developing mobile apps', 'implementing native integrations', 'architecting React Native projects') with good coverage, though it omits synonyms like 'RN', 'Expo app', or extension/SDK language that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	The React Native / Expo niche is specific and the triggers ('architecting React Native projects', 'native integrations') are distinct from generic web or backend skills, giving minimal conflict risk as in the 5 anchor.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (674 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: Dicklesworthstone/pi_agent_rust
Path: tests/ext_conformance/artifacts/agents-wshobson/frontend-mobile-development/skills/react-native-architecture/SKILL.md
Commit: 6453c0b

Reviewed: about 9 hours ago

Table of Contents

Discovery Implementation Validation

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.