expo-dev-client

Build and distribute Expo development clients locally or via TestFlight

Quality

59%

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

Quality

Content

57%Scale 1-5

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

This skill provides solid, actionable guidance for building Expo development clients with concrete commands and a useful configuration example. Its main weaknesses are the lack of validation checkpoints in the build/deploy workflows and some verbosity in explaining concepts Claude already understands. The content would benefit from tighter prose, explicit verification steps after builds and installations, and better progressive disclosure for the longer sections.

Suggestions

Add explicit validation checkpoints after key steps (e.g., verify build succeeded before attempting install, verify app launches correctly after installation, check signing status before building).

Trim the 'Key settings' explanations and the 'Using the Dev Client' bullet list—Claude already understands these concepts; just show the commands.

Add a feedback loop for build failures: e.g., 'If build fails → check `eas credentials` → fix signing → rebuild → verify'.

Consider splitting the installation instructions and troubleshooting into a referenced file to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The skill includes some unnecessary explanation (e.g., the 'Key settings' section explaining what `developmentClient: true` does is somewhat obvious, and the 'What dev client provides' bullet list tells Claude things it already knows). The 'Important: When Development Clients Are Needed' section, while useful context, is somewhat verbose. Overall mostly efficient but could be tightened.	3 / 5
Actionability	Provides concrete, executable commands throughout (eas build commands, installation commands, troubleshooting commands) with a complete eas.json configuration example. Minor gaps exist—the local iOS device installation path is vague ('Use Xcode Devices window or ideviceinstaller'), and the tar extraction uses a glob path that may not match actual output.	4 / 5
Workflow Clarity	The TestFlight workflow has a clear sequence (build → submit → download → connect), but there are no validation checkpoints or error recovery loops. For a build/deploy workflow that can fail at multiple points (signing, submission, installation), the absence of explicit validation steps and feedback loops is a notable gap.	3 / 5
Progressive Disclosure	The content is reasonably structured with clear section headers, but everything is inlined in a single file. The troubleshooting section, platform-specific installation details, and the eas.json configuration could benefit from being split out or referenced. No bundle files exist to support progressive disclosure, and no references to external docs are provided.	3 / 5
	Total	13 / 20 Passed

Description

61%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.

The description is concise and identifies a clear domain (Expo dev client builds) with relevant trigger terms like 'TestFlight' and 'Expo'. However, it lacks an explicit 'Use when...' clause and could benefit from listing more specific sub-actions and synonyms to improve selection accuracy.

Suggestions

Add a 'Use when...' clause, e.g., 'Use when the user asks about building Expo dev clients, creating custom development builds, or distributing apps via TestFlight.'

Include additional trigger terms and synonyms such as 'EAS Build', 'dev client', 'custom development build', 'iOS beta testing', or 'local compilation'.

Expand the list of concrete actions, e.g., 'configure build profiles, manage signing credentials, run local builds, submit to TestFlight for beta distribution'.

Dimension	Reasoning	Score
Specificity	Names the domain (Expo development clients) and two concrete actions (build and distribute), but doesn't elaborate on specific sub-tasks like configuring build profiles, managing provisioning, or handling EAS configurations.	3 / 5
Completeness	Has a clear 'what' (build and distribute Expo development clients locally or via TestFlight) but lacks an explicit 'when' clause. There is no 'Use when...' guidance to help Claude know when to select this skill.	3 / 5
Trigger Term Quality	Includes strong natural keywords like 'Expo', 'development clients', 'TestFlight', 'build', and 'distribute' that users would naturally use. Missing some synonyms or related terms like 'dev client', 'EAS Build', 'iOS testing', 'custom dev build', or 'local build'.	4 / 5
Distinctiveness Conflict Risk	Fairly distinct with the combination of Expo, development clients, and TestFlight creating a clear niche. Minor overlap risk with general mobile build or deployment skills, but the Expo + TestFlight specificity reduces conflict.	4 / 5
	Total	14 / 20 Passed

Validation

90%

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 — 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

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/expo-dev-client/SKILL.md
Commit: fbdfd63

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.