zcodium-project/zcodium-community-famous-plugins-and-skills/cloudbase-cli

CloudBase CLI

Manage CloudBase resources via tcb CLI — deterministic, scriptable, auditable. The preferred interface for AI agents in CI/CD, batch operations, and resource management.

Standalone Install Note

If this environment only installed the current skill, start from the CloudBase main entry and use the published cloudbase/references/... paths for sibling skills.

• CloudBase main entry: https://cnb.cool/tencent/cloud/cloudbase/cloudbase-skills/-/git/raw/main/skills/cloudbase/SKILL.md
• Current skill raw source: https://cnb.cool/tencent/cloud/cloudbase/cloudbase-skills/-/git/raw/main/skills/cloudbase/references/cloudbase-cli/SKILL.md

Keep local references/... paths for files that ship with the current skill directory. When this file points to a sibling skill such as cloud-functions or cloudrun-development, use the standalone fallback URL shown next to that reference.

Cross-cutting protocols (load for deployment and change operations):

• Change Safety Protocol: https://cnb.cool/tencent/cloud/cloudbase/cloudbase-skills/-/git/raw/main/skills/cloudbase/references/cloudbase-platform/references/protocols/change-safety-protocol.md
• Deployment Gate: https://cnb.cool/tencent/cloud/cloudbase/cloudbase-skills/-/git/raw/main/skills/cloudbase/references/cloudbase-platform/references/protocols/deployment-gate.md

Core Principles

1. `--help` first — never guess commands.

tcb CLI changes between versions. Before using any command for the first time, run tcb <command> --help to check parameters and discover official doc links.

1. 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.

1. Verify your work.

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

1. 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.

1. Confirm environment first.

Always verify envId with the user before operations. Run tcb env use <envId> to avoid accidentally modifying production.

1. 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.

When to use this skill

Use when the user wants to manage CloudBase resources via command line:

• Deploy/debug cloud functions, web apps, CloudRun services
• Manage storage, hosting, databases (NoSQL/MySQL)
• Configure permissions, CORS, domains, routing
• CI/CD scripting, batch operations, terminal-based resource management

Do NOT use for

• SDK-based in-app integration (web/miniprogram/node) → use cloud-functions,

no-sql-web-sdk, auth-web, etc.

• MCP tool calls for IDE-integrated workflows → use CloudBase MCP directly
• Console UI operations
• CloudBase Agent SDK development → use cloudbase-agent-ts

How to use this skill (for a coding agent)

1. Always load `references/core.md` first — it covers authentication,

environment switching, tcb docs queries, and error diagnosis.

1. Route to the correct domain reference using the Routing table below.
2. Load only the one reference file that matches the user's task.

Do not preload all references.

1. Stop loading more context once you have the workflow and command

syntax for the current task.

1. If the task shifts to SDK/in-app code, switch to the appropriate

SDK skill (e.g., cloud-functions, no-sql-web-sdk) instead.

Routing

Quick workflow

1. tcb login → confirm envId with user → tcb env use <envId>
2. tcb <command> --help to verify syntax
3. Execute the command (with --dry-run for destructive ops)
4. Verify the result with the corresponding list / detail command
5. Report the outcome to the user

Minimum self-check

• [ ] Loaded references/core.md before any domain module?
• [ ] Confirmed target envId with the user?
• [ ] Used --help for unfamiliar commands?
• [ ] Used --dry-run before destructive operations?
• [ ] Verified the result after each operation?
• [ ] Stayed within CLI scope — did not drift into SDK code?