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
--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.
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.
Verify your work.
After deploying or modifying any resource, run the corresponding list/detail
command to confirm the change took effect.
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.
Confirm environment first.
Always verify envId with the user before operations. Run tcb env use <envId>
to avoid accidentally modifying production.
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)
- Always load
references/core.md first — it covers authentication,
environment switching, tcb docs queries, and error diagnosis.
- Route to the correct domain reference using the Routing table below.
- Load only the one reference file that matches the user's task.
Do not preload all references.
- Stop loading more context once you have the workflow and command
syntax for the current task.
- 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
| User Task |
Read |
| Login, env switching, tcb docs, error diagnosis |
references/core.md |
| Deploy/debug cloud functions |
references/functions.md |
| Deploy web app (React/Vue/Next.js) |
references/app.md |
| Deploy CloudRun service |
references/cloudrun.md |
| Deploy static site |
references/hosting.md |
| Upload/download files, ACL rules |
references/storage.md |
| NoSQL (MongoDB) database operations |
references/nosql.md |
| MySQL database operations |
references/mysql.md |
| Roles, policies, access control |
references/permission.md |
| CORS, custom domains, routing rules |
references/access.md |
Quick workflow
tcb login → confirm envId with user → tcb env use <envId>tcb <command> --help to verify syntax- Execute the command (with
--dry-run for destructive ops)
- Verify the result with the corresponding
list / detail command
- Report the outcome to the user
Minimum self-check
1---
2name: cloudbase-cli
3description: CloudBase CLI (tcb, 云开发CLI, Tencent CloudBase命令行) resource management skill. This skill should be used when users need to deploy cloud functions, manage CloudRun apps, upload files to storage, query NoSQL/MySQL databases, deploy static hosting, set access permissions, or configure CORS/domains/routing via tcb commands. Also use for CI/CD pipeline scripting, batch operations, terminal-based CloudBase management, or when the user prefers CLI over SDK/MCP.
4version: 2.23.8
5alwaysApply: false
6---
7
8# CloudBase CLI
9
10Manage CloudBase resources via `tcb` CLI — deterministic, scriptable, auditable.
11The preferred interface for AI agents in CI/CD, batch operations, and resource management.
12
13## Standalone Install Note
14
15If this environment only installed the current skill, start from the CloudBase main entry and use the published `cloudbase/references/...` paths for sibling skills.
16
17- CloudBase main entry: `https://cnb.cool/tencent/cloud/cloudbase/cloudbase-skills/-/git/raw/main/skills/cloudbase/SKILL.md`
18- Current skill raw source: `https://cnb.cool/tencent/cloud/cloudbase/cloudbase-skills/-/git/raw/main/skills/cloudbase/references/cloudbase-cli/SKILL.md`
19
20Keep 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.
21
22**Cross-cutting protocols** (load for deployment and change operations):
23- 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`
24- Deployment Gate: `https://cnb.cool/tencent/cloud/cloudbase/cloudbase-skills/-/git/raw/main/skills/cloudbase/references/cloudbase-platform/references/protocols/deployment-gate.md`
25
26## Core Principles
27
281. **`--help` first — never guess commands.**
29 tcb CLI changes between versions. Before using any command for the first time,
30 run `tcb <command> --help` to check parameters and discover official doc links.
31
322. **Deployment Gate.**
33 Before any deployment, publish, custom domain, or CloudRun operation, you must first complete the checks in `cloudbase-platform/references/protocols/deployment-gate.md`.
34
353. **Verify your work.**
36 After deploying or modifying any resource, run the corresponding list/detail
37 command to confirm the change took effect.
38
393. **Dry-run before destructive actions.**
40 Use `--dry-run` for delete/overwrite operations. Show the preview to the user
41 and wait for explicit confirmation before executing.
42
434. **Confirm environment first.**
44 Always verify envId with the user before operations. Run `tcb env use <envId>`
45 to avoid accidentally modifying production.
46
475. **Recover from errors, don't loop.**
48 If a command fails after 2-3 attempts, check the exit code (`$?`), read the
49 error message, consult `tcb docs search`, and try a different approach.
50
51## When to use this skill
52
53Use when the user wants to manage CloudBase resources via command line:
54- Deploy/debug cloud functions, web apps, CloudRun services
55- Manage storage, hosting, databases (NoSQL/MySQL)
56- Configure permissions, CORS, domains, routing
57- CI/CD scripting, batch operations, terminal-based resource management
58
59## Do NOT use for
60
61- SDK-based in-app integration (web/miniprogram/node) → use `cloud-functions`,
62 `no-sql-web-sdk`, `auth-web`, etc.
63- MCP tool calls for IDE-integrated workflows → use CloudBase MCP directly
64- Console UI operations
65- CloudBase Agent SDK development → use `cloudbase-agent-ts`
66
67## How to use this skill (for a coding agent)
68
691. **Always load `references/core.md` first** — it covers authentication,
70 environment switching, `tcb docs` queries, and error diagnosis.
712. **Route to the correct domain reference** using the Routing table below.
723. **Load only the one reference file** that matches the user's task.
73 Do not preload all references.
744. **Stop loading more context** once you have the workflow and command
75 syntax for the current task.
765. **If the task shifts to SDK/in-app code**, switch to the appropriate
77 SDK skill (e.g., `cloud-functions`, `no-sql-web-sdk`) instead.
78
79## Routing
80
81| User Task | Read |
82|-----------|------|
83| Login, env switching, tcb docs, error diagnosis | `references/core.md` |
84| Deploy/debug cloud functions | `references/functions.md` |
85| Deploy web app (React/Vue/Next.js) | `references/app.md` |
86| Deploy CloudRun service | `references/cloudrun.md` |
87| Deploy static site | `references/hosting.md` |
88| Upload/download files, ACL rules | `references/storage.md` |
89| NoSQL (MongoDB) database operations | `references/nosql.md` |
90| MySQL database operations | `references/mysql.md` |
91| Roles, policies, access control | `references/permission.md` |
92| CORS, custom domains, routing rules | `references/access.md` |
93
94## Quick workflow
95
961. `tcb login` → confirm envId with user → `tcb env use <envId>`
972. `tcb <command> --help` to verify syntax
983. Execute the command (with `--dry-run` for destructive ops)
994. Verify the result with the corresponding `list` / `detail` command
1005. Report the outcome to the user
101
102## Minimum self-check
103
104- [ ] Loaded `references/core.md` before any domain module?
105- [ ] Confirmed target envId with the user?
106- [ ] Used `--help` for unfamiliar commands?
107- [ ] Used `--dry-run` before destructive operations?
108- [ ] Verified the result after each operation?
109- [ ] Stayed within CLI scope — did not drift into SDK code?
aiskillstore