Capgo Native Builds

This handles Capgo's cloud build service for compiling native iOS and Android binaries when you don't want to build locally or set up your own CI. It covers the full workflow: CLI login with API keys, storing signing credentials (Apple certificates, provisioning profiles, Android keystores), requesting builds, and getting either direct download links or automatic uploads to TestFlight and Play Store. The interactive `build init` command is useful for first-time iOS setup since it can generate and save signing material with minimal manual steps. Credentials live in your local `~/.capgo-credentials` directory and only get sent to Capgo during the actual build job. Good for teams that want hosted builds without managing Jenkins or GitHub Actions runners, though you'll still need your own Apple and Google developer accounts.

skills.sh installs: 754
GitHub stars: 77
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add cap-go/capgo-skills --skill capgo-native-builds --agent claude-code

Installs into .claude/skills of the current project.

Files

Capgo Native Builds

Build signed iOS and Android binaries on Capgo Cloud Build and deliver them to the stores or to a temporary download link.

Facts below were checked against @capgo/cli 8.77 and https://capgo.app/docs/builder/ (October 2026). The CLI describes native cloud builds as "limited beta".

When to Use

TRIGGER when:

The user asks for a Capgo Cloud Build, a native build in the cloud, a signed IPA/APK/AAB, a TestFlight, App Store, or Play upload through Capgo, or a temporary build download link or QR code.
The user runs or asks about build init, build request, build prescan, build needed, build last-output, build sync-ios-version, or any build credentials ... subcommand.
A Capgo build fails on signing, provisioning, keystore, prescan, or store upload.

Do not use when:

SKILL.md on GitHub