Agent skill · tencentcloudbase
cloudbase-declarative-deploy
CloudBase declarative deployment from a cloudbaserc config (声明式部署, 配置式部署, cloudbaserc 部署) through the deployApply / deployPlan MCP tools. Use when deploying database, functions, app, hosting, or gateway resources described in cloudbaserc.json/yaml as a single desired-state config, when a user wants a dry-run plan before applying, or when handling multi-environment deploys via mode / envOverrides. Covers plan-then-apply flow (deployPlan dry-run → deployApply confirm=true), envId resolution priority, only/skip filtering, concurrency, and continueOnError. Prefer deployPlan before deployApply; do not confuse with per-resource tcb CLI deploy or single-function deploy.
What it needs
About 5k tokens when loaded.
What this skill does
CloudBase Declarative Deploy Deploy a whole CloudBase project from one cloudbaserc config as desired state, using the deployPlan (dry-run) and deployApply (apply) MCP tools. The orchestrator applies resources in a fixed dependency order: Sibling skills (local only) Sibling CloudBase skills ship beside this skill. Use local relative paths such as ../cloudbase-cli/SKILL.md. Cloud-hosted MCP mode does not guarantee access to a local workspace filesystem or stable relative paths. If a referenced sibling file is not available in cloud mode, use this skill's embedded guidance as source of truth and ask the user for any missing constraints (or to install the missing skill). Do not HTTP-fetch remote skill or protocol markdown into the agent context. Cross-cutting protocols (required before applying any deploy): Change Safety Protocol: ../cloudbase-platform/references/protocols/change-safety-protocol.md Deployment Gate: ../cloudbase-platform/references/protocols/deployment-gate.md When to use this skill The project has a cloudbaserc.json / .yaml / .yml / .js describing multiple resources, and the user wants to deploy them together as one config. The user asks for 声明式部署 / 配置式部署 / "deploy from cloudbaserc" / "deploy the whole project". The user wants to preview what a deploy will change before applying (dry-run plan). Multi-environment deploy: production/staging via mode + envOverrides. Do NOT use for Deploying a single cloud function or one static site via tcb CLI → ../cloudbase-cli/SKILL.md. In-app SDK integration (web/miniprogram/node) → the matching SDK skill. Console UI operations. Cloud mode deployPlan / deployApply in this skill are the local-form declarative executor. In cloud-hosted MCP mode these tools are intentionally not registered (filtered at tool registration), because that runtime has no local cwd / filesystem-bound execution path. If you are in cloud mode and do not see deployPlan / deployApply in the tool list, this is expected behavior. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills tencentcloudbase/cloudbase-declarative-deploy