expo-development

Scaffolds Expo/React Native apps, configures EAS Build profiles, manages native modules via CNG, sets up Expo Router navigation, and uses EAS Update for OTA deployments. Use when creating React Native apps with Expo, configuring EAS builds, setting up Expo Router, managing native modules, or deploying OTA updates.

Quality

88%

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

Quality

Content

83%Weight 40%Scale 1-5

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

A lean, highly actionable Expo reference with concrete commands and config throughout. Its main weakness is workflow clarity: destructive and batch operations (prebuild --clean, OTA rollback, signing) lack explicit validation checkpoints and error-recovery feedback loops.

Suggestions

Add a numbered prebuild workflow with a validation checkpoint, e.g. after `npx expo prebuild`, verify the build runs locally before committing, since `--clean` discards native state destructively.

Make the OTA rollback sequence explicit with a feedback loop: list prior groups with `eas update:list`, republish, then confirm the active branch with `eas update:configure` or a runtime check.

Add a brief 'verify the build' step for EAS Build (e.g. check `eas build:view <id>` status before promoting) to give the build/deploy flow an explicit checkpoint.

Dimension	Reasoning	Score
Conciseness	Dense bullet points packed with executable commands and concrete config values (e.g. 'runtimeVersion: { policy: "fingerprint" }', 'eas update:republish --group <previous-group-id>') with no padding or restating of concepts Claude already knows, matching the score-5 'lean and efficient' anchor.	5 / 5
Actionability	Provides copy-paste-ready commands and exact config snippets covering the common cases (prebuild, eas.json profiles, EAS Update, rollback, secrets, Router conventions), matching the score-5 anchor for fully executable guidance.	5 / 5
Workflow Clarity	Sequences are implicit across bullets rather than numbered, and several operations are destructive or batch (prebuild --clean wiping native dirs, OTA rollback, autoIncrement) without explicit validation checkpoints or feedback loops, hitting the score-3 cap for destructive/batch operations lacking validation.	3 / 5
Progressive Disclosure	Well under 50 lines with no need for external references, organized into three clear sections (CNG, EAS Build/Update, Expo Router) plus a docs link; per the simple-skill exception this scores 5 without bundle files.	5 / 5
	Total	18 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A high-quality, third-person description that concretely enumerates capabilities and pairs them with an explicit multi-trigger 'Use when' clause. It is specific, well-scoped to Expo, and carries low conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Scaffolds Expo/React Native apps, configures EAS Build profiles, manages native modules via CNG, sets up Expo Router navigation, and uses EAS Update for OTA deployments') with comprehensive coverage across the Expo domain, matching the score-5 anchor.	5 / 5
Completeness	Clearly answers 'what' (scaffolds, configures, manages, sets up, uses EAS Update) and 'when' via an explicit 'Use when ...' clause listing five concrete trigger scenarios, matching the score-5 anchor.	5 / 5
Trigger Term Quality	Good natural-term coverage ('creating React Native apps with Expo', 'configuring EAS builds', 'setting up Expo Router', 'deploying OTA updates'); a few common phrasings like 'prebuild', 'OTA update', or file extensions are missing, so it sits just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	Targets a clear Expo-specific niche with distinct triggers (EAS, CNG, Expo Router, OTA) and minimal overlap risk with other skills, matching the score-5 anchor.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: monkilabs/opencastle
Path: src/orchestrator/plugins/expo/SKILL.md
Commit: f297837

Reviewed: 1 day 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.