- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill cloudbase-cli -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill cloudbase-cli -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill cloudbase-cli -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill cloudbase-cli -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/TencentCloudBase/CloudBase-AI-Toolkit/tree/HEAD/config/.claude/skills/cloudbase-cliFrom the publisher
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 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):
../cloudbase-platform/references/protocols/change-safety-protocol.md../cloudbase-platform/references/protocols/deployment-gate.md../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:
pgstore → ../postgresql-development-cloudbase/SKILL.md../postgresql-development-cloudbase/SKILL.md--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 --without-template, 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.
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.
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.
Use when the user wants to manage CloudBase resources via command line, or when MCP is not usable yet:
tcb login + the matching domain command now; leave MCP ready for next sessiontcb deploy)tcb policy), roles, users, CORS, domains, routingcloud-functions,
cloudbase-document-database-web-sdk, auth-web-cloudbase, etc.postgresql-development-cloudbasecloudbase-agent-tsreferences/core.md first — it covers authentication, site selection,
environment switching, tcb docs queries, and error diagnosis.tcb login (check the site) → confirm envId with the user → tcb env use <envId>tcb <command> --help (or -h)--dry-run for destructive ops)list / detail commandreferences/core.md before any domain module?isIntl) and the target envId with the user?--help failure was not misread as "command missing"?--dry-run before destructive operations?All packaged reference files (required for skill lint reachability):
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
---name: cloudbase-clidescription: CloudBase CLI (tcb, 云开发CLI, Tencent CloudBase命令行) resource management skill. Use when deploying cloud…---# config/.claude/skills/cloudbase-cli/SKILL.mdOverview
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.
FAQ
Download config/.claude/skills/cloudbase-cli/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/TencentCloudBase/CloudBase-AI-Toolkit.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.
tcb routesreferences/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 |