Use this skill to create a new App Store Connect app by driving the web UI.
Works with
This is opt-in, local-only automation that requires the user to be signed in.
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionasc-app-create-uiExecute the skills CLI command in your project's root directory to begin installation:
Fetches asc-app-create-ui from rudrankriyam/asc-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-app-create-ui. Access via /asc-app-create-ui 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
710
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
710
stars
Use this skill to create a new App Store Connect app by driving the web UI. This is opt-in, local-only automation that requires the user to be signed in.
# Register the bundle ID via public API (if not already registered)
asc bundle-ids create --identifier "com.example.app" --name "My App" --platform IOS
# Confirm no app record exists yet
asc apps list --bundle-id "com.example.app" --output json
Navigate to https://appstoreconnect.apple.com/apps and ensure the user is signed in.
The "New App" button (blue "+" icon) opens a dropdown menu, not a dialog directly.
The platforms are checkboxes (not radio buttons). Click the checkbox for the desired platform(s):
NamePrimary Languageselect_option or equivalent with the language label (e.g., "English (U.S.)").Bundle ID<select> dropdown. The options load asynchronously after platform selection."My App - com.example.app"SKULimited Access or Full Access.<span> overlays.<span>.scrollIntoView on the radio element first, then click the radio ref directly. This bypasses the overlay interception./apps/<APP_ID>/...).asc apps view --id "APP_ID" --output json --pretty
# or
asc apps list --bundle-id "com.example.app" --output json
asc app-setup info set --app "APP_ID" --primary-locale "en-US"
asc app-setup categories set --app "APP_ID" --primary GAMES
asc web apps availability create \
--app "APP_ID" \
--territory "USA,GBR" \
--available-in-new-territories true
Use the experimental web flow above only for the first availability bootstrap. If app availability already exists, switch to asc pricing availability edit --app "APP_ID" ... for later territory changes.
The first click opens a menu with "New App" and "New App Bundle". You must click the menu item, not just the button.
Apple's custom radio buttons wrap the <input type="radio"> in styled <span> elements. Direct ref-based clicks may fail with "click target intercepted". The fix is:
scrollIntoView).After selecting a platform, the Bundle ID dropdown shows "Loading..." and is disabled. Wait for it to become enabled and populated before selecting.
Apple's Ember.js forms use custom change handlers. browser_fill (atomic set) may not trigger validation. If the Create button stays disabled after filling all fields:
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.
ceorkm/mobile-app-ui-design
anthropics/claude-code
mblode/agent-skills
github/awesome-copilot
sickn33/antigravity-awesome-skills
leonxlnx/taste-skill
asc-app-create-ui reduced setup friction for our internal harness; good balance of opinion and flexibility.
asc-app-create-ui fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
asc-app-create-ui has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: asc-app-create-ui is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend asc-app-create-ui for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
asc-app-create-ui is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in asc-app-create-ui — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added asc-app-create-ui from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
asc-app-create-ui reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for asc-app-create-ui matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 43