SkillAgentSearch skills...

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

Install / Use

npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill cloud-api-operations

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

81/100

Category

Operations

Supported Platforms

Universal

Our assessment of cloud-api-operations

cloud-api-operations scores 81/100 on our quality scale, 645th of 755 Operations skills we index.

Its SKILL.md is 5.7 KB long, well organised into 9 sections and no code examples: a solid amount of guidance for an agent.

With 1,124 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
13/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so cloud-api-operations is actively maintained.
  • Our last check on 2026-11-08 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

cloud-api-operations compared with similar skills

All 4 of these similar skills score higher than cloud-api-operations; compare them before choosing.

SkillScoreStarsUpdatedFormat
cloud-api-operations (this skill)by TencentCloudBase811.1k54d agoSKILL.md
claude-memby thedotmack100117.9ktodayCLAUDE.md
Agent-Reachby Panniantong100112.7k9d agoCLAUDE.md
rufloby ruvnet10082.0ktodayCLAUDE.md
headroomby headroomlabs-ai10079.9ktodayCLAUDE.md

Frequently asked questions

How do I install cloud-api-operations?
Run npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill cloud-api-operations. The install tabs above show the steps for each supported agent.
Which AI agents does cloud-api-operations work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is cloud-api-operations safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is cloud-api-operations still maintained?
The repository was last updated about 2 months ago, so cloud-api-operations is actively maintained.

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. version: 2.34.8

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

  • 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 is known, 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

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.

Related Skills

View on GitHub
GitHub Stars1.1k
CategoryOperations
Updated1mo ago
Forks143

Languages

TypeScript

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions