eas-simulator

Mechanism

When It Triggers · How It Works · What It Produces

Breaks down how the skill works and what it produces, so you can quickly judge whether it fits your scenario and value.

Trigger

When a user (or agent) needs to run/control an Expo app on a remote iOS/Android simulator hosted on EAS cloud — especially on Linux/CI/cloud sandbox with no local sim, or for agent-driven screenshot/click sessions, live dev-build reload, or shareable browser preview.

Mechanism

Detect host: if no local sim (non-Darwin or no simctl), proceed with EAS Simulator; on macOS ask first.
Run all commands via npx --yes eas-cli@latest simulator:* (experimental hidden API).
Core loop: simulator:start (writes .env.eas-simulator) → install app → simulator:exec npx agent-device@latest ... to drive (open/tap/screenshot) → simulator:stop.
Match build type to goal (dev build for live edit; static for screenshot).

Result

A cloud simulator session with the user's app installed and driven remotely; produces screenshots, live browser preview URL, and verification of app behavior without local sim infrastructure.

Use Cases

Two Typical Use Cases

Scenario 01

Linux dev verifies app on cloud iOS sim

A developer on a Linux machine or a headless CI agent cannot run Xcode or Android Studio simulators locally. They use this skill to start an EAS cloud iOS simulator, install a dev build via agent-device, and let the agent tap through flows and capture screenshots. Value: verifies app behavior on real iOS without a Mac, and catches UI bugs before release.

Scenario 02

Test missing iOS version via cloud sim

A macOS user lacks a specific iOS version and wants an agent to test a feature remotely. The skill starts a cloud simulator of that iOS version, streams a browser preview URL for the user to watch, and drives the app to screenshot key screens. Value: tests against an iOS version the local machine can't provide, with a shareable live preview for stakeholders.

Skill Relationships

Which Skills I Use · Which Skills Use Me

Dependency relationships read as "the upper tier points to the lower tier." The current Skill sits in the middle tier — above are Skills that depend on it, below are Skills it depends on.

Tier 1 · These Skills Use Me

No explicit dependency

Tier 2 · Current Skill

eas-simulatorCli Manual · Workflow

Tier 3 · I Use These Skills

No explicit dependency on other Skills

Full Relationship Graph

Browse this skill's relationships within its skillset. Click a node to switch the side panel; use the search box to jump to any skill.

Skill File

SKILL.md

Open in GitHub ↗

SKILL.mdLoading from GitHub…

Skill Composition

Open in GitHub ↗

SKILL.md20.0%
references60.0%
other20.0%

▸skills/eas-simulator/
▸root
- ·SKILL.md
- ▸agents
  - ·openai.yaml
- ▸references
  - ·controllers.md
  - ·run-your-app.md
  - ·troubleshooting.md

Per the Agent Skills spec, SKILL.md is the only required file. The colored bars classify the rest into the three spec-aligned optional directories (scripts / references / assets) and an 'other' bucket. The full directory tree is below.

Related in Skillset

You May Also Need These Skills

expo-examples

Expo Examples gives the canonical ~70 `with-*` integration patterns from expo/examples. It helps you find, read, and adapt the version-matched setup for third-party libs into an existing app, or scaffold a new one via `npx create-expo --example`. Value: avoid hand-rolled, mismatched integrations with official, maintained patterns.

Workflow

expo-web-to-native

Migrates an existing web React app to native iOS/Android with Expo by scaffolding a shell, running the web UI in DOM components on day one, then strangling screens to native by value using @expo/ui and expo-router. Produces a shippable native app that reuses web code incrementally with verified parity.

Workflow

expo-data-fetching

Helps implement and debug any network request, API call, or data fetching in Expo apps. Covers fetch API, React Query, SWR, error handling, caching, offline support, and Expo Router loaders. Produces secure, correct networking code with auth and offline readiness, reducing bugs.

Style Guide · Workflow

eas-workflows

Helps developers understand and write EAS CI/CD workflow YAML files for Expo projects. Fetches live JSON schema and docs via a Node script, generates/edits .eas/workflows/*.yml, and validates against the schema. Delivers schema-conformant pipelines and accurate workflow answers for build/deploy automation.

Workflow

/eas-simulator

When It Triggers · How It Works · What It Produces

Trigger

Mechanism

Result

Two Typical Use Cases

Linux dev verifies app on cloud iOS sim

Test missing iOS version via cloud sim

Which Skills I Use · Which Skills Use Me

Full Relationship Graph

SKILL.md

Skill Composition

You May Also Need These Skills

expo-examples

expo-web-to-native

expo-data-fetching

eas-workflows

When It Triggers · How It Works · What It Produces

Trigger

Mechanism

Result

Two Typical Use Cases

Linux dev verifies app on cloud iOS sim

Test missing iOS version via cloud sim

Which Skills I Use · Which Skills Use Me

Full Relationship Graph

SKILL.md

Skill Composition

You May Also Need These Skills

expo-examples

expo-web-to-native

expo-data-fetching

eas-workflows