Skills/ClawHub/huawei-cloud-product-list

huawei-cloud-product-list@1.0.7

CAUTION

Publisher claims: "1. List the Huawei Cloud product (service) catalog — the 云服务类型 directory — through KooCLI (hcloud BSS ListServiceTypes, read-only GET /v2/products/service-types), with an automatic fallback to the official huaweicloudsdkbss v2 SDK when hcloud is not installed or the CLI metadata lacks the BSS service. 2. Every catalog item carries the product name (service_type_name / 名称), its service type code (service_type_code / 编码) and its abbreviation (abbreviation / 缩写), so users can browse the对外开放 Huawei Cloud product line in one call. 3. Three output modes: table (default — 名称 / 编码 / 缩写), --json (raw response array with every returned field), and --names-only (compact product name list). Output is written to stdout only (errors go to stderr). 4. Supports --name (server-side fuzzy match on the service type name), --code (client-side match on the service type code), region override, page-size, and automatic offset paging. 5. Explicit error hints for an empty catalog (「未查询到华为云产品（服务）目录数据」), 403 / insufficient IAM permission (「无权限访问华为云产品目录…，请检查 IAM 权限」), missing or invalid AK/SK credentials, and hcloud not installed. 6. Built-in write-intent guard: any mutating intent (create / delete / update / modify / transfer / reclaim / adjust / freeze / send / issue / cancel ...) or any operation other than ListServiceTypes is rejected before execution — this skill is strictly read-only. 7. Triggers include: "华为云产品列表", "产品目录", "服务目录", "云服务类型", "华为云有哪些产品", "list huawei cloud products", "service catalog", "product catalog", "list cloud services", "huawei cloud service types". 8. Offline unit tests (mocked hcloud subprocess) cover output modes, filters, paging, error scenarios, SDK fallback, standardization, and the write-intent guard." Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher wlc-dev · joined 14 days agoInstalls 0Last detonated 1 h ago
What would fix thisWatchDispute verdict

Is [email protected] safe to install?

KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-05 and scored it 65/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: static analysis only — behavior not yet observed.

Behavior trace

Queued for honeypot run · static analysis only
t+CategoryObserved action

This version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.

Static findings

MEDIUM
Python subprocess execution detectedscripts/ensure_env.py:56 · Python subprocess execution detectedFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
Python subprocess execution detectedscripts/list_products.py:232 · Python subprocess execution detectedFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05

What would make this Verified

15 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim wlc-dev: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
  3. Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
Publish a new version to ClawHub, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim wlc-dev