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.
79
71%
Does it follow best practices?
Impact
91%
1.13xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/frontend-mobile-development/skills/react-native-architecture/SKILL.mdQuality
Discovery
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 a strong skill description that clearly communicates its scope (React Native/Expo mobile development), lists specific capabilities (navigation, native modules, offline sync, cross-platform patterns), and includes an explicit 'Use when...' clause with natural trigger terms. It is concise, uses third-person voice, and is distinctive enough to avoid conflicts with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete capabilities: 'Build production React Native apps with Expo, navigation, native modules, offline sync, and cross-platform patterns.' These are distinct, concrete technical areas rather than vague abstractions. | 3 / 3 |
Completeness | Clearly answers both 'what' (build production React Native apps with Expo, navigation, native modules, offline sync, cross-platform patterns) and 'when' (Use when developing mobile apps, implementing native integrations, or architecting React Native projects) with an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'React Native', 'Expo', 'mobile apps', 'native integrations', 'navigation', 'offline sync', 'cross-platform'. These cover the primary terms a developer would use when seeking help with mobile development in this stack. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to React Native/Expo mobile development, which is a distinct niche. The combination of 'React Native', 'Expo', 'native modules', and 'mobile apps' makes it unlikely to conflict with web development, backend, or other frontend skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides highly actionable, executable code examples covering a broad range of React Native/Expo patterns, which is its primary strength. However, it is excessively verbose — dumping hundreds of lines of well-known patterns into a single monolithic file without progressive disclosure or clear workflow sequencing. The content would be far more effective if condensed to key decisions and gotchas, with detailed patterns split into referenced files.
Suggestions
Split the six detailed patterns into separate referenced files (e.g., patterns/navigation.md, patterns/offline.md, patterns/auth.md) and keep SKILL.md as a concise overview with links to each.
Remove or drastically condense code that represents standard/well-known patterns (e.g., the full Button component with styles, the haptics wrapper) — focus on project-specific decisions and non-obvious gotchas.
Add explicit workflow steps with validation checkpoints for common multi-step processes like 'setting up a new project' or 'preparing a production release' (e.g., verify build succeeds before submitting to stores).
Remove the 'When to Use This Skill' and 'Core Concepts' comparison table sections — these explain things Claude already knows and waste token budget.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~400+ lines, with extensive code examples that cover well-known patterns (React Query setup, auth context, haptics wrappers, button components with styles). The Expo vs Bare RN comparison table, 'When to Use This Skill' section, and Do's/Don'ts lists explain things Claude already knows. Much of this could be condensed to key patterns and gotchas only. | 1 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code examples throughout — from project setup commands to complete TypeScript implementations of auth flows, offline-first patterns, navigation, native modules, and EAS build configuration. Every pattern includes concrete, runnable code. | 3 / 3 |
Workflow Clarity | The patterns are presented as isolated code blocks rather than a sequenced workflow. The EAS Build section has clear commands but lacks validation checkpoints (e.g., verifying build success before submitting, testing OTA updates). There's no explicit workflow for setting up a new project end-to-end with verification steps between stages. | 2 / 3 |
Progressive Disclosure | The entire skill is a monolithic wall of code with no references to external files. All six patterns, build configuration, and best practices are inlined in a single massive document. This content would benefit enormously from splitting patterns into separate referenced files (e.g., NAVIGATION.md, OFFLINE.md, AUTH.md) with a concise overview in the main skill. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (667 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- wshobson/agents
- Commit
34632bc
- 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.