/cloudbase-cli

name: cloudbase-cli
description: CloudBase CLI (tcb, 云开发CLI, Tencent CloudBase命令行) resource management skill. Use when deploying cloud functions, CloudRun, storage, NoSQL/MySQL, static hosting, permissions, CORS/domains via tcb; for CI/CD and batch ops; when the user prefers CLI; or as the first-session fallback when CloudBase MCP tools are not loaded yet (after install/config, before IDE restart). Also covers tcb login and site switching (国内站/国际站 via --intl or config isIntl), environment lifecycle (env create/modify/renew/delete/apikey/login/domain), tcb config and cloudbaserc.json sync, log search (logs search, CLS), metric monitoring (monitor), data model and PostgreSQL migrations (db model, db pg migration), sandbox/agent/integration management — do not default to tcb deploy.
version: 2.37.6
license: MIT
alwaysApply: false

CloudBase CLI

Manage CloudBase resources via `tcb` CLI — deterministic, scriptable, auditable. Primary interface for CI/CD and batch ops; **also the first-session fallback** when MCP tools are not yet available in the conversation.

Sibling skills (local only)

Sibling CloudBase skills ship beside this skill. Use local relative paths such as `../auth-tool-cloudbase/SKILL.md`.

If a referenced sibling skill file is missing from this environment, ask the user to install the full CloudBase plugin (or the missing skill). Do **not** HTTP-fetch remote skill or protocol markdown into the agent context.

**Cross-cutting protocols** (required before code changes or deployments):

• Change Safety Protocol: `../cloudbase-platform/references/protocols/change-safety-protocol.md`
• Deployment Gate: `../cloudbase-platform/references/protocols/deployment-gate.md`
• MCP vs CLI fallback: `../cloudbase/references/tooling-fallback.md` (packaged beside this skill as the `cloudbase` entry guideline)

**Route, do not improvise** — when a task belongs to another skill, hand over instead of guessing flags here:

• PostgreSQL schema / RLS / `pgstore` → `../postgresql-development-cloudbase/SKILL.md`
• Data-model design (ER / Mermaid) → `../postgresql-development-cloudbase/SKILL.md`
• In-app SDK code (web / miniprogram / node) → the matching SDK skill

Core Principles

1. **`--help` first — but its failure does NOT mean the command is missing.** Run `tcb <command> --help` to check parameters and find official doc links. On current CLI versions many **second-level** commands reject `--help` (`error: unknown option '--help'`), while some accept `-h`, and `tcb help <cmd>` only works one level deep. Try `-h`, then `tcb help <cmd>`, then `tcb docs search "<keyword>"` — never conclude a command does not exist from a help error. `tcb --help` itself is a **hand-maintained static list**, so absence from it says nothing about lifecycle: `init`, `pull`, `new`, `open`, `rollback`, `self-update`, `monitor`, `integration`, `service`, `cloudfunction`, `cloudrunfunction` and `run:deprecated` are all registered yet unlisted. **Absence from help ≠ deprecated**, and **"no marker" ≠ endorsed** — the statuses differ: `tcb monitor` / `tcb integration` are **officially supported** (recommend normally), while `tcb service` and `tcb cloudfunction` / `tcb cloudrunfunction` are **not recommended** (product decision, no code marker). Full status table: `references/core.md`.

2. **Confirm the site (国内站 / 国际站) as well as the envId.** A credential from one site does not work on the other, and the failure looks like an auth error. One-off: `tcb login --intl true|false`; persistent: `tcb config set isIntl true|false`. Pick one mechanism and keep it consistent — see `references/core.md` / `references/config.md`.

3. **Deployment Gate.** Before any deployment, publish, custom domain, or CloudRun operation, you must first complete the checks in `cloudbase-platform/references/protocols/deployment-gate.md`.

4. **Verify your work.** After deploying or modifying any resource, run the corresponding list/detail command to confirm the change took effect.

5. **Dry-run before destructive actions.** Use `--dry-run` for delete/overwrite operations. Show the preview to the user and wait for explicit confirmation before executing.

6. **Confirm environment first.** Always verify envId with the user before operations. Run `tcb env use <envId>` to avoid accidentally modifying production.

7. **Recover from errors, don't loop.** If a command fails after 2-3 attempts, check the exit code (`$?`), read the error message, consult `tcb docs search`, and try a different approach.

8. **First-session fallback, not MCP replacement.** If CloudBase MCP tools are missing in this session, use this skill to unblock login/manage. Still configure MCP (plugin / mcp.json) so the **next** session can prefer MCP. When MCP tools are already available, prefer MCP unless the user asked for CLI/CI. Route deploy work through the domain reference table below — **do not** recommend `tcb deploy`.

9. **No npm/npx.** If Node/npm/npx are missing, tell the user to install Node.js LTS (or use the IDE marketplace MCP path) before retrying CLI/plugin install. See guideline `tooling-fallback.md`.

When to use this skill

Use when the user wants to manage CloudBase resources via command line, **or** when MCP is not usable yet:

• **First session / post-install:** MCP not in the tool list, or just configured and needs restart → `tcb login` + the matching domain command now; leave MCP ready for next session
• Deploy/debug cloud functions, static hosting, CloudRun services (via domain refs — not `tcb deploy`)
• Manage storage, hosting, databases (NoSQL / MySQL / PostgreSQL), data models and migrations
• Manage environments (create / package / renew / destroy, API Keys, login policy, safe domains, usage)
• Configure resource authorization (`tcb policy`), roles, users, CORS, domains, routing
• Search logs and read monitoring metrics
• Manage sandbox, agent and integration