cloud-api-operations
/cloud-api-operations
Operate Tencent Cloud control-plane resources (monitoring/alarms, CLB, CAM roles, COS, MySQL, SCF) via cloud APIs when no dedicated MCP tool covers the task. Use when a task needs control-plane operations beyond CloudBase's own tooling, or when a callCloudApi call failed and needs classifying. Also covers enterprise platform integration: wrapping CloudBase MCP into an organization-specific MCP (tool trimming, dangerous-action interception, per-user API Key distribution, audit) — use when the user mentions 企业接入 / 封装 MCP / 企业专属 MCP / 多租户凭证下发 / platform MCP wrapping. See recipes/enterprise-mcp-wr
- Author
- tencentcloudbase ↗
- Repository
- cloudbase-skills ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 17
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 3
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Operate Tencent Cloud control-plane resources (monitoring/alarms, CLB, CAM roles, COS, MySQL, SCF) via cloud APIs when no dedicated MCP tool covers the task. Use when a task needs control-plane operations beyond CloudBase's own tooling, or when a callCloudApi call failed and needs classifying. Also covers enterprise platform integration: wrapping CloudBase MCP into an organization-specific MCP (tool trimming, dangerous-action interception, per-user API Key distribution, audit) — use when the user mentions 企业接入 / 封装 MCP / 企业专属 MCP / 多租户凭证下发 / platform MCP wrapping. See recipes/enterprise-mcp-wr
Original author description
Operate Tencent Cloud control-plane resources (monitoring/alarms, CLB, CAM roles, COS, MySQL, SCF) via cloud APIs when no dedicated MCP tool covers the task. Use when a task needs control-plane operations beyond CloudBase's own tooling, or when a callCloudApi call failed and needs classifying. Also covers enterprise platform integration: wrapping CloudBase MCP into an organization-specific MCP (tool trimming, dangerous-action interception, per-user API Key distribution, audit) — use when the user mentions 企业接入 / 封装 MCP / 企业专属 MCP / 多租户凭证下发 / platform MCP wrapping. See recipes/enterprise-mcp-wr
How it works
- Sibling skills (local only)
- When to use
- Workflow
- Constraints
SKILL.md preview
--- name: cloud-api-operations description: "Operate Tencent Cloud control-plane resources (monitoring/alarms, CLB, CAM roles, COS, MySQL, SCF) via cloud APIs when no dedicated MCP tool covers the task. Use when a task needs control-plane operations beyond CloudBase's own tooling, or when a callCloudApi call failed and needs classifying. Also covers enterprise platform integration: wrapping CloudBase MCP into an organization-specific MCP (tool trimming, dangerous-action interception, per-user API Key distribution, audit) — use when the user mentions 企业接入 / 封装 MCP / 企业专属 MCP / 多租户凭证下发 / platform MCP wrapping. See recipes/enterprise-mcp-wrapper.md." version: 2.36.1 license: MIT --- # Cloud API Operations Operate Tencent Cloud resources that CloudBase depends on but that no dedicated MCP tool covers (monitoring & alarms, CLB, CAM roles, cross-product infra). Two goals: **find the right API without guessing**, and **reuse proven workflows instead of re-exploring**. ## Sibling skills (local only) Sibling CloudBase skills ship beside this skill. Use local relative paths such as `../cloudbase-platform/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. ## When to use - The user asks to manage/operate Tencent Cloud resources beyond CloudBase's dedicated MCP tools (e.g. configure alarm policies, inspect CLB, attach CAM policies). - The user wants to control these resources from code and asks which API/SDK to use. - A callCloudApi call failed and you need to classify the error (wrong Action / wrong params / missing CAM permission) and recover. ## Workflow ### 1. Discover the API — resolve names from a documented source 1. **Read the API index first**: https://docs.cloudbase.net/ai/cloudbase-ai-toolkit/api-reference.md — auto-synced daily, action-level coverage (TCB 105 + dependency products: MySQL / SCF / COS). Check rate limits there too. The index check is a quick grep — run it in parallel with step 2/3 fetches, do not serialize. 2. If the index does not cover the target product, go to the product's official API docs (e.g. monitor: https://cloud.tencent.com/document/product/649/30343) and confirm the exact Action name, Version, and parameters. 3. For machine-readable parameter schema, fetch the official SDK models source directly — see `./references/calling-methods.md` §2 item 4. **Done when**: the Action name, Version, and full parameter shape each trace to the index, official product docs, or SDK models source — nothing from memory. A call that still returns `action ... is invalid or not found` means a name was not resolved this way; classify and recover via the error table in `./references/calling-methods.md` §1. > **API first:公开 API 概览就是契约边界。** 索引里查不到某个能力,它就不在公开契约内 —— 不要拿某个 SDK 的封装方法反推未公开的 Action 名去调(这类 Action 不受公开文档保护,非该语言的使用者也无从照做)。此时改用有公开 API 的等价路径,或把缺口明确告诉用户。本 skill 的 recipes 只收录公开 API 覆盖的场景。 ### 2. Choose the calling path | Scenario | Path | Reference | | --- | --- | --- | | Interactive ops inside this session | MCP `callCloudApi` | `./references/calling-methods.md` §1 | | Picking the `service` identifier / deciding whether `version` is needed | MCP `callCloudApi` | `./references/service-versions.md` | | User's code / scripts | Official SDKs (TC3-HMAC-SHA256) or `@cloudbase/manager-node` | `./references/calling-methods.md` §2 | | Quick one-off verification | API Explorer (https://console.cloud.tencent.com/api/explorer) | — | Priority rule: if `@cloudbase/manager-node` has a matching method, use it; drop to raw cloud API only when it does not. ### 3. Check credentials before the first call **Three identities produce the same error text.** Before reading anything into an `UnauthorizedOperation`, find out which one you are holding: | Identity | How it is reached | CAM / CloudAudit | | --- | --- | --- | | Account-level login (`federated-user/<id>`) | Device-code / web login, or account-level SecretId + Key | reachable, subject to that identity's CAM policies | | `TCB_QcsRole` service role | what CLI / MCP **become** after calling a CloudBase product API | refused (`resource (...) has no permission`) | | Environment API Key (`<uin>:TCB-CAPI-Configured-idaas-apikey`) | `--cloudbase-api-key -e <envId>` | refused — the API Key model has no channel to attach arbitrary CAM policies | Confirm the identity with `sts GetCallerIdentity` (`--api-version 2018-08-13`) before concluding anything: the refusal text is identical across all three rows, so it cannot tell you which row you are in. **Order matters.** Calling a CloudBase product API swaps the identity to `TCB_QcsRole` for the rest of the session, so a CAM / CloudAudit call issued *after* any product call is refused even though the login is account-level. Do the CAM / audit work **first**. - Read the current credential scope from `auth` tools: `credential_scope: account` = account-level, reaches control-plane APIs subject to that identity's CAM policies; `env` = API Key, scoped to one environment's data plane plus the fixed TCB policies. - Permission comes from a different place per credential identity: the account-level identity's own policies, the API Key model (no channel to attach arbitrary CAM policies), or the TCB service role that CLI / MCP assume. Which cross-product capabilities that role family already covers is not fixed — read the attached policies (`ListAttachedRolePolicies` + `GetPolicy`) instead of assuming, and treat `UnauthorizedOperation` as "this identity lacks this action", never as a broken setup. - On `UnauthorizedOperation` / `AuthFailure`, hand the user a **one-click CAM grant link** (role name + policy name + `principal`) instead of telling them to go find the policy in the console, then retry the original call. Role targets, the `principal` values, and which preset policy covers what: `./references/calling-methods.md` §3. **Done when**: the credential identity has been confirmed with `sts GetCallerIdentity` (not inferred from the error text), and every permission error has been converted into a clickable authorization link carrying a concrete policy name before any retry. ### 4. Follow a proven recipe when one exists Recipes encode the exact call sequence, required parameters, and empirically discovered pitfalls so the flow works on the first pass. One scenario per file — start from the index `./references/recipes/README.md`, whose 状态 column records how far each recipe has been verified: - **PostgreSQL storage-usage alarm**: `./references/recipes/pg-storage-alarm.md` - **ICP filing readiness and wait-time checks**: `./references/recipes/icp-filing-readiness.md` - **PostgreSQL instance spec change and shared-to-dedicated upgrade**: `./references/recipes/pg-instance-spec.md` - **Custom domain onboarding for an env (HTTP access domain, certificate, DNS binding)**: `./references/recipes/custom-domain.md` - **Operation trace / 操作审计 — who did what, from which IP, with which key**: `./references/recipes/cloud-audit-operation-trace.md` - **Platform edition onboarding — create env and issue the environment API key**: `./references/recipes/platform-onboarding.md` - **Wiring that credential into a user's agent, one env per project**: `./references/recipes/platform-agent-connect.md` - **Closing down the agent's tool surface — plugin trimming, gateway wrap for audit, expert-enforced constraints**: `./references/recipes/platform-agent-guardrails.md` - **Platform edition usage, billing cycle, and environment recycling**: `./references/recipes/platform-usage-and-recycle.md` **Done when**: every parameter value in the call sequence traces to a recipe value marked as verified (实测) or to official docs. ## Constraints - Region is a top-level `region` argument (X-TC-Region), never a body param. Some APIs additionally take a short region code inside `Dimensions` (e.g. `sh` vs `ap-shanghai`) — these are different fields. - Route SDK-language details to official SDK docs or sdkHints; keep this skill SDK-language-agnostic.
Files in this package (17)
- SKILL.md 8 KB
- references/calling-methods.md 14 KB
- references/service-versions.md 5 KB
- references/recipes/README.md 7 KB
- references/recipes/billing-charges-explained.md 5 KB
- references/recipes/cloud-audit-operation-trace.md 20 KB
- references/recipes/credits-exhaustion.md 7 KB
- references/recipes/custom-domain.md 30 KB
- references/recipes/enterprise-mcp-wrapper.md 11 KB
- references/recipes/icp-filing-readiness.md 16 KB
- references/recipes/pg-instance-spec.md 31 KB
- references/recipes/pg-monitor-data.md 5 KB
- references/recipes/pg-storage-alarm.md 7 KB
- references/recipes/platform-agent-connect.md 6 KB
- references/recipes/platform-agent-guardrails.md 6 KB
- references/recipes/platform-onboarding.md 5 KB
- references/recipes/platform-usage-and-recycle.md 5 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · tencentcloudbase/cloudbase-skills | 90 | MIT |
| tencentcloudbase/cloudbase-ai-toolkit | 90 | MIT |
Identical content appears in 2 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 8de8a88c5f31 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90cloudbase-cli
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… - 100http-api-cloudbase
CloudBase official HTTP API client guide. This skill should be used when backends, scripts, or non-SDK clients must call CloudBase platform APIs over raw HTTP instead of using a platform SDK or MCP management tool. - 100http-api-cloudbase
CloudBase official HTTP API client guide. This skill should be used when backends, scripts, or non-SDK clients must call CloudBase platform APIs over raw HTTP instead of using a platform SDK or MCP management tool. - 100cloud-oidc
Use when connecting a Nia Teams Agent to Alibaba Cloud RAM OIDC, Tencent Cloud CAM OIDC, or Kubernetes OIDC RBAC via standard Workload OIDC, configuring ordinary permissions, human-confirmed elevated permissions, role prompts, and live token verification from an environment… - 100boomi-cloud-api-management
Operates Boomi Cloud API Management (CAM), the SaaS API management platform formerly known as TIBCO Cloud API Management or Mashery. Use when the user works with CAM or Mashery APIs, endpoints, packages, plans, applications, or API keys. Not for the Boomi API Gateway or API Control Plane (ACP). - 100cloudbase-platform
CloudBase platform knowledge and best practices. Use this skill for general CloudBase platform understanding, including storage, hosting, authentication, cloud functions, database permissions, and data models.