Automated summary
This skill walks through preparing and submitting a mobile app to the App Store and Google Play, from the pre-submission checklist to release management and rejection handling.
Strengths
- Covers both platforms with separate steps for App Store Connect and Google Play Console
- Provides a concrete checklist: icons, screenshots per required size, privacy policy, age rating
- Details a phased rollout strategy (1% → 5% → 20% → 100%) with crash-rate monitoring
- Cites specific Apple guideline numbers that commonly trigger rejections (4.0 Design, 5.1.1 Privacy)
Limitations
- Explicitly excludes enterprise, web, and desktop distribution
- Offers tool mentions like Fastlane snapshot or EAS rather than full automation scripts
- Limited depth on ASO copywriting and localization beyond a checkbox item
Use it when preparing a first submission or an update for an iOS/Android app and you need to structure metadata, screenshots, and the release strategy.
Avoid it for internal, web, or desktop app distribution, or when the need is building the app rather than shipping it to a store.
Security analysis
SafeThe skill only provides app-store submission guidance and checklists. It declares Read, Write, and Grep but contains no executable commands, network calls, credential handling, destructive actions, or obfuscated payloads. The risk of listing it is minimal.
No concerns found
How this analysis is madeExamples
I'm submitting my React Native app to the App Store for the first time. Walk me through the pre-submission checklist and what metadata I need in App Store Connect.Help me plan a phased rollout on Google Play for version 3.0, including the staged percentages and what crash-free rate should trigger a full release.Apple rejected my app under Guideline 5.1.1 about privacy. Help me understand the issue, fix it, and write a response in the Resolution Center.name: app-store-deploy description: Navigate App Store and Google Play submission — metadata, screenshots, review guidelines, and release management allowed-tools: [Read, Write, Grep] effort: medium
When to activate
- Preparing app for first App Store/Play Store submission
- Creating store listings with optimized metadata
- Generating screenshots and app previews
- Navigating the review process and handling rejections
- Setting up phased releases and A/B testing store listings
When NOT to use
- For internal/enterprise app distribution
- For web app deployment
- For desktop app distribution
Instructions
- Pre-submission checklist. Privacy policy URL, support URL, app icon (1024x1024), screenshots (all required sizes), age rating.
- App Store (iOS). App Store Connect: create app record, upload build via Xcode/EAS, configure pricing/availability, fill metadata.
- Play Store (Android). Google Play Console: create app, upload AAB, complete data safety form, set up store listing.
- Screenshots. iPhone 6.7" + 6.5" (required), iPad 12.9" if universal. Android: phone + 7" + 10" tablet. Use tools like Fastlane snapshot.
- Review guidelines. Apple: no placeholder content, no test accounts that expire, no private API usage. Google: policy compliance, target SDK version.
- Release strategy. Internal testing → closed beta → phased rollout (1% → 5% → 20% → 100%). Monitor crash rates at each stage.
- Handle rejections. Read rejection reason carefully, fix issue, resubmit. Use Resolution Center for appeals. Common: Guideline 4.0 (Design), 5.1.1 (Privacy).
Example
Release Checklist — App Store v2.1.0:
Pre-build:
☐ Update version number (2.1.0) and build number (42)
☐ Update CHANGELOG.md
☐ Run full test suite (unit + integration + UI)
☐ Update screenshots if UI changed
Store metadata:
☐ What's New text (max 4000 chars)
☐ Description updated if features added
☐ Keywords reviewed (App Store only)
Release:
☐ Upload build to App Store Connect / Play Console
☐ Submit for review (App Store) / Rollout to 5% (Play Store)
☐ Monitor crash-free rate >99.5%
☐ Full rollout after 48h at 5%
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/app-store-google-play-submission-mrzxuqhg/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/app-store-google-play-submission-mrzxuqhg' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/app-store-google-play-submission-mrzxuqhg/download' --output '.skill-downloads/app-store-google-play-submission-mrzxuqhg/SKILL.md.part' && mv '.skill-downloads/app-store-google-play-submission-mrzxuqhg/SKILL.md.part' '.skill-downloads/app-store-google-play-submission-mrzxuqhg/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/app-store-google-play-submission-mrzxuqhg/SKILL.md' && test -s '.skill-downloads/app-store-google-play-submission-mrzxuqhg/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/app-store-deploy' && cp -R '.skill-downloads/app-store-google-play-submission-mrzxuqhg' '.claude/skills/app-store-deploy'Cursor
test -f '.skill-downloads/app-store-google-play-submission-mrzxuqhg/SKILL.md' && test -s '.skill-downloads/app-store-google-play-submission-mrzxuqhg/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/app-store-deploy' && cp -R '.skill-downloads/app-store-google-play-submission-mrzxuqhg' '.cursor/skills/app-store-deploy'Codex
test -f '.skill-downloads/app-store-google-play-submission-mrzxuqhg/SKILL.md' && test -s '.skill-downloads/app-store-google-play-submission-mrzxuqhg/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/app-store-deploy' && cp -R '.skill-downloads/app-store-google-play-submission-mrzxuqhg' '.agents/skills/app-store-deploy'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/app-store-google-play-submission-mrzxuqhg'openskills read 'app-store-google-play-submission-mrzxuqhg'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/app-store-google-play-submission-mrzxuqhg/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.