CtrlK
BlogDocsLog inGet started
Tessl Logo

codex-expo-run-actions

Wire Expo projects into the Codex app with project-local run scripts and .codex/environments/environment.toml actions. Use when the user wants the Codex app Run button, build/run actions, action buttons, or a stable Expo start/run workflow from Codex.

79

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The content is a lean, well-structured instruction skill: a sequenced workflow with a validation checkpoint, concrete commands and paths, guardrails, and a single clearly-signaled reference file for the executable script. It respects Claude's intelligence and the context budget.

DimensionReasoningScore

Conciseness

The body uses terse imperative bullets and assumes Claude's competence, never explaining what Expo or Metro is; every section (workflow, guardrails, output) earns its tokens.

3 / 3

Actionability

It gives concrete commands (`expo start`, `npx expo`, `--ios`, `--android`), exact file paths (`.codex/environments/environment.toml`, `script/build_and_run.sh`), and points to the executable script template in the reference, yielding specific actionable guidance.

3 / 3

Workflow Clarity

A clear 5-step sequence is given with an explicit verification checkpoint in step 5 ("run ./script/build_and_run.sh --help or a short non-server mode... to sanity-check syntax").

3 / 3

Progressive Disclosure

The body is a well-organized overview with one clearly signaled, one-level-deep reference (references/expo-run-button-bootstrap.md, which exists) holding the full script template, keeping SKILL.md lean.

3 / 3

Total

12

/

12

Passed

Description

100%

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, concrete, and clearly states both capability and trigger conditions in third person. It names specific artifacts (run scripts, environment.toml) and natural trigger terms without fluff.

DimensionReasoningScore

Specificity

"Wire Expo projects into the Codex app with project-local run scripts and .codex/environments/environment.toml actions" names multiple concrete actions (wiring, run scripts, environment.toml actions) rather than vague language.

3 / 3

Completeness

It explicitly answers both what (wire Expo into Codex via run scripts + environment.toml) and when ("Use when the user wants the Codex app Run button, build/run actions, action buttons...").

3 / 3

Trigger Term Quality

"Codex app Run button, build/run actions, action buttons, or a stable Expo start/run workflow from Codex" covers natural phrases a user would actually say when they need this skill.

3 / 3

Distinctiveness Conflict Risk

The Codex+Expo integration niche is narrow with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
openai/plugins
Reviewed

Table of Contents

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.