Capgo Cloud

This is the traffic controller for multi-step Capgo workflows that touch more than one product area. You'd reach for it when a request spans native builds, OTA releases, store publishing, and org setup, then it routes you to the specific skill once the intent is clear. Think of it as the entry point when someone says "I need to build and ship my app through Capgo" without specifying whether they mean hosted builds, live updates, or App Store submission. The source is candid about its job: figure out what the user actually needs, then hand off to capgo-native-builds, capgo-release-management, or one of the other specialized skills. It's an umbrella, not a destination.

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

View on GitHub

Install

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

Installs into .claude/skills of the current project.

Files

Capgo Cloud

Plan and sequence Capgo Cloud work that spans native builds, OTA releases, store publishing, and org administration.

When to Use

TRIGGER when:

The user wants "a hosted mobile cloud" for a Capacitor app: native builds, live updates, and publishing together.
The user is replacing a hosted build-and-deploy service and needs the Capgo product mapping.
The user asks which Capgo pieces they need and in what order.

Do not use when the request is already about one area:

Native cloud builds and signing: capgo-native-builds
Bundle uploads, channels, rollouts, rollback, encryption: capgo-release-management
Updater plugin wiring and debugging: capgo-live-updates
Org, member, and security policy: capgo-organization-management
CLI auth, command lookup, MCP setup only: capgo-cli-usage
Repo-owned pipeline design (CI files, release gates): capgo-release-workflows
Store listing and submission prep: capacitor-app-store, capacitor-apple-review-preflight
Migrating from Ionic Appflow: ionic-appflow-migration