Content
68%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, practical skill that provides clear guidelines for building Expo Router apps. Its strengths are concrete code examples for navigation patterns, clear library preferences, and a well-organized reference system. Weaknesses include some verbosity in the Expo Go section, lack of explicit validation/verification workflows, and a few areas where rules are stated without accompanying code examples.
Suggestions
Trim the 'Running the App' / 'When Expo Go Works' section—Claude knows what Expo Go supports; a shorter decision rule ('Use Expo Go unless you need custom native modules, Apple targets, or third-party native code') would suffice.
Add a brief validation step or checklist for common operations like restructuring routes (e.g., 'After moving routes, verify no broken imports and test navigation paths').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient and assumes Claude's competence with React Native/Expo. The 'When Expo Go Works' section is slightly verbose listing things Claude would know, and the 'Running the App' section over-explains Expo Go vs custom builds. Most other sections are lean and directive. | 4 / 5 |
Actionability | Provides concrete, executable code examples for navigation, context menus, link previews, sheets, modals, and route structure. The code is copy-paste ready. Minor gaps exist—some sections like 'Library Preferences' are directive rules without code examples, and some references are delegated to external files without inline snippets. | 4 / 5 |
Workflow Clarity | The 'Running the App' section has a clear decision tree for Expo Go vs custom builds. However, there's no overall workflow for building an app from scratch, no validation/verification steps after creating routes or navigation structures, and the content reads more as a collection of rules than a sequenced process. For a guidelines-style skill this is acceptable but lacks checkpoints. | 3 / 5 |
Progressive Disclosure | The references section at the top clearly lists 14 separate reference files with one-line descriptions, providing good one-level-deep navigation. The main SKILL.md serves as an overview with appropriate inline content. However, since no bundle files were provided, we can't verify the referenced files exist. Some sections (like the full route structure example) could arguably be in a reference file but are reasonably sized inline. | 4 / 5 |
Total | 15 / 20 Passed |