[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79GQQS6DVC4SFEXAKSD0XFD":3,"skill-same:01M79GQQS6DVC4SFEXAKSD0XFD":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M79GQQS6DVC4SFEXAKSD0XFD","cloudbase-declarative-deploy",null,"CloudBase declarative deployment from a cloudbaserc config (声明式部署, 配置式部署, cloudbaserc 部署) through the deployBuild \u002F deployPlan \u002F deployApply MCP tools. Use when deploying database, functions, app, hosting, or gateway resources described in cloudbaserc.json\u002Fyaml as a single desired-state config, when a user wants to build static hosting artifacts locally first (deployBuild), or wants a dry-run plan before applying (deployPlan), or when handling multi-environment deploys via mode \u002F envOverrides. Covers build-plan-apply flow (deployBuild local build → deployPlan dry-run → deployApply confirm=true), hosting build-output neutralization, envId resolution priority, only\u002Fskip filtering, concurrency, and continueOnError. Prefer deployBuild (when hosting declares a buildCommand) and deployPlan before deployApply; do not confuse with per-resource tcb CLI deploy or single-function deploy.","infometa\u002Fworkbuddyskills","infometa","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F109397516?v=4","01M79FS3XQK361MJFWQ2GFK95C","01M79FS3YPWKZYW9EPAAP2BFBJ",447,"MIT","https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fconnectors\u002Fcloudbase\u002Fskills\u002Freferences\u002Fcloudbase-declarative-deploy\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cloudbase-declarative-deploy\ndescription: CloudBase declarative deployment from a cloudbaserc config (声明式部署, 配置式部署, cloudbaserc 部署) through the deployBuild \u002F deployPlan \u002F deployApply MCP tools. Use when deploying database, functions, app, hosting, or gateway resources described in cloudbaserc.json\u002Fyaml as a single desired-state config, when a user wants to build static hosting artifacts locally first (deployBuild), or wants a dry-run plan before applying (deployPlan), or when handling multi-environment deploys via mode \u002F envOverrides. Covers build-plan-apply flow (deployBuild local build → deployPlan dry-run → deployApply confirm=true), hosting build-output neutralization, envId resolution priority, only\u002Fskip filtering, concurrency, and continueOnError. Prefer deployBuild (when hosting declares a buildCommand) and deployPlan before deployApply; do not confuse with per-resource tcb CLI deploy or single-function deploy.\nversion: 2.36.2\nlicense: MIT\nalwaysApply: false\n---\n\n# CloudBase Declarative Deploy\n\nDeploy a whole CloudBase project from one `cloudbaserc` config as **desired state**,\nusing the `deployBuild` (local hosting build), `deployPlan` (dry-run) and `deployApply`\n(apply) MCP tools. The orchestrator applies resources in a fixed dependency order:\n\n```\ndatabase → functions → app → hosting → gateway\n```\n\n## Sibling skills (local only)\n\nSibling CloudBase skills ship beside this skill. Use local relative paths such as\n`..\u002Fcloudbase-cli\u002FSKILL.md`.\n\nCloud-hosted MCP mode does not guarantee access to a local workspace filesystem or\nstable relative paths. If a referenced sibling file is not available in cloud mode,\nuse this skill's embedded guidance as source of truth and ask the user for any\nmissing constraints (or to install the missing skill). Do **not** HTTP-fetch remote skill or protocol markdown into the agent context.\n\n**Cross-cutting protocols** (required before applying any deploy):\n- Change Safety Protocol: `..\u002Fcloudbase-platform\u002Freferences\u002Fprotocols\u002Fchange-safety-protocol.md`\n- Deployment Gate: `..\u002Fcloudbase-platform\u002Freferences\u002Fprotocols\u002Fdeployment-gate.md`\n\n## When to use this skill\n\n- The project has a `cloudbaserc.json` \u002F `.yaml` \u002F `.yml` \u002F `.js` describing multiple\n  resources, and the user wants to deploy them together as one config.\n- The user asks for 声明式部署 \u002F 配置式部署 \u002F \"deploy from cloudbaserc\" \u002F \"deploy the whole project\".\n- The user wants to preview what a deploy will change before applying (dry-run plan).\n- The user wants to build the static hosting artifact locally first (declarative\n  hosting deploys no longer build implicitly — see `deployBuild`).\n- Multi-environment deploy: production\u002Fstaging via `mode` + `envOverrides`.\n\n## Do NOT use for\n\n- Deploying a single cloud function or one static site via `tcb` CLI → `..\u002Fcloudbase-cli\u002FSKILL.md`.\n- In-app SDK integration (web\u002Fminiprogram\u002Fnode) → the matching SDK skill.\n- Console UI operations.\n\n## Cloud mode: deploy through the two-step upload channel\n\n`deployBuild` \u002F `deployPlan` \u002F `deployApply` in this skill are the **local-form declarative\nexecutor**. In cloud-hosted MCP mode they are intentionally not registered, because that\nruntime has no local `cwd` and no filesystem-bound execution path.\n\nThis is an **execution-channel switch, not a capability gap**. Everything still deploys, but\nthe artifact is uploaded first and the build runs in the cloud. If those three tools are\nmissing from the tool list, that is expected — pick the channel that matches the resource.\n\n### Cloud functions — two-phase zip\n\n1. `queryFunctions(action=getFunctionUploadUrl, functionName?)` returns `uploadUrl`,\n   `uploadHeaders`, `cosBucketName`, `cosBucketRegion`, `cosObjectName`, `expiresInSeconds`\n2. `PUT` the function zip to `uploadUrl` with `uploadHeaders`\n3. `manageFunctions(action=createFunction|updateFunctionCode, code={cosBucketName,\n   cosObjectName, cosBucketRegion?})` — phase B deploys from the environment's own COS bucket\n   (`deployMode=cos`); pass the triple through unchanged, the schema is strict\n\n`contentPath` (a local directory) is rejected in cloud mode. For layer contents use\n`base64Content`; for code use the two-phase path above.\n\n### CloudApp — two-step upload plus a cloud pipeline\n\n1. `queryApps(action=getUploadUrl, serviceName=...)` returns `uploadUrl`, `uploadHeaders`,\n   `unixTimestamp`\n2. Upload the source\u002Fbuild zip to `uploadUrl` with the returned headers\n   (`Content-Type: application\u002Fzip`)\n   - Public dependencies resolvable from a lockfile: `package.json` plus lockfile is enough\n   - Private or offline dependencies: package `node_modules` explicitly\n3. `manageApps(action=deployApp, cosTimestamp=\u003CunixTimestamp>, installCmd?, buildCmd?, deployCmd?)`\n   - `installCmd` \u002F `buildCmd` \u002F `deployCmd` are pipeline declarations executed in the cloud\n     container; you pass data and declarations, you do not run local shell commands\n\n### Static hosting — route through CloudApp\n\n`manageHosting(action=upload)` is blocked in cloud mode because it needs a local path.\nDeploy a static site through the CloudApp two-step upload above (upload the prebuilt\nartifact, exclude `node_modules`). Uploading or downloading an already-hosted file has no\nremote substitute and needs local mode. The other hosting actions (`delete`,\n`setWebsiteDocument`, `enableService`, `bindDomain`, `unbindDomain`, `updateDomain`) remain\navailable.\n\n### What cloud mode does not give you\n\n- **No dry-run.** There is no `deployPlan` against a local `cloudbaserc`. Do not claim a plan\n  was generated or reviewed in cloud mode; state what is about to be deployed and what the\n  upload contains. Roadmap: upload `cloudbaserc` as a data artifact, then run server-side\n  plan\u002Fapply orchestration.\n- **No local project context.** `mode` \u002F `envOverrides` resolution from a project file does\n  not apply; pass the target environment explicitly.\n\nFor parameter details, see `references\u002Fplan-and-apply.md` (`Cloud-hosted upload pipeline path`).\n\n## Core principles\n\n1. **Plan before apply — always.**\n   Run `deployPlan` first (dry-run, zero side effects). Read the per-resource action\n   classification and show it to the user before calling `deployApply`.\n\n2. **Apply requires explicit confirm.**\n   `deployApply` will refuse unless `confirm=true` is passed. This is the destructive-write guard.\n\n3. **Deployment Gate.**\n   Before any apply, complete `cloudbase-platform\u002Freferences\u002Fprotocols\u002Fdeployment-gate.md`\n   and present the mandatory declaration.\n\n4. **Conservative on existing resources by default.**\n   `yes` defaults to `false` → existing resources are skipped, not overwritten. Only pass\n   `yes=true` when the user explicitly wants to overwrite\u002Fupdate existing resources.\n\n5. **database failure always aborts.**\n   Even with `continueOnError=true`, a database-stage failure stops the whole deploy,\n   because later resources depend on it.\n\n6. **Resolve envId explicitly.**\n   Never rely on implicit defaults silently — know which environment is targeted (see\n   the priority table below) and confirm it with the user before applying.\n\n## Plan action classification\n\n`deployPlan` returns a list of resource entries. Each `status` means:\n\n| status | meaning |\n|--------|---------|\n| `create` | new resource, will be created |\n| `update` | exists, will be overwritten\u002Fupdated |\n| `skip` | no change needed |\n| `conflict` | conflict detected — deploy will abort, must resolve first |\n| `deploy` | direct overwrite upload |\n\nIf any entry is `conflict`, stop and resolve it before applying.\n\n## envId resolution priority\n\n```\nexplicit envId param  >  cloudbaserc `envId`  >  logged-in \u002F bound environment\n```\n\nIf none can be resolved, the tool errors out. Prefer confirming the resolved envId\nwith the user before applying to production.\n\n## Local workflow (build → plan → apply)\n\nWhen `hosting` declares a `buildCommand`, declarative deploy is a three-step flow —\n`deployApply` no longer runs the local build implicitly:\n\n1. Ensure a `cloudbaserc` config exists under the project root (`cwd`).\n2. **Build first** (only when `hosting` has a `buildCommand`): call\n   `deployBuild({ cwd, mode? })` to produce the local artifacts (builds every hosting\n   item; pure-static items without a build command are skipped automatically).\n   - If the build artifacts are missing at apply time, `deployApply` fails with\n     `BUILD_OUTPUT_NOT_FOUND` and directs you back to this step — call `deployBuild`\n     first, then retry.\n   - `deployBuild` needs no `envId` and no `confirm` (local build only, never touches\n     cloud resources); if dependencies are not installed it fails with\n     `DEPENDENCY_NOT_INSTALLED` and tells you to run install first.\n3. Call `deployPlan` (optionally with `mode`, `envId`, `only`, `skip`). Read the plan.\n4. Present the plan + Deployment Gate declaration to the user; get confirmation.\n5. Call `deployApply` with `confirm=true` (plus `yes` \u002F `concurrency` \u002F `continueOnError`\n   as needed). Reuse the same `mode` \u002F `envId` \u002F `only` \u002F `skip` as the plan.\n   A hosting item with existing build output is uploaded directly (the tool clears\n   the build command and reports `hostingNeutralized: true`); rebuild with `deployBuild`\n   after source changes so the upload is not stale.\n6. Report the applied result back to the user.\n\nFor cloud-hosted MCP mode, do not ask for local `cwd`\u002Ffilesystem reads; use the\n`Cloud mode` upload-channel flow above.\n\n## Build & pipeline execution\n\nUse this mental model: **build → plan → apply**. The build executor depends on resource type.\n\n| resource | typical build executor | deployment path |\n|----------|------------------------|-----------------|\n| `hosting` | `deployBuild` (local shell build, run **before** apply) | `deployApply` uploads the built output directly; missing output → `BUILD_OUTPUT_NOT_FOUND` |\n| `app` (`framework=static`) | local prebuilt artifact | package upload + deploy record |\n| `app` (non-static frameworks) | cloud pipeline | source zip upload + cloud build + deploy |\n| `functions` | local zip \u002F cloud build \u002F image pipeline | depends on `buildStrategy` (`zip`\u002F`cloud`\u002F`local`\u002F`image`) |\n\n`deployBuild` builds every `hosting` item that has a `buildCommand` (framework mapping or\npackage.json auto-detection); it skips pure-static items. Build failures surface as\n`BUILD_FAILED`, missing local dependencies as `DEPENDENCY_NOT_INSTALLED` (run install\nfirst — `deployBuild` never installs dependencies for you).\n\nBuild command resolution follows declaration priority:\n\n`explicit config` > `framework mapping defaults` > `package.json` auto-detection\n\n`buildCommand` \u002F `installCommand` \u002F `deployCmd` are declarative intent in config.\nExecution ownership depends on path:\n\n- local-form paths: specific steps may run in local shell executor\n- cloud-hosted paths: commands are executed by cloud pipeline container (staticCmd),\n  or replaced by prebuilt artifact upload\n\nSo the answer to \"can cloud mode run local CLI commands\" is: execution authority is\nmoved from local shell to cloud pipeline; agent transmits declarations and artifacts.\n\n## Routing\n\n| User task | Read |\n|-----------|------|\n| cloudbaserc resource fields & desired-state config shape | `references\u002Fconfig-schema.md` |\n| deployPlan → deployApply two-step flow, parameters, safety | `references\u002Fplan-and-apply.md` |\n| Multi-env (mode \u002F envOverrides), envId priority, env vars | `references\u002Fmulti-env.md` |\n\n## Minimum self-check\n\n- [ ] Built the hosting artifacts first (`deployBuild`) when `hosting` declares a `buildCommand`?\n- [ ] Ran `deployPlan` and read the action classification before `deployApply`?\n- [ ] Resolved and confirmed the target `envId`?\n- [ ] Completed the Deployment Gate declaration before applying?\n- [ ] Passed `confirm=true` only after user confirmation?\n- [ ] Left `yes=false` unless overwrite of existing resources was explicitly requested?\n- [ ] Handled any `conflict` entries before applying?\n\n## Reference index\n\nAll packaged reference files (required for skill lint reachability):\n\n- [config-schema.md](references\u002Fconfig-schema.md)\n- [plan-and-apply.md](references\u002Fplan-and-apply.md)\n- [multi-env.md](references\u002Fmulti-env.md)\n","# CloudBase Declarative Deploy\n\nDeploy a whole CloudBase project from one `cloudbaserc` config as **desired state**,\nusing the `deployBuild` (local hosting build), `deployPlan` (dry-run) and `deployApply`\n(apply) MCP tools. The orchestrator applies resources in a fixed dependency order:\n\n```\ndatabase → functions → app → hosting → gateway\n```\n\n## Sibling skills (local only)\n\nSibling CloudBase skills ship beside this skill. Use local relative paths such as\n`..\u002Fcloudbase-cli\u002FSKILL.md`.\n\nCloud-hosted MCP mode does not guarantee access to a local workspace filesystem or\nstable relative paths. If a referenced sibling file is not available in cloud mode,\nuse this skill's embedded guidance as source of truth and ask the user for any\nmissing constraints (or to install the missing skill). Do **not** HTTP-fetch remote skill or protocol markdown into the agent context.\n\n**Cross-cutting protocols** (required before applying any deploy):\n- Change Safety Protocol: `..\u002Fcloudbase-platform\u002Freferences\u002Fprotocols\u002Fchange-safety-protocol.md`\n- Deployment Gate: `..\u002Fcloudbase-platform\u002Freferences\u002Fprotocols\u002Fdeployment-gate.md`\n\n## When to use this skill\n\n- The project has a `cloudbaserc.json` \u002F `.yaml` \u002F `.yml` \u002F `.js` describing multiple\n  resources, and the user wants to deploy them together as one config.\n- The user asks for 声明式部署 \u002F 配置式部署 \u002F \"deploy from cloudbaserc\" \u002F \"deploy the whole project\".\n- The user wants to preview what a deploy will change before applying (dry-run plan).\n- The user wants to build the static hosting artifact locally first (declarative\n  hosting deploys no longer build implicitly — see `deployBuild`).\n- Multi-environment deploy: production\u002Fstaging via `mode` + `envOverrides`.\n\n## Do NOT use for\n\n- Deploying a single cloud function or one static site via `tcb` CLI → `..\u002Fcloudbase-cli\u002FSKILL.md`.\n- In-app SDK integration (web\u002Fminiprogram\u002Fnode) → the matching SDK skill.\n- Console UI operations.\n\n## Cloud mode: deploy through the two-step upload channel\n\n`deployBuild` \u002F `deployPlan` \u002F `deployApply` in this skill are the **local-form declarative\nexecutor**. In cloud-hosted MCP mode they are intentionally not registered, because that\nruntime has no local `cwd` and no filesystem-bound execution path.\n\nThis is an **execution-channel switch, not a capability gap**. Everything still deploys, but\nthe artifact is uploaded first and the build runs in the cloud. If those three tools are\nmissing from the tool list, that is expected — pick the channel that matches the resource.\n\n### Cloud functions — two-phase zip\n\n1. `queryFunctions(action=getFunctionUploadUrl, functionName?)` returns `uploadUrl`,\n   `uploadHeaders`, `cosBucketName`, `cosBucketRegion`, `cosObjectName`, `expiresInSeconds`\n2. `PUT` the function zip to `uploadUrl` with `uploadHeaders`\n3. `manageFunctions(action=createFunction|updateFunctionCode, code={cosBucketName,\n   cosObjectName, cosBucketRegion?})` — phase B deploys from the environment's own COS bucket\n   (`deployMode=cos`); pass the triple through unchanged, the schema is strict\n\n`contentPath` (a local directory) is rejected in cloud mode. For layer contents use\n`base64Content`; for code use the two-phase path above.\n\n### CloudApp — two-step upload plus a cloud pipeline\n\n1. `queryApps(action=getUploadUrl, serviceName=...)` returns `uploadUrl`, `uploadHeaders`,\n   `unixTimestamp`\n2. Upload the source\u002Fbuild zip to `uploadUrl` with the returned headers\n   (`Content-Type: application\u002Fzip`)\n   - Public dependencies resolvable from a lockfile: `package.json` plus lockfile is enough\n   - Private or offline dependencies: package `node_modules` explicitly\n3. `manageApps(action=deployApp, cosTimestamp=\u003CunixTimestamp>, installCmd?, buildCmd?, deployCmd?)`\n   - `installCmd` \u002F `buildCmd` \u002F `deployCmd` are pipeline declarations executed in the cloud\n     container; you pass data and declarations, you do not run local shell commands\n\n### Static hosting — route through CloudApp\n\n`manageHosting(action=upload)` is blocked in cloud mode because it needs a local path.\nDeploy a static site through the CloudApp two-step upload above (upload the prebuilt\nartifact, exclude `node_modules`). Uploading or downloading an already-hosted file has no\nremote substitute and needs local mode. The other hosting actions (`delete`,\n`setWebsiteDocument`, `enableService`, `bindDomain`, `unbindDomain`, `updateDomain`) remain\navailable.\n\n### What cloud mode does not give you\n\n- **No dry-run.** There is no `deployPlan` against a local `cloudbaserc`. Do not claim a plan\n  was generated or reviewed in cloud mode; state what is about to be deployed and what the\n  upload contains. Roadmap: upload `cloudbaserc` as a data artifact, then run server-side\n  plan\u002Fapply orchestration.\n- **No local project context.** `mode` \u002F `envOverrides` resolution from a project file does\n  not apply; pass the target environment explicitly.\n\nFor parameter details, see `references\u002Fplan-and-apply.md` (`Cloud-hosted upload pipeline path`).\n\n## Core principles\n\n1. **Plan before apply — always.**\n   Run `deployPlan` first (dry-run, zero side effects). Read the per-resource action\n   classification and show it to the user before calling `deployApply`.\n\n2. **Apply requires explicit confirm.**\n   `deployApply` will refuse unless `confirm=true` is passed. This is the destructive-write guard.\n\n3. **Deployment Gate.**\n   Before any apply, complete `cloudbase-platform\u002Freferences\u002Fprotocols\u002Fdeployment-gate.md`\n   and present the mandatory declaration.\n\n4. **Conservative on existing resources by default.**\n   `yes` defaults to `false` → existing resources are skipped, not overwritten. Only pass\n   `yes=true` when the user explicitly wants to overwrite\u002Fupdate existing resources.\n\n5. **database failure always aborts.**\n   Even with `continueOnError=true`, a database-stage failure stops the whole deploy,\n   because later resources depend on it.\n\n6. **Resolve envId explicitly.**\n   Never rely on implicit defaults silently — know which environment is targeted (see\n   the priority table below) and confirm it with the user before applying.\n\n## Plan action classification\n\n`deployPlan` returns a list of resource entries. Each `status` means:\n\n| status | meaning |\n|--------|---------|\n| `create` | new resource, will be created |\n| `update` | exists, will be overwritten\u002Fupdated |\n| `skip` | no change needed |\n| `conflict` | conflict detected — deploy will abort, must resolve first |\n| `deploy` | direct overwrite upload |\n\nIf any entry is `conflict`, stop and resolve it before applying.\n\n## envId resolution priority\n\n```\nexplicit envId param  >  cloudbaserc `envId`  >  logged-in \u002F bound environment\n```\n\nIf none can be resolved, the tool errors out. Prefer confirming the resolved envId\nwith the user before applying to production.\n\n## Local workflow (build → plan → apply)\n\nWhen `hosting` declares a `buildCommand`, declarative deploy is a three-step flow —\n`deployApply` no longer runs the local build implicitly:\n\n1. Ensure a `cloudbaserc` config exists under the project root (`cwd`).\n2. **Build first** (only when `hosting` has a `buildCommand`): call\n   `deployBuild({ cwd, mode? })` to produce the local artifacts (builds every hosting\n   item; pure-static items without a build command are skipped automatically).\n   - If the build artifacts are missing at apply time, `deployApply` fails with\n     `BUILD_OUTPUT_NOT_FOUND` and directs you back to this step — call `deployBuild`\n     first, then retry.\n   - `deployBuild` needs no `envId` and no `confirm` (local build only, never touches\n     cloud resources); if dependencies are not installed it fails with\n     `DEPENDENCY_NOT_INSTALLED` and tells you to run install first.\n3. Call `deployPlan` (optionally with `mode`, `envId`, `only`, `skip`). Read the plan.\n4. Present the plan + Deployment Gate declaration to the user; get confirmation.\n5. Call `deployApply` with `confirm=true` (plus `yes` \u002F `concurrency` \u002F `continueOnError`\n   as needed). Reuse the same `mode` \u002F `envId` \u002F `only` \u002F `skip` as the plan.\n   A hosting item with existing build output is uploaded directly (the tool clears\n   the build command and reports `hostingNeutralized: true`); rebuild with `deployBuild`\n   after source changes so the upload is not stale.\n6. Report the applied result back to the user.\n\nFor cloud-hosted MCP mode, do not ask for local `cwd`\u002Ffilesystem reads; use the\n`Cloud mode` upload-channel flow above.\n\n## Build & pipeline execution\n\nUse this mental model: **build → plan → apply**. The build executor depends on resource type.\n\n| resource | typical build executor | deployment path |\n|----------|------------------------|-----------------|\n| `hosting` | `deployBuild` (local shell build, run **before** apply) | `deployApply` uploads the built output directly; missing output → `BUILD_OUTPUT_NOT_FOUND` |\n| `app` (`framework=static`) | local prebuilt artifact | package upload + deploy record |\n| `app` (non-static frameworks) | cloud pipeline | source zip upload + cloud build + deploy |\n| `functions` | local zip \u002F cloud build \u002F image pipeline | depends on `buildStrategy` (`zip`\u002F`cloud`\u002F`local`\u002F`image`) |\n\n`deployBuild` builds every `hosting` item that has a `buildCommand` (framework mapping or\npackage.json auto-detection); it skips pure-static items. Build failures surface as\n`BUILD_FAILED`, missing local dependencies as `DEPENDENCY_NOT_INSTALLED` (run install\nfirst — `deployBuild` never installs dependencies for you).\n\nBuild command resolution follows declaration priority:\n\n`explicit config` > `framework mapping defaults` > `package.json` auto-detection\n\n`buildCommand` \u002F `installCommand` \u002F `deployCmd` are declarative intent in config.\nExecution ownership depends on path:\n\n- local-form paths: specific steps may run in local shell executor\n- cloud-hosted paths: commands are executed by cloud pipeline container (staticCmd),\n  or replaced by prebuilt artifact upload\n\nSo the answer to \"can cloud mode run local CLI commands\" is: execution authority is\nmoved from local shell to cloud pipeline; agent transmits declarations and artifacts.\n\n## Routing\n\n| User task | Read |\n|-----------|------|\n| cloudbaserc resource fields & desired-state config shape | `references\u002Fconfig-schema.md` |\n| deployPlan → deployApply two-step flow, parameters, safety | `references\u002Fplan-and-apply.md` |\n| Multi-env (mode \u002F envOverrides), envId priority, env vars | `references\u002Fmulti-env.md` |\n\n## Minimum self-check\n\n- [ ] Built the hosting artifacts first (`deployBuild`) when `hosting` declares a `buildCommand`?\n- [ ] Ran `deployPlan` and read the action classification before `deployApply`?\n- [ ] Resolved and confirmed the target `envId`?\n- [ ] Completed the Deployment Gate declaration before applying?\n- [ ] Passed `confirm=true` only after user confirmation?\n- [ ] Left `yes=false` unless overwrite of existing resources was explicitly requested?\n- [ ] Handled any `conflict` entries before applying?\n\n## Reference index\n\nAll packaged reference files (required for skill lint reachability):\n\n- [config-schema.md](references\u002Fconfig-schema.md)\n- [plan-and-apply.md](references\u002Fplan-and-apply.md)\n- [multi-env.md](references\u002Fmulti-env.md)\n",{"name":5,"license":14,"version":23,"alwaysApply":19,"description":7},"2.36.2","main","33b6151ccee9aa0816c6f32d021be77d82772755","connectors\u002Fcloudbase\u002Fskills\u002Freferences\u002Fcloudbase-declarative-deploy",138,"https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills","https:\u002F\u002Fgithub.com\u002Finfometa","2026-11-11 03:15:35",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add infometa\u002Fworkbuddyskills --skill cloudbase-declarative-deploy",{"tool":37,"command":38},"bunx","bunx skills add infometa\u002Fworkbuddyskills --skill cloudbase-declarative-deploy",{"tool":40,"command":41},"pnpm","pnpm dlx skills add infometa\u002Fworkbuddyskills --skill cloudbase-declarative-deploy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fconnectors\u002Fcloudbase\u002Fskills\u002Freferences\u002Fcloudbase-declarative-deploy\u002FSKILL.md",true,[45,51,55],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Fconfig-schema.md","REFERENCE","参考文档",5510,"https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fconnectors\u002Fcloudbase\u002Fskills\u002Freferences\u002Fcloudbase-declarative-deploy\u002Freferences\u002Fconfig-schema.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fmulti-env.md",2065,"https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fconnectors\u002Fcloudbase\u002Fskills\u002Freferences\u002Fcloudbase-declarative-deploy\u002Freferences\u002Fmulti-env.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fplan-and-apply.md",7554,"https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fconnectors\u002Fcloudbase\u002Fskills\u002Freferences\u002Fcloudbase-declarative-deploy\u002Freferences\u002Fplan-and-apply.md",[60,67,74,81,88,97],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M7A1EC013S1PBBTSH2PA2S7D","yingmi-skill","当用户需要查询基金、策略、公告、财经资讯，做资产配置、组合诊断、风险回测、现金流分析，或生成图表、PDF 时，优先使用本 Skill 获取真实数据与可执行能力。","https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fskills\u002Fyingmi-skill\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":18},"01M7A194T67P6NRVYK8KCTH3CH","web-access","所有联网操作必须通过此 skill 处理，包括：搜索、网页抓取、登录后操作、网络交互等。","https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-access\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":18},"01M7A14FATMDD6FK8QAGXY5GVR","tencentmap-map-assistant","腾讯位置服务·地图助手 Skill，一句自然语言调用腾讯地图全套能力，无需开发者账号、开箱即用。提供 AI 旅游攻略、地点搜索（含评分\u002F人均\u002F营业时间）、关键词提示、路线规划（驾车\u002F步行\u002F公交\u002F骑行）、地址解析与逆解析、行政区划、IP 定位、距离计算、天气查询，并可将行程或多 POI 渲染成网页地图。涉及找地点、规划路线、旅游行程、查天气、坐标转换等出行场景时使用。","https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fskills\u002Ftencentmap-map-assistant\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M7A0SX4XW5053MZ2S921EDH2","skill-scanner","Scan any agent skill for security risks before you install or use it. Powered by Tencent Zhuque Lab A.I.G (AI-Infra-Guard). 100% local static analysis — no file contents or credentials leave your device. Compatible with CodeBuddy, Cursor, Windsurf, Claude Code, OpenClaw and more. Triggers on: 这个 skill 安全吗, skill 安全扫描, 检查 skill 安全, audit skill, scan skill, check skill safety, analyze skill, inspect skill, verify skill, skill security, skill supply chain. Do NOT trigger for general agent usage, full system health checks, project debugging, or normal development.","https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fskills\u002Fskill-scanner\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":92,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":18},"01M7A0SQC2CZB3450G8471673M","skill-creator","Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends agent capabilities with specialized knowledge, workflows, or tool integrations.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":18},"01M7A0RHV7BKS7DFQF9X9QCCNN","shader-dev","Comprehensive GLSL shader techniques for creating stunning visual effects — ray marching, SDF modeling, fluid simulation, particle systems, procedural generation, lighting, post-processing, and more.","https:\u002F\u002Fgithub.com\u002Finfometa\u002Fworkbuddyskills\u002Fblob\u002Fmain\u002Fskills\u002Fshader-dev\u002FSKILL.md",[],[]]