app-store-publishing

Automate iOS App Store and Google Play submissions with EAS Build workflows.

3|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/Basilisk-Systems/claude-toolkit --skill app-store-publishing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: app-store-publishing
Source: https://github.com/Basilisk-Systems/claude-toolkit/tree/main/skills/app-store-publishing
Command: npx skills add https://github.com/Basilisk-Systems/claude-toolkit --skill app-store-publishing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

App-store publishing tasks are automated end-to-end, reducing time-to-publish and eliminating manual handoffs.

Core Features & Use Cases

  • EAS Build configuration and submit workflows for iOS and Android.
  • Health app readiness considerations and store-specific requirements.
  • IAP integration planning and OTA update coordination across stores.

Quick Start

Configure EAS Build, set up signing and submissions, and push a release to stores.

Frequently Asked Questions about app-store-publishing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate App Store and Google Play submissions for my Expo app?

You can automate App Store and Google Play submissions by orchestrating EAS Build workflows, which handle app signing, build configuration, and store deployment steps end-to-end for Expo and React Native applications.

What do I need to configure in eas.json before submitting to the app store?

Before app store submission, you need to configure eas.json profiles that define build credentials, signing mechanisms, and submission targets to validate and push your iOS and Android releases automatically.

Can I use EAS Build to handle both iOS app signing and store submission?

Yes, EAS Build orchestrates both iOS app signing and store submission by validating credentials, applying app signing configurations, and deploying the final build directly to the App Store and Google Play.

Does this handle store requirements for health apps and IAP integration?

Yes, the submission workflow applies health app readiness considerations and coordinates In-App Purchase integration planning to satisfy cross-store requirements during the deployment process.

What is the best way to coordinate OTA updates with store release submissions?

The best way to coordinate OTA updates with store submissions is to align your release checklists and store metadata deployment with OTA update workflows, ensuring version consistency across stores.

Why does my EAS Build submission fail validation before reaching the store?

EAS Build submission validation often fails when eas.json profiles lack proper signing credentials, app store metadata is incomplete, or cross-store requirements like health app readiness are not met.