jbvc/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.
69
69%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a stub that delegates all substantive content to an external playbook while providing no actionable guidance, concrete examples, or meaningful workflow in the main file. The instructions are generic boilerplate that could apply to any skill and contain no React Native-specific knowledge. It fails to serve as a useful overview or quick reference for any of its stated use cases.
Suggestions
Add at least one concrete, executable code example in the main skill file (e.g., Expo project initialization command, a navigation setup snippet, or an offline sync pattern).
Replace the generic instruction bullets with specific, actionable steps for common tasks like setting up an Expo project or configuring navigation.
Provide a brief summary of what's in the implementation playbook so Claude knows when and why to reference it (e.g., 'Playbook covers: Expo Router setup, native module bridging, offline SQLite sync patterns').
Add at least one multi-step workflow with validation checkpoints for a common operation like building and deploying a production app.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively short but includes generic filler instructions ('Clarify goals, constraints, and required inputs', 'Apply relevant best practices') that add no value. The 'Do not use' section is also boilerplate. However, it's not excessively verbose. | 2 / 3 |
Actionability | There is no concrete code, no specific commands, no executable examples, and no actual technical guidance. The instructions are entirely abstract ('Apply relevant best practices and validate outcomes') and delegate everything to an external resource file. | 1 / 3 |
Workflow Clarity | There is no clear workflow, no sequenced steps, and no validation checkpoints. The four bullet points under Instructions are generic platitudes rather than an actionable process for any of the listed use cases. | 1 / 3 |
Progressive Disclosure | There is a reference to an external resource file (resources/implementation-playbook.md), which is appropriate progressive disclosure. However, the SKILL.md itself provides essentially zero useful overview content—it's an empty shell pointing elsewhere, making the reference less useful without any inline quick-start material. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents