Capgo Organization Management

When you need to manage Capgo organizations without touching OTA uploads or builds, this handles the admin side: listing orgs, checking members, and tweaking security settings like 2FA enforcement or API key expiration. It's basically a wrapper around the Capgo CLI organization commands with guardrails to prevent you from locking people out. The guidance is careful about checking member status before flipping security switches, which is the right instinct for any multi-tenant setup. If you're doing Capgo work and the task involves the word "organization" but not "deploy," this is the one to reach for.

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

View on GitHub

Install

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

Installs into .claude/skills of the current project.

Files

Capgo Organization Management

Administer Capgo accounts and organizations safely from the CLI.

Facts below were checked against @capgo/cli 8.77 (October 2026). All commands accept -a, --apikey.

When to Use

TRIGGER when:

The user needs their Capgo account ID or email for support (account whoami).
The user lists, creates, renames, or deletes organizations.
The user audits members or 2FA status, or enforces 2FA, a password policy, API-key expiration, or hashed API keys.
The user needs to know which org owns an app (app list --show-org --show-org-id).
A command fails with an org-level 2FA or permission error.

Do not use when:

The work is bundles, channels, or rollouts. Use capgo-release-management.
The user needs native cloud builds. Use capgo-native-builds.
The user wants an agent connected to the Capgo account (MCP). Use capgo-cli-usage.