cloudbase-cli skill
✓ VerifiedManage Tencent CloudBase resources including cloud functions, storage, databases, and hosting via the tcb command line interface.
- GitHub stars
- 1,164
- Files
- 21
- Last commit
- Nov 11, 2026
- License
- MIT
- Allowed tools
- —
What does the cloudbase-cli skill do?
cloudbase-cli manages Tencent CloudBase resources including cloud functions, storage, databases, and hosting via the tcb command line interface.
Summary generated from the skill's SKILL.md.
About the cloudbase-cli skill
Managing Tencent CloudBase resources through a command line interface is what this skill enables for developers and DevOps engineers. It provides a deterministic and scriptable way to handle cloud functions, CloudRun services, storage, and various database types including NoSQL, MySQL, and PostgreSQL. The skill is particularly useful for executing batch operations, setting up CI/CD pipelines, or acting as a fallback when specialized MCP tools are not yet configured in a session.
Users interact with the tcb command to perform tasks such as environment lifecycle management, log searching via CLS, and metric monitoring. It handles complex configurations like CORS, custom domains, and resource permissions through tcb policy. To ensure safety, the skill encourages using the --dry-run flag for destructive actions and requires verifying the environment ID and site type, such as the international or domestic versions, before executing commands. It relies on a structured set of reference files to guide command syntax and error diagnosis.
What an agent can do with it
- 1Automate cloud resource deploymentA developer can use this skill to integrate cloud function and static hosting deployments into a CI/CD pipeline.
- 2Monitor system healthAn engineer can search through service logs and check performance metrics for cloud functions or databases.
- 3Configure environment settingsUsers can switch between domestic and international sites or manage different environment lifecycles.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the cloudbase-cli skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the cloudbase-cli skill in Claude Code
~/.claude/skills/cloudbase-cli/SKILL.md
$ npx degit TencentCloudBase/CloudBase-AI-Toolkit/config/.claude/skills/cloudbase-cli ~/.claude/skills/cloudbase-cliInstall the cloudbase-cli skill in Claude Code (project)
.claude/skills/cloudbase-cli/SKILL.md
$ npx degit TencentCloudBase/CloudBase-AI-Toolkit/config/.claude/skills/cloudbase-cli .claude/skills/cloudbase-cliInstall the cloudbase-cli skill in Codex
~/.agents/skills/cloudbase-cli/SKILL.md
$ npx degit TencentCloudBase/CloudBase-AI-Toolkit/config/.claude/skills/cloudbase-cli ~/.agents/skills/cloudbase-cliInstall the cloudbase-cli skill in Gemini CLI
~/.gemini/skills/cloudbase-cli/SKILL.md
$ npx degit TencentCloudBase/CloudBase-AI-Toolkit/config/.claude/skills/cloudbase-cli ~/.gemini/skills/cloudbase-cliInstall the cloudbase-cli skill in Claude.ai
npx degit TencentCloudBase/CloudBase-AI-Toolkit/config/.claude/skills/cloudbase-cli cloudbase-cli && zip -r cloudbase-cli.zip cloudbase-cli # claude.ai → Customize → Skills → + → Create skill → Upload a skill → cloudbase-cli.zip
Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work
- Source repository linked and reachabletencentcloudbase/cloudbase-ai-toolkit/config/.claude/skills/cloudbase-cli is public and reachablegithub.com/tencentcloudbase/cloudbase-ai-toolkit/tree/HEAD/c ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-11-11github.com/tencentcloudbase/cloudbase-ai-toolkit/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/tencentcloudbase/cloudbase-ai-toolkit/blob/HEAD/c ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/tencentcloudbase/cloudbase-ai-toolkit/blob/HEAD/c ↗Pass
- SKILL.md follows the Agent Skills formatValid name and description; says when to use it; 181 linesgithub.com/tencentcloudbase/cloudbase-ai-toolkit/blob/HEAD/c ↗Pass
SKILL.md
View on GitHubCloudBase 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 thecloudbaseentry 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
-
--helpfirst — but its failure does NOT mean the command is missing. Runtcb <command> --helpto 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, andtcb help <cmd>only works one level deep. Try-h, thentcb help <cmd>, thentcb docs search "<keyword>"— never conclude a command does not exist from a help error.tcb --helpitself 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,cloudrunfunctionandrun:deprecatedare all registered yet unlisted. Absence from help ≠ deprecated, and "no marker" ≠ endorsed — the statuses differ:tcb monitor/tcb integrationare officially supported (recommend normally), whiletcb serviceandtcb cloudfunction/tcb cloudrunfunctionare not recommended (product decision, no code marker). Full status table:references/core.md. -
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 — seereferences/core.md/references/config.md. -
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-runfor 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, consulttcb 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 / 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 instances
- 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. - PostgreSQL schema design, RLS and migration workflow →
postgresql-development-cloudbase - 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.mdfirst — it covers authentication, site selection, environment switching,tcb docsqueries, and error diagnosis. - Route to the correct reference using the Routing table below.
- Load only the reference files that match the user's task. Do not preload all of them.
- 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 or PostgreSQL design, switch to the appropriate sibling skill instead.
Routing
| User Task | Read |
|---|---|
Login, site (国际站/国内站), env switching, tcb docs, error diagnosis |
references/core.md |
| Create / modify / renew / destroy an environment, API Keys, login policy, safe domains, usage | references/env.md |
tcb config (CLI settings, cloudbaserc.json sync), tcb init / new / pull / open / validate / self-update / rollback |
references/config.md |
Configure an AI tool + MCP + Skills (tcb ai) |
references/config.md |
| Deploy/debug cloud functions, versions, provisioned concurrency, layers, triggers | references/functions.md |
| Deploy static site / SPA (preferred CLI web path) | references/hosting.md |
| Deploy CloudRun service, traffic/canary, versions, build & runtime logs | references/cloudrun.md |
Experimental all-in-one web shorthand (tcb deploy, tcb app build) — avoid unless the user asks |
references/app.md |
| Upload/download files, ACL rules, COS vs PG object storage | references/storage.md |
| NoSQL (MongoDB) database operations, collection dump | references/nosql.md |
| MySQL instance, SQL execution, backups, slow queries | references/mysql.md |
Data model definitions, sync-model-dts, PostgreSQL migrations |
references/schema.md |
| Search logs (CLS: functions / CloudRun / database / auth / LLM / gateway) | references/logs.md |
| Metric monitoring (functions, CloudRun, DB, hosting, auth, gateway…) | references/monitor.md |
Resource authorization (tcb policy), roles, users |
references/permission.md |
CORS, custom domains, CDN cache purge, routing rules (tcb routes) |
references/access.md |
tcb service (HTTP 访问服务) — ⚠️ not recommended; read access.md for the routes/domains equivalent |
references/access.md |
WeDa / 微搭 low-code apps and components (tcb lowcode) |
references/lowcode.md |
| Sandbox tools / instances / API keys | references/sandbox.md |
| Agent create / update / delete | references/agent.md |
| Integration instances (types, create, bind, delete) | references/integration.md |
| PostgreSQL schema / RLS / migration workflow (not just the CLI flags) | ../postgresql-development-cloudbase/SKILL.md |
Quick workflow
tcb login(check the site) → confirm envId with the user →tcb env use <envId>- Look up the command in the matching reference; verify syntax with
tcb <command> --help(or-h) - Execute the command (with
--dry-runfor destructive ops) - Verify the result with the corresponding
list/detailcommand - Report the outcome to the user
Minimum self-check
- Loaded
references/core.mdbefore any domain module? - Confirmed the site (
isIntl) and the target envId with the user? - Checked that
--helpfailure was not misread as "command missing"? - Used
--dry-runbefore destructive operations? - For PG environments: switched to the PostgreSQL skill instead of reusing NoSQL/MySQL paths?
- Verified the result after each operation?
- Stayed within CLI scope — did not drift into SDK code?
Reference index
All packaged reference files (required for skill lint reachability):
Files in this skill
21cloudbase-cli skill questions
How do I install the cloudbase-cli skill in Claude Code?
Run npx degit TencentCloudBase/CloudBase-AI-Toolkit/config/.claude/skills/cloudbase-cli ~/.claude/skills/cloudbase-cli. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the cloudbase-cli skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
How do I switch between the China and International sites?
You can switch sites using the --intl flag during login or by setting the persistent configuration with 'tcb config set isIntl true|false'.
What should I do if a command returns an error when using --help?
Do not assume the command is missing; some second-level commands reject --help. Try using -h, 'tcb help <cmd>', or 'tcb docs search'.
Is it safe to run destructive commands immediately?
No, you should use the --dry-run flag for delete or overwrite operations to preview changes and wait for user confirmation.