How do I install the IOS Rocketsim Operator skill?

Run npx skillmds@latest add xopoko/ios-rocketsim-operator in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is IOS Rocketsim Operator safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with IOS Rocketsim Operator?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is IOS Rocketsim Operator free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published IOS Rocketsim Operator?

Xopoko (@xopoko) published this skill. Their other Agent Skills are listed on their SkillMD profile.

IOS Rocketsim Operator by xopoko — Agent Skill

Name: IOS Rocketsim Operator
Author: Xopoko

File contents

iOS RocketSim Operator

Before invoking Apple-only binaries, confirm the execution context is macOS. From Windows or Linux, run those steps in a Mac SSH project or through an already configured remote transport; do not retry missing Apple binaries locally.

Use the installed RocketSim app as the versioned Simulator automation layer. Always resolve the matching app bundle, bundled skill, and CLI before interacting with a simulator.

Discovery

Prefer a running RocketSim bundle:

ROCKETSIM_PID="$(pgrep -x RocketSim | head -1)"
APP_PATH=""
if [ -n "$ROCKETSIM_PID" ]; then
  APP_PATH="$(ps -o command= -p "$ROCKETSIM_PID" | sed 's#/Contents/MacOS/RocketSim$##')"
fi
printf '%s\n' "$APP_PATH"

If not running, enumerate candidates with:

mdfind "kMDItemCFBundleIdentifier == 'com.swiftLee.RocketSim'"

Also check /Applications/RocketSim.app, /Applications/RocketSim 2.app, ~/Applications/RocketSim.app, and ~/Applications/RocketSim 2.app.

For each candidate, validate both files:

test -f "$APP_PATH/Contents/Resources/Agent-Skill/SKILL.md" && \
test -x "$APP_PATH/Contents/Helpers/rocketsim"

Use the first valid candidate. If RocketSim is running, use the running bundle only if it validates; otherwise rediscover or stop.

If no candidate validates, tell the user to launch or install a current RocketSim build from the Mac App Store: https://apps.apple.com/us/app/rocketsim-for-xcode-simulator/id1504940162

Required Paths

After discovery, set:

Bundled skill: $APP_PATH/Contents/Resources/Agent-Skill/SKILL.md
CLI: $APP_PATH/Contents/Helpers/rocketsim

Before any CLI call:

pgrep -x RocketSim >/dev/null && echo "Running" || echo "Not running"

If RocketSim is not running, ask the user to launch it. If it is running from a different bundle than APP_PATH, restart discovery and prefer the running bundle.

Handoff

Read the bundled Agent-Skill/SKILL.md and follow it. Wherever it refers to rocketsim, use the resolved absolute CLI path. Do not use ad hoc simulator automation until discovery, validation, and the running-app check pass.

---name: ios-rocketsim-operatordescription: RocketSim iOS Simulator UI: inspect and control accessibility state, gestures, typing, hardware buttons, and CLI automation.---# iOS RocketSim OperatorBefore invoking Apple-only binaries, confirm the execution context is macOS. From Windows or Linux, run those steps in a Mac SSH project or through an already configured remote transport; do not retry missing Apple binaries locally.Use the installed RocketSim app as the versioned Simulator automation layer. Always resolve the matching app bundle, bundled skill, and CLI before interacting with a simulator.## DiscoveryPrefer a running RocketSim bundle:```bashROCKETSIM_PID="$(pgrep -x RocketSim | head -1)"APP_PATH=""if [ -n "$ROCKETSIM_PID" ]; then APP_PATH="$(ps -o command= -p "$ROCKETSIM_PID" | sed 's#/Contents/MacOS/RocketSim$##')"fiprintf '%s\n' "$APP_PATH"```If not running, enumerate candidates with:```bashmdfind "kMDItemCFBundleIdentifier == 'com.swiftLee.RocketSim'"```Also check `/Applications/RocketSim.app`, `/Applications/RocketSim 2.app`, `~/Applications/RocketSim.app`, and `~/Applications/RocketSim 2.app`.For each candidate, validate both files:```bashtest -f "$APP_PATH/Contents/Resources/Agent-Skill/SKILL.md" && \test -x "$APP_PATH/Contents/Helpers/rocketsim"```Use the first valid candidate. If RocketSim is running, use the running bundle only if it validates; otherwise rediscover or stop.If no candidate validates, tell the user to launch or install a current RocketSim build from the Mac App Store:`https://apps.apple.com/us/app/rocketsim-for-xcode-simulator/id1504940162`## Required PathsAfter discovery, set:- Bundled skill: `$APP_PATH/Contents/Resources/Agent-Skill/SKILL.md`- CLI: `$APP_PATH/Contents/Helpers/rocketsim`Before any CLI call:```bashpgrep -x RocketSim >/dev/null && echo "Running" || echo "Not running"```If RocketSim is not running, ask the user to launch it. If it is running from a different bundle than `APP_PATH`, restart discovery and prefer the running bundle.## HandoffRead the bundled `Agent-Skill/SKILL.md` and follow it. Wherever it refers to `rocketsim`, use the resolved absolute CLI path. Do not use ad hoc simulator automation until discovery, validation, and the running-app check pass.

Frequently asked questions

IOS Rocketsim Operator