AgentStack
SKILL verified MIT Self-run

Ios Simulator Triage

skill-simiancraft-simiancraft-skills-ios-simulator-triage · by simiancraft

>-

No reviews yet
0 installs
13 views
0.0% view→install

Install

$ agentstack add skill-simiancraft-simiancraft-skills-ios-simulator-triage

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Ios Simulator Triage? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

iOS Simulator Triage (living failure catalog)

Classify first (which layer failed), then recover. Most fixes live in the sibling skills; this skill routes you to them and supplies the logging tools that turn a symptom into a cause.

Route by symptom

  • It never installs or launches (xcodebuild, CocoaPods, or prebuild failed): a **build

failure** -> references/build-failures.md.

  • It launches, then crashes or misbehaves: a runtime failure ->

references/runtime-failures.md, split into app-native and Expo / React-Native because the logs and the fixes differ.

  • It runs, but AXe cannot find or tap the element: an automation failure ->

references/automation-failures.md.

Read the logs first

Every layer has a log that names the cause; guessing without it wastes a cycle. references/logging.md is the cross-cutting tool, indexed by layer: the unified log (simctl spawn booted log stream), the app's stdout and stderr (simctl launch --console), crash reports, the diagnostic bundle (simctl diagnose), and the Metro terminal for the JS layer.

Rules

  • Identify the layer before changing anything; a build fix will not cure a runtime crash.
  • Pull the log before forming a hypothesis; the unified log or the crash report usually names

the cause outright.

  • Every factual claim here and in the references cites a primary source (the tools' own help,

Apple); a prior-art skill is never a source.

Out of scope

Happy-path driving -> ios-simulator and expo-ios-simulator. What makes an app addressable -> mobile-accessibility.

Where to go

  • references/build-failures.md: code signing, CocoaPods, prebuild, and architecture.
  • references/runtime-failures.md: native crashes and the Expo / RN failure modes.
  • references/automation-failures.md: empty describe-ui, missed taps, and blocking overlays.
  • references/logging.md: the unified log, console output, crash reports, and diagnose.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.