- name
SKILL.md
ไฟล์สกิลยังคงอยู่ในรีโพซิทอรีของผู้เผยแพร่
วางคำสั่งที่คัดลอกไว้ในเทอร์มินัล คำสั่งจะติดตั้ง SKILL.md นี้ลงในเอเจนต์ตัวนั้น
npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill cloud-api-operations -a cursor -yวางคำสั่งที่คัดลอกไว้ในเทอร์มินัล คำสั่งจะติดตั้ง SKILL.md นี้ลงในเอเจนต์ตัวนั้น
npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill cloud-api-operations -a claude-code -yวางคำสั่งที่คัดลอกไว้ในเทอร์มินัล คำสั่งจะติดตั้ง SKILL.md นี้ลงในเอเจนต์ตัวนั้น
npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill cloud-api-operations -a codex -yวางคำสั่งที่คัดลอกไว้ในเทอร์มินัล คำสั่งจะติดตั้ง SKILL.md นี้ลงในเอเจนต์ตัวนั้น
npx skills add TencentCloudBase/CloudBase-AI-Toolkit --skill cloud-api-operations -a grok -yส่งข้อความที่คัดลอกไว้ในแชต Grok Bot แล้ว Bot จะดึง SKILL.md นี้จาก GitHub และเพิ่มลงในสกิลที่ Bot ทุกตัวของคุณใช้ร่วมกัน
Install this skill: https://github.com/TencentCloudBase/CloudBase-AI-Toolkit/tree/HEAD/config/.claude/skills/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 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.
./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 覆盖的场景。
Priority rule: if @cloudbase/manager-node has a matching method, use it; drop to raw cloud API only when it does not.
Three identities produce the same error text. Before reading anything into an UnauthorizedOperation, find out which one you are holding:
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.
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.ListAttachedRolePolicies + GetPolicy) instead of assuming, and treat UnauthorizedOperation as "this identity lacks this action", never as a broken setup.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.
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:
./references/recipes/pg-storage-alarm.md./references/recipes/icp-filing-readiness.md./references/recipes/pg-instance-spec.md./references/recipes/custom-domain.md./references/recipes/cloud-audit-operation-trace.md./references/recipes/platform-onboarding.md./references/recipes/platform-agent-connect.md./references/recipes/platform-agent-guardrails.md./references/recipes/platform-usage-and-recycle.mdNo recipe for this scenario? A single public Action with no multi-step orchestration does not need a new recipe: resolve it from the API index, then call it through callCloudApi (or tcb api in a script). Recipes exist for call sequences, prerequisite checks and cleanup obligations — not for one-shot switches.
Done when: every parameter value in the call sequence traces to a recipe value marked as verified (实测) or to official docs.
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.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 operat
---name: cloud-api-operationsdescription: Operate Tencent Cloud control-plane resources (monitoring/alarms, CLB, CAM roles, COS, MySQL, SCF) via cloud…---# config/.claude/skills/cloud-api-operations/SKILL.mdภาพรวม
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.
FAQ
ดาวน์โหลด config/.claude/skills/cloud-api-operations/SKILL.md จากผู้เผยแพร่ หรือคัดลอกพาธแล้วเปิดรีโพซิทอรี PlugMCP แสดงรายการสกิลเท่านั้น ไม่ได้โฮสต์ไฟล์
ผู้เผยแพร่เก็บไว้ที่ https://github.com/TencentCloudBase/CloudBase-AI-Toolkit
Claude, Cursor, Codex และ Grok Build อ่าน SKILL.md ที่คุณเพิ่มจากรีโพซิทอรีของผู้เผยแพร่ได้ ส่วน Grok Bot จะติดตั้งให้เมื่อคุณส่งลิงก์โฟลเดอร์ GitHub ของสกิลในแชต