Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Alicloud Security Kms
v1.0.3Manage Alibaba Cloud Key Management Service (KMS) via OpenAPI/SDK. Use whenever the user needs key lifecycle/resource operations, policy/configuration change...
⭐ 0· 1.1k·2 current·2 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill's stated purpose is Alibaba Cloud KMS management and the runtime instructions clearly require Alibaba Cloud credentials and access to OpenAPI metadata; that capability is coherent with the name and description. However, the registry metadata lists no required environment variables or primary credential even though SKILL.md requires ALICLOUD_ACCESS_KEY_ID / ALICLOUD_ACCESS_KEY_SECRET (and optionally ALICLOUD_REGION_ID) or a shared credentials file. The omission is an inconsistency between claimed requirements and declared requirements.
Instruction Scope
SKILL.md gives narrow, expected instructions: discover API metadata, use SDK/OpenAPI to call KMS APIs, save outputs to output/alicloud-security-kms/, and prefer least-privilege credentials. It does not instruct reading unrelated system files or exfiltrating data to unusual endpoints. The only external network access is to api.aliyun.com for API metadata, which matches the skill purpose.
Install Mechanism
No install spec is provided (instruction-only) and the only included code is a small Python script that fetches OpenAPI metadata from api.aliyun.com and writes JSON/MD to the local output directory. No downloads of arbitrary code, no archive extraction, and no non-standard binary installation are present.
Credentials
The SKILL.md expects sensitive credentials (ALICLOUD_ACCESS_KEY_ID and ALICLOUD_ACCESS_KEY_SECRET) and references a shared config path (~/.alibabacloud/credentials). Those are appropriate and proportionate for a KMS management skill, but they are not declared in the skill's metadata (required env vars / primary credential). That mismatch makes it unclear to the platform or user what secrets will be requested or needed.
Persistence & Privilege
The skill does not request always:true, does not declare system-wide config changes, and is user-invocable with autonomous invocation allowed (the platform default). There is no evidence the skill tries to persist itself beyond normal outputs in its own output directory.
What to consider before installing
This skill's code and instructions are consistent with an Alibaba Cloud KMS helper, but its registry metadata fails to declare that it needs your Alibaba Cloud access key and secret. Before installing or invoking: (1) treat this as a skill that will require your ALICLOUD_ACCESS_KEY_ID and ALICLOUD_ACCESS_KEY_SECRET — only provide least-privilege credentials (prefer read-only or limited KMS permissions) and avoid long-lived full-admin keys; (2) review the included script locally to confirm it only fetches api.aliyun.com metadata (it does); (3) run first in a sandbox or with test account/keys; (4) ask the publisher to update the skill metadata to list the required env vars and primary credential so the platform can surface the exact secret requests; and (5) for any mutating operations, confirm region and ask the agent to prompt you before performing changes.Like a lobster shell, security has layers — review code before you run it.
latestvk97dtvfwdt8k7xm8j306f5xc6982q192
License
MIT-0
Free to use, modify, and redistribute. No attribution required.