Works with
Packaged from the source skill for Claude, Codex and 4 more.
About this skill
Mobile Release brings local project checks and staged-rollout decisions into one workflow. Three Python utilities inspect iOS privacy declarations, selected Android release settings and supplied crash or ANR counts. They read files or data you provide rather than querying store accounts.
Use this skill when
- An iOS project needs a review of required-reason API declarations, purpose strings and vendored SDK privacy manifests.
- An Android release needs checks against the packaged target-API and component-configuration rules.
- A rollout decision should compare actual affected-user counts with a baseline instead of relying on a percentage alone.
What it can do
The scripts produce findings with distinct outcomes for warnings, invalid input and blocking conditions. The rollout utility uses baseline and new-release counts to propose proceed, hold or halt. References and a release checklist explain the evidence expected around the checks.
The packaged rule tables are dated snapshots, not a live feed of store policy. Confirm current platform requirements before submission, choose privacy explanations that match the code’s actual use and review any rule that may have changed. The tools do not upload a build, validate every dependency or guarantee acceptance by Apple or Google. A rollout result also depends on representative and correctly recorded input counts.
Typical workflows
- Inspect an iOS candidate: supply the local project and declared API uses, review manifest and purpose-string findings, then correct the project before rerunning the check.
- Inspect an Android candidate: select the relevant form factor, review target-API and exported-component findings and identify declarations requiring store-console attention.
- Assess a staged rollout: provide comparable baseline and release counts, investigate blockers or an insufficient sample, and keep the final rollout decision with the release owner.
What is inside the skill
Section headings from the original SKILL.md (about 598 words of instructions). Read the full text in the source repository before installing.
- Workflow
- Hard rules
- Scripts
- References and assets
Bundled files
assets/release_checklist.mdassets/rollout.example.csvreferences/ios_submission_rules.mdreferences/play_release_rules.mdreferences/staged_rollout_gates.mdscripts/android_release_check.pyscripts/ios_privacy_manifest_check.pyscripts/rollout_gate.pyLICENSE
Example prompts
- Review this local iOS release candidate for privacy-manifest and purpose-string gaps. Explain the finding next to the actual API use, identify outdated rule-table assumptions and do not submit the build.
- Inspect this Android project for release blockers using the phone form factor. Report target-SDK, exported-component and debuggable-setting findings, then list platform requirements we must recheck against current official guidance.
- Compare the supplied baseline and new-release rollout counts. Distinguish a measurable regression from an insufficient sample and produce a release-owner review note without widening the rollout.
How to install Mobile Release
Claude Packaged
- Download the Claude package from the skill page. The ZIP contains one folder named after the skill, with SKILL.md and any bundled reference files.
- For Claude Code, unpack the folder into ~/.claude/skills/ to use it in every project, or into .claude/skills/ inside a repository to share it with your team.
- For Claude apps, upload the ZIP in the Skills section of the capabilities settings.
- Start a new session and describe the task in your own words. Claude picks the skill when the request matches its description.
Codex Packaged
- Download the Codex package. The ZIP contains one folder named after the skill, with SKILL.md and bundled resources.
- Unpack the complete folder into .agents/skills/ inside your repository, or into ~/.agents/skills/ for personal use. Preserve its relative reference-file paths.
- Start a new Codex session and invoke the skill by name or with $skill-name, or describe a matching task.
- AGENTS.md is separate project guidance. The ZIP does not generate or modify that file.
GPT Packaged
- Download the GPT package from the skill page.
- Create or edit a custom GPT (or a ChatGPT project) and paste the contents of SKILL.md into the instructions field.
- Upload the bundled reference files as knowledge so the GPT can consult them.
- Test with one of the example prompts from the skill page and adjust the instructions if your use case differs.
Gemini Packaged
- Download the Gemini package from the skill page.
- For a project, unpack the complete folder into .gemini/skills/ or .agents/skills/. For personal use, use ~/.gemini/skills/ or ~/.agents/skills/.
- Run /skills reload in Gemini CLI, then /skills list to check discovery. There is no need to paste the skill into GEMINI.md.
- Test a matching task and verify the referenced tools and files are available.
Cursor Packaged
- Download the Cursor package from the skill page.
- Unpack the complete skill folder into .cursor/skills/ or .agents/skills/ in your project. For personal local use, ~/.cursor/skills/ and ~/.agents/skills/ are also supported.
- Start a new Cursor session. Type / in Agent chat and select the skill name, or describe a matching task.
- Commit the skill folder and resources for team use. Personal local skills are not automatically available to remote agents or automation runs.
OpenCode Packaged
- Download the OpenCode package from the skill page.
- Unpack the complete folder into .opencode/skills/ in your project, or ~/.config/opencode/skills/ for personal use. OpenCode also supports .agents/skills/ and .claude/skills/ compatibility locations.
- Keep supporting files at their original relative paths. AGENTS.md is separate project-wide guidance and is not generated by this ZIP.
- Start OpenCode in the project and test a matching task with the model and permissions you use.
Permissions & security
Inspect the source, license and declared permissions before use. Read the scripts before running them. Review method
Mobile Release FAQ
What does the Mobile Release skill do?
Inspect iOS and Android project files for selected release issues, then compare rollout crash counts with a baseline. Uses dated local rules and does not submit to either store.
Which AI agents can use Mobile Release?
Packages for Claude, Codex and 4 more are built from the same source instructions.
How do I install Mobile Release in Claude?
Download the Claude package from the skill page. The ZIP contains one folder named after the skill, with SKILL.md and any bundled reference files. For Claude Code, unpack the folder into ~/.claude/skills/ to use it in every project, or into .claude/skills/ inside a repository to share it with your team.
Who made Mobile Release and what is the license?
Mobile Release is published by Alireza Rezvani under the MIT license. The source is https://github.com/alirezarezvani/claude-skills/tree/main/engineering/mobile-release/skills/mobile-release. The catalog keeps the original attribution.
What permissions does Mobile Release need?
Declared permissions: read project files, write generated skill files. Risk level: low. Check the scripts in the source before running them.