eas-simulator agent skill by expo

At a glance

Before you install

Read from the skill's files at the directory's October 19, 2026 snapshot: what ships with it, what its code reads, and the terms it is published under.

• Bundled scripts: none.
• Commands in SKILL.md: its code blocks run npx, which fetches or runs software from outside the skill folder.
• Credential names SKILL.md mentions: EXPO_TOKEN.
• Tool permissions requested: Bash(npx *eas-cli@*), Bash(npx *agent-device@*), Bash(npx expo *), Bash(eas *), Bash(expo *), Bash(xcodebuild*), Bash(pod*), Bash(argent *), Bash(ffmpeg*) (the allowed-tools field of SKILL.md).
• License: MIT, an open-source or open-content license.

Install eas-simulator

The skills CLI works with Claude Code, Codex, Cursor and other agents; the other routes copy the folder by hand.

npx skills add https://github.com/expo/skills/tree/main/plugins/expo/skills/eas-simulator

tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/expo/skills.git "$tmp/repo"
mkdir -p .claude/skills
cp -R "$tmp/repo/"plugins/expo/skills/eas-simulator .claude/skills/
rm -rf "$tmp"

python3 ~/.codex/skills/.system/skill-installer/scripts/install-skill-from-github.py \
    --repo expo/skills \
    --path plugins/expo/skills/eas-simulator

expo/skills is third-party code. Read SKILL.md and any bundled scripts before you install it.

How the author describes it

Run and control a user's app on a remote iOS/Android simulator hosted on EAS cloud. Read before running any `eas simulator:*` commands - it has the current syntax for this experimental API. Use whenever the user needs a simulator they can't run locally - 'run my app on a cloud simulator', 'use eas simulator to run/install/screenshot my app', 'I'm on Linux/Cursor and need an iOS device', 'no sim on this box / headless CI', 'let an agent click through my app and screenshot it', 'test my dev build on a remote sim with live reload', 'stream a sim to my browser' - even when they don't say 'EAS Simulator' or 'cloud'. On a host WITHOUT a local simulator (Linux, CI, cloud sandbox) it's the default; on macOS, do NOT auto-trigger for a plain 'run on the simulator' - use it only for a cloud/remote/shareable sim, an iOS version they lack, or an agent-driven session. NOT for local sims (expo run:ios, Xcode, Android Studio), EAS Build/Update, web preview, or physical devices.

From the description field of SKILL.md. Agents read this line to decide when to load the skill.

Sections in SKILL.md

• When to use
• Cloud vs local: decide this first
• Prerequisites
• Session lifetime
• Check availability first
• The core loop (always the same)
• Always name the session
• Commands at a glance
• Running the user's app — pick a mode
• Driving the device (agent-device)
• When the app crashes: device logs and crash reports (iOS)
• Operating principles
• Stop and clean up
• References
• Submitting Feedback

Files in the skill folder

• SKILL.md
• agents/openai.yaml
• references/controllers.md
• references/logs-and-crashes.md
• references/run-your-app.md
• references/troubleshooting.md

Suede Skill Check: 85/100 · B

eas-simulator passes the required frontmatter check and all seven graded checks, which cover the SKILL.md format, a declared license and a commit in the last year. Those checks earn 56 of the score’s points; the rest come from description quality, instruction depth, bundled files, maintenance and curated-list citations. How the score works.

Where this skill is cited

expo/skills appears in 2 curated lists: heilcheng/awesome-agent-skills, travisvn/awesome-claude-skills.

More developer tools skills

All developer tools and frameworks skills

More from expo/skills

All 25 skills in expo/skills