Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Use when the user needs Xcode build/test/run workflows, simulator or device control, UI automation, screenshots/video, logs, or LLDB debugging through XcodeBuildMCP tools. Includes discovery of projects/schemes, session defaults, and common simulator/device workflows.
Use when the user needs Xcode build/test/run workflows, simulator or device control, UI automation, screenshots/video, logs, or LLDB debugging through XcodeBuildMCP tools. Includes discovery of projects/schemes, session defaults, and common simulator/device workflows.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Use the xcodebuildmcp toolset to build/run/test apps, manage simulators/devices, automate UI, and capture logs/screen media. Default to a safe, repeatable flow: discover β set defaults β execute β verify.
This skill assumes the XcodeBuildMCP server is installed and exposed to your MCP client so the tools appear (e.g., mcp__xcodebuildmcp__build_run_sim). If the tools are missing, follow the setup steps in: references/mcp-setup.md (requirements + MCP client config examples)
"Build and run the iOS app on the latest simulator and take a screenshot." "Run unit tests on the simulator and share the failing test logs." "Open the simulator, navigate to Settings, and toggle Dark Mode." "Install and launch the app on my connected iPhone."
Discover the project/workspace and schemes: mcp__xcodebuildmcp__discover_projs mcp__xcodebuildmcp__list_schemes Set session defaults (so subsequent tools donβt need repeated params): mcp__xcodebuildmcp__session-set-defaults (workspacePath/projectPath, scheme, simulatorId/deviceId) Run the task: Build/run: mcp__xcodebuildmcp__build_run_sim or mcp__xcodebuildmcp__build_run_macos Tests: mcp__xcodebuildmcp__test_sim / mcp__xcodebuildmcp__test_macos / mcp__xcodebuildmcp__test_device Verify and gather evidence: mcp__xcodebuildmcp__screenshot (sim) mcp__xcodebuildmcp__start_sim_log_cap β mcp__xcodebuildmcp__stop_sim_log_cap
Build/Run: iOS simulator, macOS, device installs Testing: simulator/macOS/device Simulator management: list/boot/erase/appearance/location/gestures UI automation: describe UI β tap/type/swipe/gesture Logs & debugging: sim logs, device logs, LLDB attach/breakpoints Media: screenshots, screen recording Load references/workflows.md for detailed step-by-step sequences and command patterns.
Always call mcp__xcodebuildmcp__describe_ui before coordinate-based taps/swipes/long-press. Prefer mcp__xcodebuildmcp__session-set-defaults early to reduce parameter noise. If user didnβt specify target device/simulator, list options and ask (or pick a sensible default with useLatestOS). Avoid destructive actions (erase sims, clean) unless the user asked for them.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.