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)
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.
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.
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)
- Configure permissions, CORS, domains, routing
- CI/CD scripting, batch operations, terminal-based resource management
- User explicitly prefers CLI over MCP
Do NOT use for
- SDK-based in-app integration (web/miniprogram/node) → use
cloud-functions,
cloudbase-document-database-web-sdk, auth-web-cloudbase, etc.
- When CloudBase MCP tools are already available in this session and the user did not ask for CLI → prefer MCP
- 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, cloudbase-document-database-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 static site / SPA (preferred CLI web path) |
references/hosting.md |
| Deploy CloudRun service |
references/cloudrun.md |
Experimental all-in-one web shorthand (tcb deploy) — avoid unless user explicitly asks |
references/app.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
Reference index
All packaged reference files (required for skill lint reachability):
- access.md
- app.md
- cloudrun.md
- core.md
- functions.md
- hosting.md
- mysql.md
- nosql.md
- permission.md
- storage.md
1---2name: cloudbase-cli3description: 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). Covers tcb login (device code for Tencent Cloud accounts; --cloudbase-api-key -e for environment API Key without an account; --apiKeyId/--apiKey for CI) and domain commands (fn/hosting/cloudrun/…) as MCP auth/manage parity — do not default to tcb deploy.4---5
6# CloudBase CLI
7
8Manage CloudBase resources via `tcb` CLI — deterministic, scriptable, auditable.
9Primary interface for CI/CD and batch ops; **also the first-session fallback** when MCP tools are not yet available in the conversation.
10
11## Sibling skills (local only)
12
13Sibling CloudBase skills ship beside this skill. Use local relative paths such as `../auth-tool-cloudbase/SKILL.md`.
14
15If 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.
16
17**Cross-cutting protocols** (required before code changes or deployments):
18- Change Safety Protocol: `../cloudbase-platform/references/protocols/change-safety-protocol.md`
19- Deployment Gate: `../cloudbase-platform/references/protocols/deployment-gate.md`
20- MCP vs CLI fallback: `../cloudbase/references/tooling-fallback.md` (packaged beside this skill as the `cloudbase` entry guideline)
21
22## Core Principles
23
241. **`--help` first — never guess commands.**
25 tcb CLI changes between versions. Before using any command for the first time,
26 run `tcb <command> --help` to check parameters and discover official doc links.
27
282. **Deployment Gate.**
29 Before any deployment, publish, custom domain, or CloudRun operation, you must first complete the checks in `cloudbase-platform/references/protocols/deployment-gate.md`.
30
313. **Verify your work.**
32 After deploying or modifying any resource, run the corresponding list/detail
33 command to confirm the change took effect.
34
353. **Dry-run before destructive actions.**
36 Use `--dry-run` for delete/overwrite operations. Show the preview to the user
37 and wait for explicit confirmation before executing.
38
394. **Confirm environment first.**
40 Always verify envId with the user before operations. Run `tcb env use <envId>`
41 to avoid accidentally modifying production.
42
435. **Recover from errors, don't loop.**
44 If a command fails after 2-3 attempts, check the exit code (`$?`), read the
45 error message, consult `tcb docs search`, and try a different approach.
46
476. **First-session fallback, not MCP replacement.**
48 If CloudBase MCP tools are missing in this session, use this skill to unblock
49 login/manage. Still configure MCP (plugin / mcp.json) so the **next** session
50 can prefer MCP. When MCP tools are already available, prefer MCP unless the
51 user asked for CLI/CI. Route deploy work through the domain reference table
52 below — **do not** recommend `tcb deploy`.
53
547. **No npm/npx.**
55 If Node/npm/npx are missing, tell the user to install Node.js LTS (or use the
56 IDE marketplace MCP path) before retrying CLI/plugin install. See guideline
57 `tooling-fallback.md`.
58
59## When to use this skill
60
61Use when the user wants to manage CloudBase resources via command line, **or** when MCP is not usable yet:
62- **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
63- Deploy/debug cloud functions, static hosting, CloudRun services (via domain refs — not `tcb deploy`)
64- Manage storage, hosting, databases (NoSQL/MySQL)
65- Configure permissions, CORS, domains, routing
66- CI/CD scripting, batch operations, terminal-based resource management
67- User explicitly prefers CLI over MCP
68
69## Do NOT use for
70
71- SDK-based in-app integration (web/miniprogram/node) → use `cloud-functions`,
72 `cloudbase-document-database-web-sdk`, `auth-web-cloudbase`, etc.
73- When CloudBase MCP tools are already available in this session and the user did not ask for CLI → prefer MCP
74- Console UI operations
75- CloudBase Agent SDK development → use `cloudbase-agent-ts`
76
77## How to use this skill (for a coding agent)
78
791. **Always load `references/core.md` first** — it covers authentication,
80 environment switching, `tcb docs` queries, and error diagnosis.
812. **Route to the correct domain reference** using the Routing table below.
823. **Load only the one reference file** that matches the user's task.
83 Do not preload all references.
844. **Stop loading more context** once you have the workflow and command
85 syntax for the current task.
865. **If the task shifts to SDK/in-app code**, switch to the appropriate
87 SDK skill (e.g., `cloud-functions`, `cloudbase-document-database-web-sdk`) instead.
88
89## Routing
90
91| User Task | Read |
92|-----------|------|
93| Login, env switching, tcb docs, error diagnosis | `references/core.md` |
94| Deploy/debug cloud functions | `references/functions.md` |
95| Deploy static site / SPA (preferred CLI web path) | `references/hosting.md` |
96| Deploy CloudRun service | `references/cloudrun.md` |
97| Experimental all-in-one web shorthand (`tcb deploy`) — avoid unless user explicitly asks | `references/app.md` |
98| Upload/download files, ACL rules | `references/storage.md` |
99| NoSQL (MongoDB) database operations | `references/nosql.md` |
100| MySQL database operations | `references/mysql.md` |
101| Roles, policies, access control | `references/permission.md` |
102| CORS, custom domains, routing rules | `references/access.md` |
103
104## Quick workflow
105
1061. `tcb login` → confirm envId with user → `tcb env use <envId>`
1072. `tcb <command> --help` to verify syntax
1083. Execute the command (with `--dry-run` for destructive ops)
1094. Verify the result with the corresponding `list` / `detail` command
1105. Report the outcome to the user
111
112## Minimum self-check
113
114- [ ] Loaded `references/core.md` before any domain module?
115- [ ] Confirmed target envId with the user?
116- [ ] Used `--help` for unfamiliar commands?
117- [ ] Used `--dry-run` before destructive operations?
118- [ ] Verified the result after each operation?
119- [ ] Stayed within CLI scope — did not drift into SDK code?
120
121## Reference index
122
123All packaged reference files (required for skill lint reachability):
124
125- [access.md](references/access.md)
126- [app.md](references/app.md)
127- [cloudrun.md](references/cloudrun.md)
128- [core.md](references/core.md)
129- [functions.md](references/functions.md)
130- [hosting.md](references/hosting.md)
131- [mysql.md](references/mysql.md)
132- [nosql.md](references/nosql.md)
133- [permission.md](references/permission.md)
134- [storage.md](references/storage.md)
infometa