agentsclimarketplace

Rocketsim

Skill patrickserrano/lacquer/profiles/ios/skills/rocketsim

Use RocketSim to inspect visible UI and interact with iOS Simulator apps. Detects the installed RocketSim version, loads the matching bundled RocketSim CLI guidance, and helps agents read visible accessibility elements, navigate screens, tap, long-press, swipe, type text, press simulator hardware buttons, and automate simulator flows reliably. Use when: (1) the user mentions RocketSim, the rocketsim command, or RocketSim CLI, (2) interacting with an app in the iOS Simulator, (3) navigating or testing a simulator app with AI, (4) reading visible UI state or accessibility elements, (5) tapping, long-pressing, swiping, typing, or pressing simulator buttons, (6) using RocketSim instead of ad-hoc simulator automation.From its SKILL.md

Install
npx -y skills add patrickserrano/lacquer --skill rocketsim

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

5.2 KB, ~1.1k tokens by cl100k_base, as published. Nobody here has run it

RocketSim Agent Skill

This skill lets agents use RocketSim as a reliable Simulator interaction layer. It finds a valid RocketSim app bundle, loads the matching bundled CLI reference, and hands off to the installed RocketSim version so simulator automation stays version-aware and in sync with the app on disk.

There is no vendored copy of RocketSim's own usage docs in this repo. The RocketSim.app bundle ships its own Agent-Skill file (Contents/Resources/Agent-Skill/SKILL.md) and CLI binary (Contents/Helpers/rocketsim) — this skill's entire job is locating the installed app and handing off to whatever that bundled file says, so guidance always matches the exact RocketSim build on disk instead of drifting out of sync with a copy pinned in this repo. If you're replicating this fleet's setup elsewhere: this is why rocketsim is a thin discovery/delegation wrapper rather than a full reference skill like the others in this profile — the real content lives in the paid app itself (https://www.rocketsim.app), not here.

Step 1: Locate and validate RocketSim.app

Developer machines can have multiple RocketSim installs side-by-side, such as an App Store build plus a locally built or renamed copy. Do not assume /Applications/RocketSim.app is the right app, and do not continue unless you validate the bundled skill and CLI paths first.

Prefer the running RocketSim app

If RocketSim is already running, prefer that app bundle first:

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
' "$APP_PATH"

If that prints a path, validate it before continuing.

Otherwise, enumerate candidate installs

If RocketSim is not running, gather candidate app bundles instead of taking the first match:

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

Then also check common fallback paths, including renamed installs:

  1. /Applications/RocketSim.app
  2. /Applications/RocketSim 2.app
  3. ~/Applications/RocketSim.app
  4. ~/Applications/RocketSim 2.app

Validate every candidate before continuing

Given a candidate app path (APP_PATH), the following two files must exist:

  • APP_PATH/Contents/Resources/Agent-Skill/SKILL.md
  • APP_PATH/Contents/Helpers/rocketsim

Use this validation:

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

Pick the first candidate that passes validation. If RocketSim is already running, only continue with the running app if it passes validation.

If no candidate passes validation, stop immediately and tell the user:

I found RocketSim installs, but none of them expose the bundled Agent Skill and CLI that this workflow requires. Please launch or install a current RocketSim build from the Mac App Store: https://apps.apple.com/us/app/rocketsim-for-xcode-simulator/id1504940162

Step 2: Resolve Paths

Given the app path (APP_PATH), derive:

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

Discovery contract

Before moving on to Step 3, all of the following must be true:

  • APP_PATH points to the RocketSim bundle you intend to use.
  • APP_PATH/Contents/Resources/Agent-Skill/SKILL.md exists.
  • APP_PATH/Contents/Helpers/rocketsim exists and is executable.
  • If RocketSim is already running, the chosen APP_PATH should be the running app bundle.

If any of these checks fail, stop and resolve discovery first. Do not attempt simulator interaction without a validated CLI path.

Step 3: Read the Bundled Skill

Read the file at APP_PATH/Contents/Resources/Agent-Skill/SKILL.md and follow its instructions. Wherever the bundled skill references the CLI binary, use the resolved absolute path from Step 2.

Step 4: Verify RocketSim is Running

Before executing any CLI command, verify the app is running:

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

If not running, ask the user to launch RocketSim before proceeding.

If RocketSim is running from a different app bundle than the APP_PATH you resolved, restart discovery and prefer the running app bundle.

Integrates with the third-party RocketSim app itself (paid, not bundled) — this discovery/delegation logic is this repo's own, not vendored from anywhere.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most automation workflows skills give in ~1.1k tokens

Counted across 745 of the 1,008 authors here whose files we hold, read 2026-08-07

  • Write conventional commit messagesin 36 of 745, across 35 files
  • Delete branches after mergein 30 of 745, across 21 files
  • Make atomic commitsin 25 of 745, across 15 files
  • Write minimal code to pass testsin 22 of 745, across 10 files
  • Re-snapshot after navigation or DOM changesin 21 of 745, across 13 files
  • Use try-catch for error handlingin 20 of 745, across 8 files
  • Run tests before committingin 20 of 745, across 12 files
  • Write tests before implementationin 20 of 745, across 8 files
  • Configure branch protection rulesin 19 of 745, across 5 files
  • Explain the why in commit messagesin 19 of 745, across 9 files
  • Refactor code while tests remain greenin 19 of 745, across 6 files
  • Interact with elements using refsin 19 of 745, across 11 files

Said here and by no other author read

  • prefer the running RocketSim app bundle
  • enumerate candidate RocketSim app bundles
  • check common fallback paths for installs
  • validate every candidate before continuing
  • verify the required bundled files exist
  • pick the first candidate that passes validation

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,645. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.