capgo-release-management SKILL.md skillA
capgo-release-management from cap-go/capgo-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add cap-go/capgo-skills/capgo-release-management@git:20261012.8082621Pins git:20261012.8082621 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- cap-go/capgo-skills
- Path
skills/capgo-release-management/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261012.8082621, committed Oct 12, 2026
- First version recorded
- Mar 18, 2026
- Size
- 8,807 bytes
- Repository stars
- 74
- License
- MIT
Runs Capgo OTA release operations with the CLI, including `bundle upload` (channels, delta, rollout, encryption, version bumps), `bundle compatibility` and `releaseType` checks, `channel add/set/promote/currentBundle/delete`, progressive rollouts and rollback, `bundle cleanup`, preview QR codes, and `key create/save` encryption setup. Use when the user ships, promotes, rolls back, or cleans up Capgo bundles, or hits upload errors such as "Version X already exists…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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`. ## Command Map | Goal | Command | | --- | --- | …
Read the whole file at its exact version.
How to install
mdr add cap-go/capgo-skills/capgo-release-management@sha256:e342c97c0c013366The line at the top of this page pins the label git:20261012.8082621, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_k246qv2a5vc2akg4)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Mar 18, 2026 and Oct 12, 2026, about one every 69 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261012.8082621 latest | 2026-10-12 | 8082621 | 8,807 B | A | view · diff |
| git:20261011.86834d4 | 2026-10-11 | 86834d4 | 8,676 B | A | view · diff |
| git:20260318.5bd0bc2 | 2026-03-18 | 5bd0bc2 | 1,814 B | A | view · diff |
| git:20260318.faa0d36 | 2026-03-18 | faa0d36 | 1,815 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8807 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
cap-go/capgo-skills · 74 stars · license MIT · pushed 2026-10-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_k246qv2a5vc2akg4 GET https://markdownregistry.com/api/v1/resolve?ref=cap-go/capgo-skills/capgo-release-management GET https://markdownregistry.com/api/v1/blob/e342c97c0c0133660dc6432def376d73234dbbc1b1eaa9d1873fbee6618b06cd
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from cap-go/capgo-skills
Every file in cap-go/capgo-skills