alibabacloud-sdk-usage

# Alibaba Cloud SDK Usage Use the local `alibabacloud-core` MCP server tools before writing Alibaba Cloud interaction code. Do not start another MCP server or call `aliyun` directly from the shell. Use the MCP Core tools (`AlibabaCloud___SearchApis`, `AlibabaCloud___ListApis`, `AlibabaCloud___GetApiDefinition`, `AlibabaCloud___GenerateCLICommand`, `AlibabaCloud___CallCLI`) to resolve metadata. Do not guess product codes, SDK packages, request models, endpoints, or parameter casing. ## Scope Check Before You Start This skill generates **SDK code that calls a small number of APIs**. If the user's request is instead an **operational pattern** that likely has a packaged solution — batch operations, audits, rotations, scheduled cleanup, multi-step runbooks — invoke `alibabacloud-find-skills` first to search the official catalog. Falling back to SDK synthesis is appropriate only after `find-skills` returns no match. Full trigger conditions are in `mcp-core-best-practices` → Skill Discovery. ## Workflow 1. Inspect the local project first. - Detect the target language from project files (`pyproject.toml`, `requirements*.txt`, `package.json`, `go.mod`, `pom.xml`, `build.gradle`, `.csproj`, `composer.json`, `Package.swift`, etc.). - Check whether Alibaba Cloud SDK dependencies are already installed or declared. - Check existing Alibaba Cloud call style. If the project uses generic `call_api` / common OpenAPI calls, continue with `callType=generic`. ...