Tessl • The management layer for AI agent skills

SkillPublic

expo-development

Expo and React Native apps: Continuous Native Generation, EAS Build and Update, Expo Router. Use when creating or configuring an Expo app, its EAS builds, native modules, routes or 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

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

An excellent lean reference: fully executable commands, exact config values, and zero fluff. The only real gap is workflow clarity — the EAS update/rollback and failure-diagnosis paths are described as facts rather than sequenced procedures with verification steps.

Suggestions

Add explicit validation checkpoints to the EAS Update flow, e.g. how to verify a published update is live (`eas update:list`, checking the group/channel mapping) before considering a rollout complete.

Turn the failure-diagnosis guidance into a short ordered sequence (build fails → `eas build:view <id>` → read the log → common fixes such as `eas credentials` for signing errors) so recovery steps are unambiguous.

State a one-line pre-flight check before destructive or batch-ish operations, e.g. confirming `ios/`/`android/` are gitignored and contain no untracked work before running `npx expo prebuild --clean`.

Dimension	Reasoning	Score
Conciseness	Dense, high-signal bullets with zero padding — e.g. "Gitignore both directories", "`eas secret:create` is deprecated" — and it assumes Claude already knows React Native basics; every token earns its place.	5 / 5
Actionability	Guidance is copy-paste ready throughout: exact commands (`npx expo prebuild --clean`, `eas update:republish --group <previous-group-id>`, `eas env:create --visibility secret`), exact config keys (`runtimeVersion: { policy: "fingerprint" }`, `developmentClient: true` + `distribution: internal`), and exact routing examples (`app/(auth)/login.tsx` serves `/login`) covering the common cases.	5 / 5
Workflow Clarity	Sequences exist but are implicit and inline — "Diagnose failures via `eas build:list` then `eas build:view <id>`", "Rollback: `eas update:republish --group <previous-group-id>`" — and no explicit validation checkpoints are given, e.g. how to confirm an OTA update actually landed on a device before treating a rollout as complete.	3 / 5
Progressive Disclosure	The skill is under 50 lines with three well-organized sections (CNG, EAS, Router), no bundle files, and a single docs link — per the rubric's simple-skill guideline, well-organized sections alone merit the top score.	5 / 5
	Total	18 / 20 Passed

Description

83%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 strong description: terse, concrete, third-person, with an explicit and well-scoped "Use when" trigger clause. Its only weaknesses are a couple of missing natural synonyms and slight overlap risk with plain React Native work.

Dimension	Reasoning	Score
Specificity	"Continuous Native Generation, EAS Build and Update, Expo Router" lists several concrete, named capabilities plus actions ("creating or configuring an Expo app"), with minor gaps rather than the comprehensive multi-action coverage of the top anchor.	4 / 5
Completeness	Explicitly answers both: the "what" ("Expo and React Native apps: Continuous Native Generation, EAS Build and Update, Expo Router") and a fully explicit "Use when creating or configuring an Expo app, its EAS builds, native modules, routes or OTA updates" trigger clause with concrete phrases.	5 / 5
Trigger Term Quality	Natural user phrases are well covered — "Expo", "React Native", "EAS builds", "native modules", "routes", "OTA updates" — though a few common variations (e.g. prebuild, TestFlight, publishing) are absent.	4 / 5
Distinctiveness Conflict Risk	A clear Expo-specific niche with distinct triggers, but the inclusion of "React Native apps" creates minor overlap risk with a generic React Native skill.	4 / 5
	Total	17 / 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/skills/expo-development/SKILL.md
Revision: 3942f46

Reviewed: 12 days ago

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.

expo-development

Table of Contents

Is this your skill?