feat: Add Mac App Store submission skill #296
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
A skill for automating Mac App Store submissions via Chrome DevTools MCP. ~95% automatable - the entire App Store Connect UI flow (metadata, screenshots, submission) can be handled automatically. Only manual step: Certificate and provisioning profile setup in Xcode (one-time per app/team). Covers: - Privacy Policy setup - Age Ratings (7-step questionnaire) - Primary Category selection - Pricing configuration - Content Rights - Screenshot upload - Build selection and submission Includes workarounds for common issues like stubborn dropdowns and the "Content Rights required" error that blocks many first-time submitters. Co-Authored-By: Claude Opus 4.5 <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
A skill for automating Mac App Store submissions via Chrome DevTools MCP. Approximately 95% of the submission process can be automated - the entire App Store Connect UI flow (metadata, screenshots, submission) can be handled automatically by Claude.
Only manual step: Certificate and provisioning profile setup in Xcode (one-time per app/team).
What it covers
Why this is useful
Many developers find the App Store Connect UI confusing, especially first-time submitters who encounter errors like "Content Rights required" without clear guidance on where to fix it. This skill documents the complete workflow with solutions to common blockers.
Differentiation from existing tools
They're complementary: this skill is the "quick path" for occasional submitters, while the MCP server is better for CI/automation pipelines.
Test plan
🤖 Generated with Claude Code