eas-simulator

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.

Agent Skill from expo/skills

Copilot Studio

Passes documented load rules

No documented load rule failed.

Microsoft 365 Copilot Preview, Frontier tenants only

Needs changes

Fails: Instructions are under 20,000 characters (M365-INSTRUCTIONS)
instructions are 25,330 characters
rule · Microsoft 365 Copilot: What is a skill

Warnings (don't change the verdict):

Warning: No sign of network access, package installs or authenticated calls (M365-SANDBOX)
SKILL.md mentions npm/npx install
rule · Microsoft 365 Copilot: Script execution sandbox

An agent can have at most 8 skills. Custom skills aren't available in tenants that use Microsoft Purview Information Barriers.

Agent Skills spec notes

Warning: No experimental allowed-tools field (SPEC-ALLOWED-TOOLS)
uses allowed-tools
rule · Agent Skills specification

Compatible isn't the same as safe. These verdicts only say whether a skill's files follow Microsoft's documented load rules. The checker reads files and never runs them, and it doesn't review what a skill or its scripts actually do. Read a skill's instructions and scripts before you add it to an agent.

Standards signals

Meets the agentskills.io required fields.

Frontmatter	Present and parsed Spec: frontmatter
name	Meets the spec (1-64 chars, a-z 0-9 hyphens) Spec: name
description	Present, 1-1,024 characters Spec: description
compatibility	Absent or under 500 characters Spec: compatibility
Name matches folder	Yes (`eas-simulator`) Spec: name
allowed-tools	Used Note: experimental in the spec; support varies by agent. Spec: allowed-tools

Observed from the public SKILL.md at the commit above on 2026-10-23. Not a certification: AAIF and the Agent Skills project don't certify skills. Validate your own skill with skills-ref validate.

Source repo	expo/skills
Path	plugins/expo/skills/eas-simulator/SKILL.md
Commit checked	`0d035556e377`
Repo license	MIT
Files	6
Scripts	None
Instructions	25,330 characters
Deepest folder	1 below the skill folder
Rules version	2026-10-22

Re-check the latest version How skill checks work

Is this wrong or out of date? Email us. Skills data built 2026-10-23; rules as of 2026-10-22.

Rule-based checks of public files against Microsoft's documented load rules, not tested in Copilot Studio or Microsoft 365 Copilot. Independent project, not affiliated with Microsoft.