Build and export iOS/macOS apps with xcodebuild for App Store Connect upload.
Works with
Handles both iOS (IPA) and macOS (PKG) builds through archive and export workflows with xcodebuild
Requires valid signing identity, provisioning profiles, and Xcode command line tools configured
Integrates with asc CLI for uploading builds; macOS uploads require explicit version and build number parameters
Build numbers must be unique and higher than previous uploads; includes commands to check existing
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionasc-xcode-buildExecute the skills CLI command in your project's root directory to begin installation:
Fetches asc-xcode-build from rudrankriyam/app-store-connect-cli-skills 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 asc-xcode-build. Access via /asc-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
708
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
708
stars
Use this skill when you need to build an app from source and prepare it for upload to App Store Connect.
ascBefore archiving, prefer asc xcode version ... over manual pbxproj edits when you need to inspect or bump app versions.
asc xcode version view
asc xcode version edit --version "1.3.0" --build-number "42"
asc xcode version bump --type build
asc xcode version bump --type patch
Notes:
--project-dir "./MyApp" when you are not running from the project root.--target "App" for deterministic reads in multi-target projects.agvtool projects and modern MARKETING_VERSION / CURRENT_PROJECT_VERSION setups.xcodebuild clean archive \
-scheme "YourScheme" \
-configuration Release \
-archivePath /tmp/YourApp.xcarchive \
-destination "generic/platform=iOS"
xcodebuild -exportArchive \
-archivePath /tmp/YourApp.xcarchive \
-exportPath /tmp/YourAppExport \
-exportOptionsPlist ExportOptions.plist \
-allowProvisioningUpdates
A minimal ExportOptions.plist for App Store distribution:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>method</key>
<string>app-store-connect</string>
<key>teamID</key>
<string>YOUR_TEAM_ID</string>
</dict>
</plist>
asc builds upload --app "APP_ID" --ipa "/tmp/YourAppExport/YourApp.ipa"
xcodebuild archive \
-scheme "YourMacScheme" \
-configuration Release \
-archivePath /tmp/YourMacApp.xcarchive \
-destination "generic/platform=macOS"
xcodebuild -exportArchive \
-archivePath /tmp/YourMacApp.xcarchive \
-exportPath /tmp/YourMacAppExport \
-exportOptionsPlist ExportOptions.plist \
-allowProvisioningUpdates
macOS apps export as .pkg files. Upload with asc:
asc builds upload \
--app "APP_ID" \
--pkg "/tmp/YourMacAppExport/YourApp.pkg" \
--version "1.0.0" \
--build-number "123"
Notes:
--pkg automatically sets platform to MAC_OS..pkg uploads, --version and --build-number are required (they are not auto-extracted like IPA uploads).--wait if you want to wait for build processing to complete.Each upload requires a unique build number higher than previously uploaded builds.
In Xcode project settings:
CURRENT_PROJECT_VERSION - build number (e.g., "316")MARKETING_VERSION - version string (e.g., "2.2.0")Check existing builds:
asc builds list --app "APP_ID" --platform IOS --limit 5
-allowProvisioningUpdates flagmacOS requires ICNS format icons with all sizes:
The build number must be higher than any previously uploaded build. Increment it with asc xcode version bump --type build, or resolve a remote-safe number with asc builds next-build-number --app "APP_ID" --version "2.2.0" --platform IOS and then apply it with asc xcode version edit --build-number "NEXT_BUILD" before rebuilding.
xcodebuild -showBuildSettings to verify configurationasc-submission-health skillPrerequisites
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
I recommend asc-xcode-build for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for asc-xcode-build matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: asc-xcode-build is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend asc-xcode-build for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
asc-xcode-build reduced setup friction for our internal harness; good balance of opinion and flexibility.
asc-xcode-build is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: asc-xcode-build is focused, and the summary matches what you get after install.
Solid pick for teams standardizing on skills: asc-xcode-build is focused, and the summary matches what you get after install.
We added asc-xcode-build from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: asc-xcode-build is focused, and the summary matches what you get after install.
showing 1-10 of 58