atmos-device-previewlisted

Control Atmos Device Preview (iOS Simulator / Android emulator) via `atmos simulator` (screenshot, tap, swipe, type, press) without MCP. Use whenever the user or task needs to tap the simulator, drive an android emulator, interact with device preview, or take a phone screenshot in Atmos. Do not use for macOS desktop capture (atmos-desktop-use) or in-page browser DOM (atmos-browser-use). Not folded into atmos-cli.
AruNi-01/atmos · ★ 6 · Code & Development · score 72

Install: claude install-skill AruNi-01/atmos

# Atmos Device Preview Drive a **claimed** iOS Simulator / Android emulator in the Atmos Simulator tab via `atmos simulator`. **No MCP.** Separate product from Desktop Use and Browser Use — **not** `atmos-cli`. Details: [`references/cli.md`](references/cli.md). ## Prerequisites 1. `atmos` on `PATH`. 2. Workspace sticky: `atmos context set --workspace <id>` (or `--workspace` on the command). Missing workspace → `CONTEXT_REQUIRED`. 3. A **live claim**. v1 tap/screenshot/swipe/type/press never start preview. ## Decision tree 1. If the message already contains a Device Preview chip / pasted prompt / explicit `udid` → use that `udid`. 2. Else `atmos simulator list`. If **one** live claim **in this workspace**, use it and say so. 3. If **several** live claims on the Computer (or none in this workspace but others exist): print `name · platform · project or workspace` (flag the current workspace) and **ask which `udid`**. Do not pick. 4. If zero claims: ask the user to Start the Simulator tab, click Agent, or run `/device-preview`. Do **not** auto-boot. 5. Then screenshot → tap/swipe/type/press **with `--udid`**. | Intent | Command | |--------|---------| | Ready / inventory | `list` then `status` | | Capture | `screenshot --udid …` | | Tap / swipe / type / press | `tap` / `swipe` / `type` / `press` **with `--udid`** | | Probe / start / stop | only if the user asked to open or close preview | | macOS desktop GUI | **other skill** — `atmos-desktop-use` | | Page