Build and manage iOS/macOS projects using native Xcode CLI tools instead of MCP servers.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionxcode-buildExecute the skills CLI command in your project's root directory to begin installation:
Fetches xcode-build from pzep1/xcode-build-skill and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate xcode-build. Access via /xcode-build in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
126
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
126
stars
Build and manage iOS/macOS projects using native Xcode CLI tools instead of MCP servers.
Use this skill when:
Preference: Always use direct CLI commands (xcodebuild, xcrun simctl) instead of XcodeBuildMCP tools.
# List schemes in a workspace
xcodebuild -workspace /path/to/App.xcworkspace -list
# List schemes in a project
xcodebuild -project /path/to/App.xcodeproj -list
# Show build settings
xcodebuild -workspace /path/to/App.xcworkspace -scheme AppScheme -showBuildSettings
# List all simulators
xcrun simctl list devices
# List as JSON (better for parsing)
xcrun simctl list devices --json
# List only available simulators
xcrun simctl list devices available
# Get simulator UUID first
UDID=$(xcrun simctl list devices --json | jq -r '.devices | .[].[] | select(.name=="iPhone 16 Pro") | .udid' | head -1)
# Build
xcodebuild \
-workspace /path/to/App.xcworkspace \
-scheme AppScheme \
-destination "platform=iOS Simulator,id=$UDID" \
-configuration Debug \
-derivedDataPath /tmp/build \
build
# Find the built .app
APP_PATH=$(find /tmp/build -name "*.app" -type d | head -1)
# Install on simulator
xcrun simctl install $UDID "$APP_PATH"
# Launch app
xcrun simctl launch $UDID com.your.bundleid
xcrun simctl io $UDID screenshot /tmp/screenshot.png
For comprehensive command documentation, see:
xcodebuild and xcrun simctl command reference# 1. Boot simulator
xcrun simctl boot $UDID 2>/dev/null || true
# 2. Build
xcodebuild -workspace App.xcworkspace -scheme App \
-destination "platform=iOS Simulator,id=$UDID" \
-derivedDataPath /tmp/build build
# 3. Find and install app
APP=$(find /tmp/build -name "*.app" -type d | head -1)
xcrun simctl install $UDID "$APP"
# 4. Launch with console output
xcrun simctl launch --console $UDID com.bundle.id
# Stream app logs (run in background)
/usr/bin/log stream \
--predicate 'processImagePath CONTAINS[cd] "AppName"' \
--style json &
LOG_PID=$!
# ... interact with app ...
# Stop logging
kill $LOG_PID
# Unit tests
xcodebuild -workspace App.xcworkspace -scheme App \
-destination "platform=iOS Simulator,id=$UDID" \
test
# Specific test class
xcodebuild -workspace App.xcworkspace -scheme App \
-destination "platform=iOS Simulator,id=$UDID" \
-only-testing "AppTests/MyTestClass" \
test
For tapping, typing, and UI element queries, use XCUITest (Apple's native UI testing framework).
This is more powerful than MCP-based automation because:
See XCUITEST_GUIDE.md for complete patterns.
Quick example:
// In a UI test file
func testLogin() {
let app = XCUIApplication()
app.launch()
// Type in text field
app.textFields["email"].tap()
app.textFields["email"].typeText("[email protected]")
// Tap button
app.buttons["Login"].tap()
// Verify result
XCTAssertTrue(app.staticTexts["Welcome"].exists)
}
Run UI tests:
xcodebuild -workspace App.xcworkspace -scheme AppUITests \
-destination "platform=iOS Simulator,id=$UDID" \
test
Unlike MCP, CLI tools don't maintain session state. Use environment variables or a config file:
# Set up session variables
export XCODE_WORKSPACE="/path/to/App.xcworkspace"
export XCODE_SCHEME="App"
export SIM_UDID="DD5E339B-468E-43C7-B219-54112C9D3250"
export APP_BUNDLE_ID="com.your.app"
# Use in commands
xcodebuild -workspace "$XCODE_WORKSPACE" -scheme "$XCODE_SCHEME" ...
xcrun simctl launch "$SIM_UDID" "$APP_BUNDLE_ID"
# Check available destinations
xcodebuild -workspace App.xcworkspace -scheme App -showDestinations
# Use exact destination string from output
# Check if already booted
xcrun simctl list devices | grep Booted
# Force shutdown and reboot
xcrun simctl shutdown $UDID
xcrun simctl boot $UDID
# Check derived data path you specified
ls -la /tmp/build/Build/Products/Debug-iphonesimulator/
# Or use default derived data
ls ~/Library/Developer/Xcode/DerivedData/
| Feature | XcodeBuildMCP | This Skill |
|---|---|---|
| Build | build_sim({...}) |
xcodebuild -workspace ... build |
| List sims | list_sims() |
xcrun simctl list devices |
| Launch app | launch_app_sim({...}) |
xcrun simctl launch $UDID $BUNDLE |
| Screenshot | screenshot({...}) |
xcrun simctl io $UDID screenshot |
| Tap/Type | tap({x,y}), type_text({...}) |
XCUITest framework |
| Session state | Built-in | Environment variables |
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
anthropics/claude-code
mblode/agent-skills
github/awesome-copilot
leonxlnx/taste-skill
sickn33/antigravity-awesome-skills
erichowens/some_claude_skills
Useful defaults in xcode-build — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
xcode-build is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: xcode-build is focused, and the summary matches what you get after install.
Registry listing for xcode-build matched our evaluation — installs cleanly and behaves as described in the markdown.
xcode-build has been reliable in day-to-day use. Documentation quality is above average for community skills.
We added xcode-build from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in xcode-build — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added xcode-build from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Keeps context tight: xcode-build is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend xcode-build for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 70