building-native-ui

Complete guide for building beautiful apps with Expo Router. Covers fundamentals, styling, components, navigation, animations, patterns, and native tabs.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/expo/skills/building-native-ui/SKILL.md

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a lean, highly actionable reference with complete executable code and a clean one-level-deep progressive disclosure structure backed by real reference files. Its main weaknesses are repeated safe-area guidance and a Running-the-App workflow that lacks explicit validation checkpoints.

Suggestions

Consolidate the repeated contentInsetAdjustmentBehavior / safe-area guidance into a single section to remove redundancy and tighten token use.

Add an explicit validation checkpoint to the 'Running the App' workflow, e.g. 'Verify the feature works in Expo Go before deciding a custom build is required'.

Trim explanatory prose in the 'Running the App' section (e.g. the sentence on custom-build complexity) down to directive bullets.

Dimension	Reasoning	Score
Conciseness	Mostly terse imperative bullets that assume Claude's competence ('expo-audio not expo-av', 'process.env.EXPO_OS not Platform.OS'), but it repeats safe-area/contentInsetAdjustmentBehavior guidance across sections and includes some explanatory prose in the 'Running the App' section, so it could be tightened.	2 / 3
Actionability	Provides complete, import-included executable code examples (Link, Stack.Screen, NativeTabs layouts, form sheets, context menus) plus concrete library and style directives, matching 'fully executable code/commands; copy-paste ready'.	3 / 3
Workflow Clarity	The 'Running the App' steps are clearly sequenced (start with Expo Go, check features, custom build only when required), but there is no explicit validation or feedback checkpoint, fitting 'sequence present but checkpoints missing or implicit'.	2 / 3
Progressive Disclosure	A well-signaled References section lists all 14 real one-level-deep reference files with one-line descriptions, and the body appropriately delegates detail to them (verified references/route-structure.md exists), matching 'clear overview with well-signaled one-level-deep references'.	3 / 3
	Total	10 / 12 Passed

Description

50%

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 clearly identifies the Expo Router domain and enumerates coverage areas, but leans on topic categories and vague qualifiers instead of concrete actions and entirely omits a 'Use when...' trigger clause. This caps completeness and trigger-term quality at the midpoint across all dimensions.

Suggestions

Add an explicit 'Use when...' trigger clause naming natural user phrases, e.g. 'Use when building Expo Router apps, adding native navigation, animations, or iOS-style UI'.

Replace the topic-category listing ('Covers fundamentals, styling...') with concrete actions such as 'Configure native tabs, build Stack navigation, add Reanimated animations, apply liquid-glass effects'.

Drop vague qualifiers like 'beautiful' and 'complete' and add common variations ('React Native', 'mobile app') to widen trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists covered domains ('styling, components, navigation, animations, patterns, and native tabs') but uses topic categories and vague adjectives like 'beautiful' and 'Complete guide' rather than concrete actions, matching the 'names domain and some actions, but not comprehensive' anchor.	2 / 3
Completeness	Clearly states what the skill covers but provides no explicit 'when should Claude use it' trigger guidance; per the judging guidelines, a missing 'Use when...' clause caps completeness at 2.	2 / 3
Trigger Term Quality	Includes relevant natural terms ('Expo Router', 'native tabs', 'navigation', 'animations') but lacks a 'Use when...' clause and common variations such as 'React Native' or 'mobile app', fitting 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	'Expo Router' names a distinct niche, but the vague framing ('beautiful apps') and absence of explicit triggers mean it could still overlap with general React Native or UI styling skills.	2 / 3
	Total	8 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: openai/plugins
Path: plugins/expo/skills/building-native-ui/SKILL.md
Commit: 11c74d6

Reviewed: about 10 hours ago

Table of Contents

Discovery Implementation Validation

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.