Build and export iOS/macOS apps with xcodebuild for App Store Connect upload.
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
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add rudrankriyam/app-store-connect-cli-skills --skill asc-xcode-buildCompatible with
Supported agents
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:
epx add rudrankriyam/app-store-connect-cli-skills --skill asc-xcode-buildFetches 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:
.cursor/skills/asc-xcode-build
Restart Cursor to activate asc-xcode-build. Access via /asc-xcode-buildin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
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.
premium-frontend-ui
github/awesome-copilot · Frontend · same category
frontend-ui-ux
code-yeongyu/oh-my-opencode · Frontend · same category
senior-frontend
alirezarezvani/claude-skills · Frontend · same category
ui-ux-pro-max
nextlevelbuilder/ui-ux-pro-max-skill · Frontend · same category
pyqt6-ui-development-rules
oimiragieo/agent-studio · Frontend · same category
tailwindcss
hairyf/skills · Frontend · same category
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