Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rshankras/run-simulator
Build, install, launch, and screenshot an iOS app in the Simulator to verify a change visually.
Passed 18 of 20 test cases with the skill, and 15 of 20 without it.
and 1 more in the full report
4 fixed16 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
On a cold simulator boot, the first screenshot taken immediately after launch shows the splash screen. Should we immediately mark the app as crashed?
| Checked | Without skill | With skill |
|---|---|---|
| Re-captures the screenshot after a brief delay before declaring failure. | Missed | Passed |
The instructions your model reads when the skill loads.
Launches the actual app in the iOS Simulator and drives it far enough to see what a user would see. Building proves the code compiles; this skill proves it runs. The payoff is a screenshot of the live app that you read back to confirm the change — a blank or crashed frame is a failure, not a pass.
This skill is generic. Nothing about a specific app is hardcoded — the scheme, simulator, product path, and bundle id are all discovered at runtime.
Use this skill when the user:
Do not use it for unit/UI test runs (xcodebuild test) — that's a different
goal. This is about meeting the app as a user would.
Run the steps in order. Each step's output feeds the next, so don't hardcode values a previous step can discover.
Prefer a workspace over a bare project when both exist (CocoaPods/SPM setups often require the workspace):
# Find the container
ls *.xcworkspace 2>/dev/null || ls *.xcodeproj 2>/dev/null
# List schemes (use -workspace X.xcworkspace OR -project X.xcodeproj)
xcodebuild -list -project <App>.xcodeproj 2>/dev/null
test cases passed, vs 15 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.