Capgo Release Management

If you're using Capgo for over-the-air updates in your Capacitor app, this skill walks Claude through the standard release workflow: uploading bundles, managing channels, running compatibility checks before rollout, and setting up encryption keys. It's basically a guard rail for the Capgo CLI so you don't accidentally push a bundle to the wrong channel or skip a compatibility check that'll break production. The skill won't help with native builds or org-level admin stuff, but for the day-to-day work of shipping bundles and controlling who gets what version, it keeps the common mistakes at bay. Most useful when you're juggling multiple channels or need to remember the encrypt-before-upload dance.

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

View on GitHub

Install

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

Installs into .claude/skills of the current project.

Files

Capgo Release Management

Ship, promote, roll back, and clean up Capgo OTA bundles from the CLI.

Facts below were checked against @capgo/cli 8.77 (October 2026). Every command accepts -a, --apikey. The appId can be omitted inside a Capacitor project.

When to Use

TRIGGER when:

The user uploads, lists, deletes, or cleans up bundles, or asks which version a channel serves.
The user creates or configures channels, promotes staging to production, starts, pauses, or rolls back a progressive rollout, or rolls back a bad release.
The user asks whether a change is OTA-safe (bundle compatibility, bundle releaseType).
The user sets up bundle encryption (key create, key save, --key-v2).

Do not use when:

The work is app-side updater code or config (notifyAppReady, autoUpdate, setChannel). Use capgo-live-updates.
A native binary is needed. Use capgo-native-builds.
The user manages organizations, members, 2FA, or API-key policy. Use capgo-organization-management.
The user wants an end-to-end release pipeline design. Use capgo-release-workflows.