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 main 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, production-quality code examples covering a broad range of React Native/Expo patterns, which is its primary strength. However, it is excessively verbose for a skill file — it reads more like a comprehensive tutorial than a concise reference, explaining many patterns Claude already knows. The lack of progressive disclosure (everything inline, no external file references) and missing validation/error-recovery steps in workflows are significant weaknesses.
Suggestions
Split the detailed patterns (auth flow, offline-first, native modules, performance, EAS build) into separate referenced files and keep SKILL.md as a concise overview with quick-start and navigation links.
Remove or drastically condense sections covering well-known patterns (e.g., React Query optimistic updates, basic auth context) — focus only on React Native/Expo-specific gotchas Claude wouldn't already know.
Add validation checkpoints to the EAS Build workflow (e.g., verify build status, check for common errors, test OTA update before promoting to production).
Remove the 'When to Use This Skill' and comparison table sections — these explain concepts Claude already understands and waste token budget.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~500+ lines, with extensive code examples that cover well-known patterns Claude already understands (React Query setup, auth context patterns, basic Expo Router usage). The comparison table, 'When to Use This Skill' section, and Do's/Don'ts lists explain concepts Claude already knows. Much of this could be condensed to key patterns and references. | 1 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code examples throughout — from project setup commands to complete component implementations, EAS build configuration, and specific library usage patterns. Every pattern includes concrete, runnable TypeScript code. | 3 / 3 |
Workflow Clarity | The EAS Build section has a clear sequence of commands, and the Quick Start provides ordered setup steps. However, there are no validation checkpoints — no steps to verify the build succeeded, no error recovery guidance for failed builds or OTA updates, and no feedback loops for the development workflow. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with all content inline. There are no references to external files for detailed patterns. The auth flow, offline-first setup, native modules, and performance optimization patterns could each be separate referenced documents, keeping the SKILL.md as a concise overview. | 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
91fe43e
- 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.