Huawei Cloud Capability Discovery
STOP - Do not answer from general knowledge. Follow the procedure below.
Use this skill to turn vague developer intent into a precise Huawei Cloud capability path.
Workflow
- Classify the goal: application hosting, compute, container, serverless, storage, database, network, security, observability, AI, data, migration, cost, or troubleshooting.
- Search Huawei Cloud Skills first when the task is scenario-based or operational.
- Use official docs for exact service limits, API request/response fields, regions, and pricing-sensitive behavior.
- Prefer KooCLI for local read-only discovery after auth is configured.
- Before using KooCLI, discover exact operation names with
hcloud <Service> --help; do not guess from intuition. Examples: list ECS instances with ECS ListServersDetails, create ECS with ECS CreateServers, inspect images through IMS GlanceShowImage.
- Prefer SDK docs when the deliverable is application code.
- Prefer MCP only when an approved Huawei Cloud MCP tool exists for the needed operation.
- Treat Terraform as a secondary V1 path for reviewed IaC, not the default.
- When no built-in devkit skill matches:
a. Search: use
huaweicloud_search_marketplace to find a matching skill in the community marketplace
b. Install: run npx skills add huaweicloud/huaweicloud-skills --skill <skill-name> -y -g
c. Execute: load the installed skill and follow its procedure
- When the deliverable is a PPT, architecture diagram (draw.io), or frontend page that needs official Huawei Cloud service logos, use the
huaweicloud_get_service_icon MCP tool to get logo URLs from the official Icons library instead of guessing or hotlinking unofficial images.
Scenario Routing
Match the scenario before picking a service. For "deploy a web app" requests, layer the recommendation instead of defaulting to a production service:
| Scenario |
Recommended path |
| hello world / prototype / demo / temporary preview (free, quick try) |
huawei-sandbox first — temporary runtime + public URL (runtime lifetime not exposed via API); credential expiry see expiresAt from connect/credentials, zero billed resources |
| production / long-term / custom domain / high availability |
huawei-functiongraph / huawei-ecs (or huawei-cce for containers) |
Route to the sandbox when the developer signals free/quick preview intent ("免费", "快速", "预览", "hello world", "原型", "演示"); route to production services only when production-grade hosting is explicitly required.
Official Service Logos
- Use
huaweicloud_get_service_icon with the service name, alias, or Chinese name (e.g. ecs, obs, modelarts, 对象存储). It returns the official CDN logo URL (logo.source_url), category, and product page link from https://open.huaweicloud.com/openplatform/icons.html.
- Prefer
logo.source_url for web deliverables and the Icons library search page for browsing; do not scrape logos from third-party sites.
Deployment Target Options
When the intent is to deploy, host, or preview a web app or static website and the developer has not named a target, do NOT default to OBS or any single service. Present the options and let the developer choose, recommending the sandbox first: ① huawei-sandbox (recommended — temporary runtime, instant preview URL) ② huawei-obs (long-term static hosting/CDN) ③ huawei-ecs ④ huawei-cce. Only follow an explicit target when the developer names one.
Region Intent
- Extract region intent from the user's words before querying. Examples: Singapore ->
ap-southeast-3 first, Hong Kong -> ap-southeast-2, Beijing -> cn-north-4, Shanghai -> cn-east-3.
- Target operation region wins over reference-resource uncertainty. If the user says "buy ECS in Singapore, reference SSY", inspect Singapore first.
- No blind all-region scans. If the reference resource location is unknown and the target region is not enough, ask the user for the region instead of scanning unrelated regions.
- For unfamiliar names, check Huawei Cloud API Explorer or official endpoint documentation for the region and service endpoint mapping.
Output Format
When routing a task, return:
intent: one concise sentencerecommended_path: Skills, CLI, API, SDK, MCP, or Terraformwhy: why this path is shortest and safestnext_action: exact next command, document lookup, or code file to inspectrisk: read-only, write, secret, permission, cost, or public exposure
Avoid
- Do not guess a service when Huawei Cloud Skills or official docs should be checked.
- Do not load many service references. Pick the next one that matches the intent.
- Do not propose write operations before the user has seen the plan.
- Do not query every region just to find a reference resource.
1---2name: huaweicloud-capability-discovery3description: Discover Huawei Cloud capabilities for an agent task. Use when the user asks what Huawei Cloud service, Skill, CLI command, API, SDK, or document should be used, or when a request is scenario-shaped and needs capability selection before implementation.4---56# Huawei Cloud Capability Discovery78**STOP - Do not answer from general knowledge.** Follow the procedure below.910Use this skill to turn vague developer intent into a precise Huawei Cloud capability path.1112## Workflow13141. Classify the goal: application hosting, compute, container, serverless, storage, database, network, security, observability, AI, data, migration, cost, or troubleshooting.152. Search Huawei Cloud Skills first when the task is scenario-based or operational.163. Use official docs for exact service limits, API request/response fields, regions, and pricing-sensitive behavior.174. Prefer KooCLI for local read-only discovery after auth is configured.185. Before using KooCLI, discover exact operation names with `hcloud <Service> --help`; do not guess from intuition. Examples: list ECS instances with `ECS ListServersDetails`, create ECS with `ECS CreateServers`, inspect images through `IMS GlanceShowImage`.196. Prefer SDK docs when the deliverable is application code.207. Prefer MCP only when an approved Huawei Cloud MCP tool exists for the needed operation.218. Treat Terraform as a secondary V1 path for reviewed IaC, not the default.229. When no built-in devkit skill matches:23 a. Search: use `huaweicloud_search_marketplace` to find a matching skill in the community marketplace24 b. Install: run `npx skills add huaweicloud/huaweicloud-skills --skill <skill-name> -y -g`25 c. Execute: load the installed skill and follow its procedure2610. When the deliverable is a PPT, architecture diagram (draw.io), or frontend page that needs official Huawei Cloud service logos, use the `huaweicloud_get_service_icon` MCP tool to get logo URLs from the official Icons library instead of guessing or hotlinking unofficial images.2728## Scenario Routing2930Match the scenario before picking a service. For "deploy a web app" requests, layer the recommendation instead of defaulting to a production service:3132| Scenario | Recommended path |33| -------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |34| hello world / prototype / demo / temporary preview (free, quick try) | `huawei-sandbox` first — temporary runtime + public URL (runtime lifetime not exposed via API); credential expiry see `expiresAt` from `connect`/`credentials`, zero billed resources |35| production / long-term / custom domain / high availability | `huawei-functiongraph` / `huawei-ecs` (or `huawei-cce` for containers) |3637Route to the sandbox when the developer signals free/quick preview intent ("免费", "快速", "预览", "hello world", "原型", "演示"); route to production services only when production-grade hosting is explicitly required.3839## Official Service Logos4041- Use `huaweicloud_get_service_icon` with the service name, alias, or Chinese name (e.g. `ecs`, `obs`, `modelarts`, `对象存储`). It returns the official CDN logo URL (`logo.source_url`), category, and product page link from https://open.huaweicloud.com/openplatform/icons.html.42- Prefer `logo.source_url` for web deliverables and the Icons library search page for browsing; do not scrape logos from third-party sites.4344## Deployment Target Options4546When the intent is to **deploy, host, or preview a web app or static website** and the developer has not named a target, do NOT default to OBS or any single service. Present the options and let the developer choose, recommending the sandbox first: ① huawei-sandbox (recommended — temporary runtime, instant preview URL) ② huawei-obs (long-term static hosting/CDN) ③ huawei-ecs ④ huawei-cce. Only follow an explicit target when the developer names one.4748## Region Intent4950- Extract region intent from the user's words before querying. Examples: Singapore -> `ap-southeast-3` first, Hong Kong -> `ap-southeast-2`, Beijing -> `cn-north-4`, Shanghai -> `cn-east-3`.51- Target operation region wins over reference-resource uncertainty. If the user says "buy ECS in Singapore, reference SSY", inspect Singapore first.52- No blind all-region scans. If the reference resource location is unknown and the target region is not enough, ask the user for the region instead of scanning unrelated regions.53- For unfamiliar names, check Huawei Cloud API Explorer or official endpoint documentation for the region and service endpoint mapping.5455## Output Format5657When routing a task, return:5859- `intent`: one concise sentence60- `recommended_path`: Skills, CLI, API, SDK, MCP, or Terraform61- `why`: why this path is shortest and safest62- `next_action`: exact next command, document lookup, or code file to inspect63- `risk`: read-only, write, secret, permission, cost, or public exposure6465## Avoid6667- Do not guess a service when Huawei Cloud Skills or official docs should be checked.68- Do not load many service references. Pick the next one that matches the intent.69- Do not propose write operations before the user has seen the plan.70- Do not query every region just to find a reference resource.
huaweicloud