Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Alibabacloud Sdk Client Initialization For Python
v0.0.1-betaInitialize and manage Alibaba Cloud SDK clients in Python. Covers singleton pattern, thread safety, endpoint vs region configuration, VPC endpoints, async mo...
⭐ 0· 50·0 current·0 all-time
by@yndu13
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
The skill's name and description (Alibaba Cloud SDK client initialization) match the instructions in SKILL.md. However, the skill metadata declares no required environment variables or credentials even though the provided examples directly read ALIBABA_CLOUD_ACCESS_KEY_ID and ALIBABA_CLOUD_ACCESS_KEY_SECRET from the environment. That metadata omission is an incoherence — if the skill is intended to run code that creates SDK clients, it legitimately needs credentials and should declare them.
Instruction Scope
SKILL.md includes runnable Python code that reads os.environ['ALIBABA_CLOUD_ACCESS_KEY_ID'] and os.environ['ALIBABA_CLOUD_ACCESS_KEY_SECRET'] (and also shows os.environ.get in another example). Reading these secrets is directly relevant to initializing SDK clients, but the instructions do not handle missing credentials safely (one example uses direct indexing which raises if unset). The doc does not instruct the agent to access unrelated files, but it does implicitly require access to sensitive environment variables not advertised in the metadata.
Install Mechanism
This is an instruction-only skill with no install spec or code files (lowest install risk). The SKILL.md recommends installing packages via pip (alibabacloud-tea-openapi and product SDKs). Pip installs from PyPI are common and expected for a Python SDK guide; they carry moderate supply-chain risk but are proportional to the stated purpose.
Credentials
The only sensitive items referenced are standard Alibaba Cloud access keys, which are proportionate to SDK initialization. The problem is the metadata declares no required env vars or primary credential while the instructions clearly rely on them. This mismatch raises the risk that credentials could be requested or accessed without clear user expectation. Also one code example uses os.environ[...] (KeyError risk) rather than safe retrieval patterns.
Persistence & Privilege
The skill does not request always:true, does not modify other skills, and has no install actions that persist code on disk. Autonomous invocation is allowed (platform default) but that alone is not a problem; combined with the undocumented credential access it does increase potential blast radius and should be considered by the user.
What to consider before installing
This skill appears to be a legitimate SDK initialization guide, but it references ALIBABA_CLOUD_ACCESS_KEY_ID and ALIBABA_CLOUD_ACCESS_KEY_SECRET inside the examples while the skill metadata lists no required credentials — that's an inconsistency you should resolve before use. Before installing or running code from this skill: (1) ask the publisher to declare required env vars/credentials explicitly; (2) never provide long-lived root credentials — use least-privilege RAM users or instance/RAM roles; (3) avoid pasting secrets into interactive chats or allowing the agent to fetch them without explicit consent; (4) if you run the provided code, test in an isolated environment with disposable credentials; and (5) prefer the examples that use safe retrieval (os.environ.get or explicit config) and handle missing credentials rather than ones that will raise and potentially leak debug info. If the skill will be allowed to run autonomously, require explicit user confirmation before it can access or request credentials.Like a lobster shell, security has layers — review code before you run it.
latestvk978zp1ragb0bg282skxz6jz4583kzda
License
MIT-0
Free to use, modify, and redistribute. No attribution required.