iOS Simulator Skill

**Judgement:** Strong, production-oriented skill for iOS simulator automation and UI-driven testing, especially well-suited to AI/agent use, but strictly tied to macOS/Xcode environments and with some destructive capabilities that must be handled carefully. **What it does well:** - Wraps `xcrun simctl` and `idb` into a single, Node-only CLI with a broad feature set: simulator lifecycle, app management, screenshots/video, clipboard/URLs, logs, permissions, push, and accessibility-based UI automation. - Output is intentionally minimal and structured (single-line JSON, optional `--pretty` / `--text`), which is ideal for OpenClaw-style agents that need low-token, machine-readable responses. - Maintains simulator state via `.ios-sim-state.json` and `--udid` overrides, helping agents avoid brittle hardcoded device IDs. - Safety tiers plus `--yes` gates for `erase`/`delete` are a good safeguard against accidental simulator data loss in automated flows. **Key risks / limitations:** - **Platform constraint:** Requires macOS with Xcode Command Line Tools (or Xcode). Non-macOS gateways must offload to a remote macOS node; this adds orchestration complexity and potential points of failure. - **Dependencies:** For full UI automation, `idb` (plus `idb_companion`) must be installed and healthy. `idb` can be finicky across Xcode versions, which may reduce reliability unless the environment is well-managed. - **Destructive commands:** `erase` and `delete` (even with `--yes`) can wipe simulator data. In multi-project or shared environments, mis-targeted UDIDs or misuse by agents could disrupt other workflows. - **Privacy/state mutation:** Commands like `privacy *`, `push`, `clipboard set`, `openurl`, and app lifecycle control mutate simulator/app state. While limited to the simulator/device environment, test data or credentials inside simulators could still be affected and logs/screenshots may surface sensitive information. **Recommended scenarios:** - Teams with existing macOS build infrastructure who want an AI/agent to orchestrate iOS simulators end-to-end (boot, install, navigate UI, capture artifacts) for regression or exploratory testing. - CI environments where deterministic simulator selection, headless app launch, and artifact generation (screenshots/videos/logs) are needed with minimal CLI chatter. - Accessibility and UI-tree–driven agents that prefer semantic selectors (labels/text) over coordinate taps and need concise JSON outputs for planning steps. - Automated validation of push notifications, deep links, and permissions flows in a controlled simulator environment. **When to be cautious / consider alternatives:** - If you cannot guarantee access to a macOS/Xcode node or want cross-platform mobile automation, this skill will not be sufficient on its own. - If your workflow involves physical devices or highly flaky `idb` setups, you may need additional tooling or more robust device farm integrations for reliability.