Capgo Cli Usage

Cap-go/capgo-skills/skills/capgo-cli-usage

by Cap-go2cfb277a148832bdb1a835b01e4de323687b498bNo license72 starsListed Oct 9, 2026Updated Oct 9, 2026Repository updated today

Guides the agent through the Capgo CLI command surface and routes requests to more specific Capgo skills. Use when the user asks generally about the Capgo CLI, app setup, diagnostics, OTA operations, native builds, or organization commands. Do not use when a more specific Capgo skill already clearly matches the request.

Instructions onlyDevOps & CloudAI & Agents
AI-generated overview

Routes general Capgo CLI requests to the right Capgo sub-skill and explains CLI commands and MCP setup.

What it does
This skill acts as an entry point for the Capgo CLI, describing when a request is general enough to stay at the routing layer and when to hand off to a narrower Capgo skill. It lists routing targets for OTA bundles and channels, native cloud builds, and organization or account commands. It also documents connecting an agent to Capgo through a hosted MCP endpoint or a local CLI MCP, and lists common commands such as init, login, doctor, probe, app add, app list, app delete, app set, app debug, and mcp. It gives brief error-handling guidance for CLI authentication issues.
When to use it
Use it when the user asks generally about the Capgo CLI, when a request spans several Capgo command groups, or when the correct Capgo sub-workflow is not yet clear. It is not meant for requests that already clearly match a more specific Capgo skill.
Requirements
No scripts are shipped; it is instructions only. Using the described workflows requires the Capgo CLI via npx, network access, and either OAuth sign-in or a Capgo API key for the hosted MCP server; a Capgo account is needed for account-related operations.

Capgo CLI Usage

Use this skill as the entry point for Capgo CLI command routing.

When to Use This Skill

  • User asks generally how to use the Capgo CLI
  • The request spans multiple Capgo command groups
  • The right Capgo sub-workflow is not obvious yet

Routing

Route specific workflows to the matching skill:

  • OTA bundles and channels -> capgo-release-management
  • native cloud builds -> capgo-native-builds
  • organizations and account commands -> capgo-organization-management

Connect the Agent to Capgo (MCP)

Capgo has two MCP servers. Use both when available.

  • Hosted MCP: https://api.capgo.app/mcp (streamable HTTP). Nothing to install; the client signs in with OAuth, or sends Authorization: Bearer <Capgo API key>. The hosted MCP includes destructive tools, so use an API key with the smallest role the task needs (read-only for reporting). Covers apps, bundles, channels, progressive rollouts, devices, stats, update health, native build status and logs, webhooks, and push notifications. Example for Claude Code: claude mcp add --transport http capgo https://api.capgo.app/mcp, then /mcp to sign in.
  • Local CLI MCP: npx @capgo/cli@latest mcp (stdio). Needed to upload a bundle from the build folder, request a native build, or run doctor.

No Capgo account yet: sign up at https://console.capgo.app (14-day free trial, no credit card). Docs: https://capgo.app/docs/ai/mcp/

Common Commands

  • init
  • login
  • doctor
  • probe
  • app add
  • app list
  • app delete
  • app set
  • app debug
  • mcp

Prefer the current CLI form:

bash
npx @capgo/cli@latest doctor

Error Handling

  • If the request is specific enough for a narrower Capgo skill, switch to that skill instead of staying at the routing layer.
  • For CLI auth issues, fix login first before troubleshooting downstream commands.

Source and attribution

Source:Cap-go/capgo-skillsinskills/capgo-cli-usageat commit2cfb277

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal