cloudbase-platform skill
✓ VerifiedProvides high-level platform concepts, capability selection, and routing guidance for CloudBase services including hosting, storage, and databases.
- GitHub stars
- 1,164
- Files
- 6
- Last commit
- Nov 11, 2026
- License
- MIT
- Allowed tools
- —
What does the cloudbase-platform skill do?
cloudbase-platform provides high-level platform concepts, capability selection, and routing guidance for CloudBase services including hosting, storage, and databases.
Summary generated from the skill's SKILL.md.
About the cloudbase-platform skill
Selecting the right CloudBase services and understanding platform architecture is what this skill enables for developers. It serves as a foundational guide for those deciding between hosting, storage, authentication, and database options before they begin writing specific implementation code. An agent should load this skill when a user needs high-level capability selection, console navigation assistance, or guidance on cross-platform best practices.
The skill provides conceptual explanations and routing guidance to ensure developers use the correct specialized tools for their specific needs. For example, it helps distinguish between Web and Mini Program authentication models and clarifies the differences between security domains and custom domains. It relies on platform-level knowledge to prevent common mistakes, such as using NoSQL syntax for PostgreSQL tasks. By providing a roadmap to sibling skills, it ensures that once a technical direction is chosen, the agent can transition to the appropriate implementation tool for tasks like cloud functions, document databases, or web development.
What an agent can do with it
- 1Compare platform capabilitiesDetermine which CloudBase service or tool is most appropriate for a new project requirement.
- 2Configure domain managementIdentify whether to add a security domain for CORS or bind a new custom HTTPS domain.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the cloudbase-platform skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the cloudbase-platform skill in Claude Code
~/.claude/skills/cloudbase-platform/SKILL.md
$ npx degit TencentCloudBase/CloudBase-AI-Toolkit/config/.claude/skills/cloudbase-platform ~/.claude/skills/cloudbase-platformInstall the cloudbase-platform skill in Claude Code (project)
.claude/skills/cloudbase-platform/SKILL.md
$ npx degit TencentCloudBase/CloudBase-AI-Toolkit/config/.claude/skills/cloudbase-platform .claude/skills/cloudbase-platformInstall the cloudbase-platform skill in Codex
~/.agents/skills/cloudbase-platform/SKILL.md
$ npx degit TencentCloudBase/CloudBase-AI-Toolkit/config/.claude/skills/cloudbase-platform ~/.agents/skills/cloudbase-platformInstall the cloudbase-platform skill in Gemini CLI
~/.gemini/skills/cloudbase-platform/SKILL.md
$ npx degit TencentCloudBase/CloudBase-AI-Toolkit/config/.claude/skills/cloudbase-platform ~/.gemini/skills/cloudbase-platformInstall the cloudbase-platform skill in Claude.ai
npx degit TencentCloudBase/CloudBase-AI-Toolkit/config/.claude/skills/cloudbase-platform cloudbase-platform && zip -r cloudbase-platform.zip cloudbase-platform # claude.ai → Customize → Skills → + → Create skill → Upload a skill → cloudbase-platform.zip
Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work · What to fix for more points
- Source repository linked and reachabletencentcloudbase/cloudbase-ai-toolkit/config/.claude/skills/cloudbase-platform is public and reachablegithub.com/tencentcloudbase/cloudbase-ai-toolkit/tree/HEAD/c ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-11-11github.com/tencentcloudbase/cloudbase-ai-toolkit/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/tencentcloudbase/cloudbase-ai-toolkit/blob/HEAD/c ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/tencentcloudbase/cloudbase-ai-toolkit/blob/HEAD/c ↗Pass
- SKILL.md follows the Agent Skills formatthe description does not say when to use the skillgithub.com/tencentcloudbase/cloudbase-ai-toolkit/blob/HEAD/c ↗Finding
SKILL.md
View on GitHubSibling skills (local only)
Sibling CloudBase skills ship beside this skill. Use local relative paths such as ../auth-tool-cloudbase/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.
Cross-cutting protocols (required before code changes or deployments):
- Change Safety Protocol:
references/protocols/change-safety-protocol.md - Deployment Gate:
references/protocols/deployment-gate.md - Sensitive Runtime Data Protection:
references/protocols/sensitive-runtime-data-protection.md
Post-deployment (optional, non-intrusive): after a deployment is verified successful, you may offer at most once to generate anonymized shareables (Deployment Share) — see references/protocols/deployment-share.md. Deliver the card, the copy and the case-wall entry in one reply; shareables only if that is all the user asked for. Never follow up if declined; never publish or submit on the user's behalf.
Activation Contract
Use this first when
- The user asks which CloudBase capability, service, or tool to use, or needs a high-level understanding of hosting, storage, authentication, cloud functions, or database options.
- The task is about console navigation, cross-platform differences, permission models, or platform-level best practices before implementation.
Read before writing code if
- It is still unclear whether the task belongs to Web, mini program, cloud functions, storage, MySQL / NoSQL, or auth.
- The response needs platform selection, conceptual explanation, or control-plane navigation more than direct implementation steps.
Then also read
- Minimal Web + database demo (BaaS-first, no cloud functions by default) ->
../minimal-web-baas-demo/SKILL.md- Stack order for 最小前后端 / Lovable-like demos: Web SDK CRUD > MCP schema > template warmup during credential wait > cloud functions (default count = 0). Capability sniff: connector ready →
queryEnv→ lock one DB plane → MCP schema →@cloudbase/js-sdkCRUD → preview.
- Stack order for 最小前后端 / Lovable-like demos: Web SDK CRUD > MCP schema > template warmup during credential wait > cloud functions (default count = 0). Capability sniff: connector ready →
- Web app implementation ->
../web-development/SKILL.md - Web auth and provider setup ->
../auth-tool-cloudbase/SKILL.md,../auth-web-cloudbase/SKILL.md - Mini program development ->
../miniprogram-development/SKILL.md - WeChat Pay, Official Account OAuth, JSAPI Pay, or Native QR-code Pay through CloudBase Integration Center ->
../cloudbase-wechat-integration/SKILL.md(official docs:https://docs.cloudbase.net/integration/introduce.md) - Cloud functions ->
../cloud-functions/SKILL.md - Official HTTP API clients ->
../http-api-cloudbase/SKILL.md - Document database ->
../cloudbase-document-database-web-sdk/SKILL.mdor../cloudbase-document-database-in-wechat-miniprogram/SKILL.md - CloudBase PostgreSQL / PG ->
../postgresql-development-cloudbase/SKILL.md - Realtime / live push / channels / live table change subscriptions / multiplayer sync ->
../postgresql-development-cloudbase/references/realtime.md- PG mode only. Read its Step 0 before writing realtime code:
describeRealtimeonly reads settings, so do not callenableRealtimeas a routine step — ask the user before provisioning. app.realtime()(Broadcast / Presence / Postgres CDC) is not document-databasecollection.watch(). Do not answer a realtime request withwatch()code, or the reverse.
- PG mode only. Read its Step 0 before writing realtime code:
- PostgreSQL schema and data modeling ->
../postgresql-development-cloudbase/SKILL.md; existing MySQL only ->../relational-database-mcp-cloudbase/SKILL.md - Cloud storage ->
../cloud-storage-web/SKILL.md
Do NOT use for
- Direct implementation of web pages, auth flows, functions, or database operations when a more specific skill already fits.
- Low-level API parameter references or SDK recipes that belong in specialized skills.
Common mistakes / gotchas
- Treating this general skill as the default entry point for all CloudBase development.
- Staying here after the correct implementation skill is already clear.
- Mixing platform overview with platform-specific API shapes or SDK details.
- Using this overview skill as a detour in an existing application where the active auth, storage, and data files are already obvious.
- Making code or configuration changes without first following the Change Safety Protocol (
cloudbase-platform/references/protocols/change-safety-protocol.md). - Starting any deployment, publish, custom domain, or CloudRun work without first completing the checks in
cloudbase-platform/references/protocols/deployment-gate.md. - Echoing
x-cloudbase-context, fullreq.headers, orprocess.envfrom Cloud Functions / CloudRun (including httpbin-style debug images) — followreferences/protocols/sensitive-runtime-data-protection.md. - Confusing security domains with custom domains: these are two different tools for different purposes. See the "Domain Management Tools" table below for the authoritative split.
When to use this skill
Use this skill for CloudBase platform knowledge when you need to:
- Understand CloudBase storage and hosting concepts
- Compare platform capabilities before implementation
- Understand cross-platform auth differences (Web vs Mini Program)
- Understand database permissions and access control
- Access CloudBase console management pages
This skill provides foundational knowledge that applies to all CloudBase projects, regardless of whether they are Web, Mini Program, or backend services.
How to use this skill (for a coding agent)
-
Understand platform differences
- Web and Mini Program have completely different authentication approaches
- Must strictly distinguish between platforms
- Never mix authentication methods across platforms
- If the workspace is already an application with TODOs or prebuilt handlers, do not stay in platform overview mode. Move quickly to the concrete implementation skill and the existing files that own the flow.
-
Follow best practices
- Use SDK built-in authentication features (Web)
- Understand natural login-free feature (Mini Program)
- Configure appropriate database permissions
- Prefer
@cloudbase/js-sdkdirect DB access for browser CRUD; use cloud functions only for secrets, scheduled/background jobs, or elevated cross-collection logic that security rules / RLS cannot express (see../minimal-web-baas-demo/SKILL.mdfor the demo default)
-
Use correct SDKs and APIs
- Different platforms require different SDKs for data models
- MySQL data models must use models SDK, not collection API
- PostgreSQL / CloudBase PG work must route to
postgresql-development-cloudbase; do not reuse NoSQLapp.database()/db.collection(...)snippets or MySQLqueryMysqlDatabase/manageMysqlDatabasefor PG data paths - Use
queryEnvtool to get environment ID - In an existing Web application with fixed structure, inspect the existing
src/lib/backend.*,src/lib/auth.*,src/lib/*service.*, and bound page handlers before broad concept reading.
-
Use the canonical CloudBase MCP setup from the main
cloudbaseguideline- This platform overview intentionally does not duplicate the full MCP / mcporter config block
- For the canonical config snippet, CLI commands, and auth examples, read the main
cloudbaseguideline first - Keep the same core rules here: prefer MCP when tools are available in this session; if not, configure MCP for next session and use
tcbCLI now (../cloudbase-cli/SKILL.md,../cloudbase/references/tooling-fallback.md). Inspect tool schemas before MCP execution. Do not hard-code Secret ID / Secret Key / Env ID in config - Keep the auth split explicit: management-side login uses
auth, while application-side auth configuration usesqueryAppAuth/manageAppAuth
CloudBase Platform Knowledge
Domain Management Tools: Clear Distinction
When working with domain-related tasks, use the correct tool based on the requirement:
| Requirement | Tool | Parameters | Purpose |
|---|---|---|---|
| Security Domain (安全域名) | manageEnv(action="addSecurityDomain" | "removeSecurityDomain") |
domains (array of host:port strings) |
CORS/request source validation for browser uploads. No certificate involved. (Deprecated alias: envDomainManagement.) |
| Reuse existing Custom Domain | queryGateway(listCustomDomains) → manageGateway(createRoute) |
domain = existing custom domain; route fields |
Expose a service/path on an already-bound custom domain. No certificateId. Prefer this when a custom domain already exists. |
| Bind new Custom Domain (自定义域名) | manageGateway(action="bindCustomDomain") |
domain (string), certificateId (string) |
First-time bind of a new public HTTPS domain. Requires certId from SSL console. |
| Delete Custom Domain | manageGateway(action="deleteCustomDomain") |
domain (string) |
Remove custom domain binding (only after routes on that domain are deleted). |
| Disable / enable gateway route | manageGateway(action="disableRoute" | "enableRoute") |
path (required), prefer explicit domain |
Toggle Routes[].Enable via ModifyHTTPServiceRoute (not ModifyGatewayRoute). |
| Disable static hosting default domain | queryGateway(listRoutes) → manageGateway(disableRoute) |
domain = *.tcloudbaseapp.com (DomainType=STATIC_STORE, IsDefault=true), usually path="/" |
Turns off public access on the shared hosting CDN default host. Do not use manageHosting. |
Key indicators for choosing the right tool:
- Task mentions "自定义域名访问" but env already has a custom domain →
listCustomDomainsthencreateRoute(domain=...)(no certificateId) - Task mentions "certificate ID" or "SSL" and needs to bind a new domain →
manageGateway(action="bindCustomDomain") - Task mentions "浏览器上传" or "CORS" or "安全域名" → Use
manageEnv(action="addSecurityDomain" / "removeSecurityDomain") - Task mentions "public access" or "HTTPS" with domain → Prefer reuse via
createRoutewhen possible; onlybindCustomDomainfor first-time domain bind - Task mentions "关闭/禁用静态托管默认域名" /
*.tcloudbaseapp.com→queryGateway(listRoutes)thenmanageGateway(disableRoute)with that STATIC_STORE domain; never inventModifyGatewayRoute - Task asks about the whole onboarding flow (能不能绑、要等多久、解析怎么配、备案是不是前置) or a bound domain is not reachable → follow
../cloud-api-operations/references/recipes/custom-domain.md: run the read-onlyVerifyHTTPServiceRoutepre-check first, then bind, then pollStatus/DNSStatus. That recipe also covers why domain registration / DNS / ICP calls may returnUnauthorizedOperationfor an account-level identity.
Error Code Troubleshooting: Route Through Official Docs
When a CloudBase tool call fails and the error message contains a specific error code (pattern Category.Code, e.g. OperationDenied.FreePackageDenied, ResourceNotFound.*), always route through the official docs before acting — do not guess the meaning, do not hardcode fix recipes here:
- Extract the error code from the error message.
- Look it up:
searchKnowledgeBase(mode="docs", action="searchDocs", query="<错误码>")— official docs search covers error-code pages. Act on the documented meaning and the fix steps the doc prescribes (plan limits → upgrade guidance, misconfiguration → config fix, etc.). - If docs search returns nothing, fall back to the canonical error-code pages:
- Error code basics & self-service troubleshooting:
https://docs.cloudbase.net/error-code/basic - Control-plane cloud API error codes:
https://cloud.tencent.com/document/product/876/34823
- Error code basics & self-service troubleshooting:
- Never assert capability-per-plan or error-code semantics from memory — official docs and the console plan comparison are the only authoritative sources. Example: for Web 安全域名 plan requirements, cite
https://cloud.tencent.com/document/product/876/127357rather than assuming which tier unlocks it.
Billing and service-stop codes are a special case: the code's own reading is misleading, so diagnose before acting. When a failure is InsufficientBalance (a cloud function answers it with HTTP 410), EXCEED_REQUEST_LIMIT, or a service that is simply down, InsufficientBalance reads as an account problem and is not one: what runs out is the environment's resource points, which are drawn down ahead of any account balance (plan quota → resource packs → pay-as-you-go) and are not restored by a top-up. The official status-code table for the serverless service says "top up and retry", so a reader who follows the text sends the user to the account and the failure stays.
Diagnose first, then advise — four causes need four different answers (free-trial points exhausted / paid plan points exhausted / plan expired / account genuinely in arrears), and only the last one involves topping up. Run manageEnv(action="usage") for the environment's credit usage for the current cycle and read the account balance alongside it (callCloudApi, billing), both read-only; the decision table, per-plan remedies and the console entries are in credits-exhaustion. Two facts to carry into any advice: a free trial cannot buy resource packs or enable pay-as-you-go (upgrading to a paid plan is the only path), and the plan names are exactly 免费体验版 / 个人版 / 标准版 / 企业版 / 企业高级版.
Recording Operation Results
When a task explicitly requires recording operation steps or results to a file (e.g., RESULT.json): perform the tool calls first, then write a complete record containing every attempt (action, success/failure, message) plus a summary with total / succeeded / failed counts. Do not write the file from memory before the calls finish.
Storage and Hosting
-
Static Hosting vs Cloud Storage:
- CloudBase static hosting and cloud storage are two different buckets
- Generally, publicly accessible files can be stored in static hosting, which provides a public web address
- Static hosting supports custom domain configuration (requires console operation)
- Cloud storage is suitable for files with privacy requirements, can get temporary access addresses via temporary file URLs
- If the task needs COS SDK polling, file metadata lookup, or temporary URLs for an uploaded object, use cloud storage tools (
manageStorage/queryStorage), notmanageHosting(action="upload")
-
Static Hosting Domain:
- CloudBase static hosting domain and website document config can be obtained via
queryHosting(action="websiteConfig") - Combine with static hosting file paths to construct final access addresses
- Default shared host looks like
<envId>-<appId>.tcloudbaseapp.com(DomainType=STATIC_STORE, oftenIsDefault=trueinqueryGateway(listRoutes)) - To disable that default public host:
manageGateway(action="disableRoute", domain="<that-host>", path="/")(orupdateRoutewithenable=false). Re-enable withenableRoute. Do not look for amanageHostingdisable-default-domain action; do not call non-existentModifyGatewayRoute— the API isModifyHTTPServiceRoute - Important: If access address is a directory, it must end with
/
- CloudBase static hosting domain and website document config can be obtained via
-
Cloud Storage Public URL:
- CRITICAL:
manageStorage(action=upload)andqueryStorage(action=url)returntemporaryUrlwhich is a temporary signed URL that expires (default 1 hour). Do NOT use this as a permanent public URL. - To get the permanent public access URL for a cloud storage object:
- Call
queryEnv(action=info)to get environment details - Extract the storage CDN domain from
EnvInfo.Storages[0].CdnDomain(e.g.,your-env-id.tcb.qcloud.la) - Construct the public URL:
https://{CdnDomain}/{cloudPath}
- Call
- Example: If
CdnDomainisenv-xxx.tcb.qcloud.laandcloudPathisuploads/avatar.jpg, the public URL ishttps://env-xxx.tcb.qcloud.la/uploads/avatar.jpg - Note: The public URL is accessible only if the storage bucket ACL allows public read (default is
PRIVATEwhich requires signed URLs)
- CRITICAL:
-
Shared-Bucket (ExternalStorage) Environments:
- Some environments keep files in a COS bucket shared with other environments, each isolated under its own directory prefix (BasePath). Detect it with
queryEnv(action="info"): cloud storage uses a shared bucket whenEnvInfo.Storages[0].Bucketis empty andStorages[0].ExternalStorage.Enabled === true; check static hosting the same way onEnvInfo.StaticStorages[0]. Storage and hosting can use different buckets and BasePaths. - Paths stay logical. Storage and hosting tools add the BasePath themselves, so pass
cloudPathexactly as in a normal environment and never prepend the BasePath or bucket name. Example: with BasePathtenant-a, upload withcloudPath="images/a.png", not"tenant-a/images/a.png"(that nests the file undertenant-a/tenant-a/). Build hosting and CDN URLs from the logical path too — the domain resolves the BasePath, and adding it to a hosting URL returns 404. manageHosting(action="setWebsiteDocument")changes a bucket-level setting that would affect every environment in the bucket, so it fails on shared-bucket hosting. Reading withqueryHosting(action="websiteConfig")still works. Tell the user this setting is managed by the platform instead of retrying.- Storage security rules are maintained per environment, not as a COS bucket ACL, so read and update them the same way as in a normal environment.
- What happens to files when a shared-bucket environment is deleted is decided by the platform. Do not promise that its BasePath directory is kept or removed.
- Some environments keep files in a COS bucket shared with other environments, each isolated under its own directory prefix (BasePath). Detect it with
Environment and Authentication
-
SDK Initialization:
- CloudBase SDK initialization requires environment ID
- Can query environment ID via
queryEnvtool - If the user only provides an environment alias, nickname, or other short form, resolve it with
queryEnv(action="list", alias=..., aliasExact=true)first and use the returned fullEnvId - Do not pass alias-like short forms directly into SDK init,
auth.set_env, console URLs, or generated config files - For Web, always initialize synchronously:
import cloudbase from "@cloudbase/js-sdk"; const app = cloudbase.init({ env: "your-full-env-id" });- Do not use dynamic imports like
import("@cloudbase/js-sdk")or async wrappers such asinitCloudBase()with internalinitPromise
- Then proceed with login using a verified method (username/password, phone, email, or WeChat)
-
Environment Management (via manageEnv): The
manageEnvtool provides full lifecycle management for CloudBase environments.Action Description Key Parameters listPackagesQuery available plans (none) createCreate new environment (needs confirm) alias,packageId,resources,duration,region,externalStoragemodifyPlanChange plan (upgrade/downgrade, needs confirm) envId,packageIdrenewRenew environment (needs confirm) envId,durationCreating an environment with specific resources:
manageEnv(action="create", alias="my-env", packageId="baas_personal", resources=["storage","function","postgresql"], confirm="yes")resources(optional, create only): controls which CloudBase capabilities to enable:storage— Cloud Storagefunction— Cloud Functionspostgresql— PostgreSQL relational database (PG mode)
- Defaults to all three when omitted. MCP always sends non-empty
Resourcesto CreateEnv. flexdb(document database) is not offered: new environments are created without a NoSQL tenant. Do not pass it — it is rejected by the schema. To find out whether an environment actually has NoSQL, readqueryEnv(action="info")→EnvInfo.RuntimeBackendsrather than assuming.- Region is selectable: pass
region(e.g.region="ap-shanghai") to choose where the environment is created. It is applied as theX-TC-Regionrequest context, not as a CreateEnv body field — so do not putRegioninsideparams. Omit it to use the current session region (cloudBaseOptions.region→TCB_REGION→ project config / rc binding → site default:ap-shanghaifor the domestic site,ap-singaporefor the intl site). Equivalent CLI:tcb env create --region ap-shanghai. - ⚠️ If you pass
region, repeat the same value on the confirming call together withconfirm="yes"; otherwise the second call falls back to the session region and the environment may be created somewhere other than the summary you confirmed. externalStorage(optional, create only):{ bucketName, region, basePath }creates the environment's cloud storage on an existing shared COS bucket instead of a dedicated one, isolating its files underbasePath(must be unique within the bucket). All three fields are required when the object is passed. Use it only when the user provides the bucket — typically a platform creating many environments under one account, where one bucket per environment would hit the account's COS bucket quota; never invent bucket names. It does not cover static hosting: the hosting bucket is chosen by the platform when hosting is enabled and cannot be set through this tool.- ⚠️ Like
region, repeat the sameexternalStorageon theconfirm="yes"call. The confirming call reads only its own arguments, so leaving it out creates the environment with a dedicated bucket instead.
manageEnv(action="create", alias="tenant-a", packageId="baas_personal", externalStorage={ bucketName: "shared-bucket-1250000000", region: "ap-shanghai", basePath: "tenant-a" }, confirm="yes")- ⚠️ All paid operations (create / modifyPlan / renew) require
confirm="yes".
Querying available packages before creating:
manageEnv(action="listPackages")- ⚠️ That list is filtered to the packages the console offers in its new-purchase / new-environment menus:
baas_personal(个人版),baas_pf_standard(标准版),baas_pf_enterprise(企业版),baas_pf_enterprise_senior(企业高级版),baas_trial(体验版),baas_integration(集成版). Package families (default/basic/trial/vip) do not map onto that set — legacy packages such asstarter(入门版),baas_team(团队版) andenterprise_basic(企业基础版) share families with the current ones and are deliberately excluded. The platform still accepts other validpackageIds, so the actual create result is authoritative.
Changing plan (use a
packageIdfromlistPackages):manageEnv(action="modifyPlan", envId="your-env-id", packageId="<packageId>", confirm="yes")Renewing an environment:
manageEnv(action="renew", envId="your-env-id", duration=1, confirm="yes")
Authentication Best Practices
Important: Authentication methods for different platforms are completely different, must strictly distinguish!
Files in this skill
6cloudbase-platform skill questions
How do I install the cloudbase-platform skill in Claude Code?
Run npx degit TencentCloudBase/CloudBase-AI-Toolkit/config/.claude/skills/cloudbase-platform ~/.claude/skills/cloudbase-platform. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the cloudbase-platform skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
When should I use the CloudBase platform skill?
Use this skill when you need to understand platform concepts, compare capabilities, navigate the console, or understand cross-platform best practices before choosing a specific implementation skill.
How should I handle specific error codes when a CloudBase tool call fails?
Do not guess the meaning; instead, extract the error code and use the searchKnowledgeBase tool to look it up in the official documentation to find the prescribed fix steps.