Complete guide for building beautiful apps with Expo Router. Covers fundamentals, styling, components, navigation, animations, patterns, and native tabs.
61
Quality
52%
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 ./config/claude/skills/building-native-ui/SKILL.mdQuality
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies its domain (Expo Router) and lists relevant topic areas, but reads more like a table of contents than actionable guidance. It lacks explicit trigger conditions telling Claude when to use this skill, and the capabilities are described as categories rather than concrete actions Claude can perform.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about Expo Router, React Native navigation, mobile app routing, or building apps with file-based routing'
Convert category listings to concrete actions: instead of 'Covers navigation', say 'Implement file-based routing, configure tab navigation, set up stack navigators'
Include common user terms and variations: 'React Native', 'mobile app development', 'screen navigation', 'tab bar', 'routing'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Expo Router apps) and lists several topic areas (styling, components, navigation, animations, patterns, native tabs), but these are categories rather than concrete actions. Missing specific verbs like 'create', 'implement', 'configure'. | 2 / 3 |
Completeness | Describes what the skill covers (Expo Router topics) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'Expo Router', 'navigation', 'animations', 'native tabs', but missing common variations users might say like 'React Native', 'mobile app', 'routing', 'screen transitions', or file extensions. | 2 / 3 |
Distinctiveness Conflict Risk | 'Expo Router' is fairly specific and distinguishes from general React or React Native skills, but 'building beautiful apps', 'styling', 'components', and 'animations' are generic enough to potentially overlap with other mobile/web development skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
72%Reviews 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 skill with excellent progressive disclosure through clear references to detailed topic files. The actionability is strong with executable code examples for navigation patterns, styling, and route configuration. Minor improvements could be made by trimming some explanatory content that Claude already knows and adding validation checkpoints for route setup workflows.
Suggestions
Trim the 'When Expo Go Works' section - Claude knows what Expo Go supports; focus only on the decision criteria
Add a validation step after route structure changes (e.g., 'Verify route loads: npx expo start and navigate to the new route')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with good code examples, but includes some unnecessary explanations (e.g., explaining when Expo Go works vs custom builds is somewhat verbose, and some rules like 'never use special characters in file names' are obvious to Claude). | 2 / 3 |
Actionability | Provides concrete, executable code examples throughout - Link components, Stack configurations, context menus, sheet presentations, and complete route structure examples are all copy-paste ready. | 3 / 3 |
Workflow Clarity | The 'Running the App' section has a clear decision flow, but lacks explicit validation checkpoints. The route structure section shows organization but doesn't include verification steps for ensuring routes work correctly. | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear overview and well-signaled one-level-deep references to 11 separate reference files covering specific topics (tabs, icons, animations, etc.). Navigation is easy and content is appropriately split. | 3 / 3 |
Total | 10 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
355d067
Table of Contents
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.