iOS Simulator Skill
v0.1.221 production-ready scripts for iOS app testing, building, and automation. Provides semantic UI navigation, build automation, accessibility testing, and simulator lifecycle management. Optimized for AI agents with minimal token output.
⭐ 1· 3.5k·16 current·17 all-time
byTristan Manchester@tristanmanchester
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description align with the supplied script: the CLI wraps xcrun simctl and optionally idb for UI/accessibility automation, which is expected for an 'iOS Simulator' skill. Minor incoherence: registry metadata earlier showed no OS restriction and no required binaries, while SKILL.md and the script require macOS (darwin) and xcrun (xcrun/simctl). This is likely a metadata omission but should be corrected.
Instruction Scope
SKILL.md directs the agent to run the included Node script which invokes local tools (xcrun/simctl and optionally idb), list/boot/erase simulators, install/uninstall apps, access app containers, capture screenshots/logs, and write a local state file (.ios-sim-state.json or custom IOS_SIM_STATE_FILE). All actions are within the expected domain for simulator management; there are no instructions to read unrelated system files or exfiltrate data to remote endpoints. The skill does instruct copying/running on a remote macOS node when needed, which is reasonable but requires user caution.
Install Mechanism
No install spec is provided (instruction-only install), and the code is bundled in the skill (scripts/ios-sim.mjs). SKILL.md suggests optional brew/pip installs for idb (facebook/fb tap and fb-idb), which are standard for that tool. There are no downloads from unknown/shortened URLs or archive extraction steps in the manifest.
Credentials
The skill declares no required credentials or env vars; it uses an optional IOS_SIM_STATE_FILE and reads PATH to discover binaries. The script can access simulator app containers and logs (app container, logs, screenshots), which is appropriate for its purpose but means it can read potentially sensitive app data that exists inside simulator files. No unrelated secrets are requested.
Persistence & Privilege
always:false and user-invocable defaults are used. The skill writes a local state file in the working directory (.ios-sim-state.json) and does not request system-wide configuration changes or access to other skills' configs. Autonomous invocation is allowed (platform default) but is not combined with broad credential access or persistent privileges.
Assessment
This skill appears to do what it says: local automation of the iOS Simulator using xcrun/simctl and optionally idb. Before installing or running: 1) Confirm you will run it on a trusted macOS machine (the script requires darwin/Xcode tools). 2) Inspect the included scripts (scripts/ios-sim.mjs) yourself (or have someone you trust review them) because the skill source is listed as unknown. 3) Be aware it will write a local state file (.ios-sim-state.json) in the working directory and can read simulator app containers, logs, and screenshots — avoid running it on a macOS host that holds sensitive data you don't want accessed. 4) If you need idb functionality, install idb from official taps (brew tap facebook/fb; brew install idb-companion; pip install fb-idb) as documented. 5) Ask the publisher to correct registry metadata (declare darwin and xcrun) so the platform can enforce OS/binary restrictions. If you are uncomfortable with an unknown source, run it only on an isolated/test macOS node.Like a lobster shell, security has layers — review code before you run it.
latestvk974g30gjk5v82ede5nay5kwxx7zk25k
License
MIT-0
Free to use, modify, and redistribute. No attribution required.