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.
76
71%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./tests/ext_conformance/artifacts/agents-wshobson/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 provides explicit trigger guidance via a 'Use when...' clause. It uses proper third-person voice and includes natural keywords that developers would use when seeking mobile development help.
| 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 | The combination of 'React Native', 'Expo', 'native modules', and 'mobile apps' creates a clear niche that is unlikely to conflict with web development, backend, or other frontend skills. The triggers are specific to mobile app development with a particular technology stack. | 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 high-quality, executable React Native/Expo code patterns but suffers significantly from verbosity and lack of progressive disclosure. It dumps ~500 lines of code that Claude largely knows how to produce, rather than focusing on project-specific conventions, gotchas, and non-obvious patterns. The content would benefit greatly from being split into a concise overview with references to detailed pattern files.
Suggestions
Reduce the main file to a concise overview (~50-80 lines) with project structure, quick start, and key decisions, then split each pattern (auth, offline, native modules, etc.) into separate referenced files like PATTERNS_AUTH.md, PATTERNS_OFFLINE.md
Remove content Claude already knows: the Expo vs Bare RN comparison table, generic Do's/Don'ts (don't inline styles, don't fetch in render), and the 'When to Use This Skill' section
Add a sequenced workflow for project setup with validation checkpoints, e.g., 'After creating the project, verify it runs with npx expo start before adding dependencies'
Focus content on non-obvious gotchas and project-specific conventions rather than complete boilerplate implementations that Claude can generate from library documentation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~500+ lines. It includes extensive boilerplate code that Claude already knows how to write (auth providers, button components, list rendering patterns). The comparison table of Expo vs Bare RN, the 'When to Use This Skill' section, and the Do's/Don'ts list all explain concepts Claude already understands. Much of this could be condensed to key patterns and gotchas only. | 1 / 3 |
Actionability | The code examples are fully executable, copy-paste ready TypeScript with proper imports, complete component implementations, and real library usage. The bash commands for project setup and EAS builds are concrete and specific. | 3 / 3 |
Workflow Clarity | While individual patterns are well-presented, there's no clear sequenced workflow for setting up a project end-to-end. The EAS Build section lists commands but lacks validation steps (e.g., verifying builds succeeded, testing before submitting to stores). The 'When to Use This Skill' section lists triggers but doesn't guide through a decision process. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of content with no references to external files. All six patterns, build configuration, best practices, and resources are inlined in a single massive document. Content like the full auth provider, offline-first setup, and native module integrations should be split into separate referenced files. | 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 (674 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- Dicklesworthstone/pi_agent_rust
- Commit
6e3d68c
- 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.