expo-dev-client

Build and distribute Expo development clients locally or via TestFlight

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/expo-dev-client/SKILL.md

The canonical home for this skill is expo-dev-client in expo/skills

Quality

Content

65%

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

The content is highly actionable with concrete commands and config, but it has no validation checkpoints in the build→install workflow and carries redundancy across the build sections that keeps it from being fully tight or progressively structured.

Suggestions

Add explicit validation checkpoints to the build flow, e.g. after building: 'Run `eas build:view` to confirm the build succeeded before installing.'

Consolidate the repeated `eas build -p ios --profile development` invocations (TestFlight, Local, Specific Platform) into one section that documents the flag variations (`--submit`, `--local`, platform flags).

Move the pinned CLI version ('>= 16.0.1') into a note or 'Requirements' line rather than embedding it in the config example, so time-sensitive info does not age the body.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean commands and config rather than explaining concepts Claude already knows, but the core `eas build -p ios --profile development` command recurs across three sections and a pinned CLI version ('>= 16.0.1') is time-sensitive info not placed in a deprecated section.	2 / 3
Actionability	Provides fully executable, copy-paste-ready commands (`eas build -p ios --profile development --submit`, `xcrun simctl install booted`, `adb install build.apk`) and a complete eas.json config block.	3 / 3
Workflow Clarity	Steps are numbered and sequenced (build → submit → TestFlight email → install), but there are no explicit validation checkpoints between build and install; verification exists only as a separate 'Checking Build Status' section rather than woven into the flow.	2 / 3
Progressive Disclosure	Sections are clearly headed and self-contained with no nested-reference problem, but all content is inline with no progressive-disclosure structure and the overlapping build-command sections could be consolidated for tighter organization.	2 / 3
	Total	9 / 12 Passed

Description

57%

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 is specific and occupies a clear niche, but it answers only the 'what' and not the 'when' — there is no explicit trigger clause to tell Claude when to invoke it.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when your app needs custom native code that Expo Go cannot run, or when distributing an iOS dev client via TestFlight.'

Broaden trigger terms to include common phrasings users actually say: 'dev client', 'EAS Build', 'custom Expo Go'.

Expand the action list beyond 'build and distribute' (e.g. 'Build, install, and distribute Expo development clients locally or via TestFlight') to reach the level-3 specificity anchor.

Dimension	Reasoning	Score
Specificity	Names the domain ('Expo development clients') and two concrete actions ('Build and distribute') plus two delivery channels (locally, via TestFlight), but stops at two verbs rather than listing multiple specific actions like the level-3 anchor.	2 / 3
Completeness	Clearly states what the skill does (build/distribute dev clients) but lacks any 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	Includes relevant natural terms ('Expo development clients', 'TestFlight') a user might say, but omits common variations like 'dev client', 'EAS Build', or 'custom Expo Go'.	2 / 3
Distinctiveness Conflict Risk	The Expo + TestFlight + local-build niche is specific and clearly distinguishable from other skills, making accidental triggering unlikely.	3 / 3
	Total	9 / 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/expo-dev-client/SKILL.md
Commit: 11c74d6

Reviewed: 4 days 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.