Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Alibabacloud Solution Deploy
v0.0.2Deploy Alibaba Cloud official tech solutions. Trigger when the user mentions an Alibaba Cloud solution, pastes a solution URL (aliyun.com/solution/tech-solut...
⭐ 0· 46·0 current·0 all-time
byalibabacloud-skills-team@sdk-team
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Suspicious
high confidencePurpose & Capability
Name/description match the files and scripts: the skill searches Alibaba Cloud solution catalogs, calls OpenAPI Explorer, and can deploy Terraform modules via IaCService. However the registry metadata declares no required environment variables or primary credential even though the skill clearly requires Alibaba Cloud credentials (AK/SK, STS, or ECS role) and RAM permissions to operate. That mismatch (claimed no credentials vs. actual need) is inconsistent.
Instruction Scope
SKILL.md explicitly instructs the agent to read local configuration (~/.aliyun/config.json or env vars), run verify_env.sh, call Alibaba Cloud OpenAPI endpoints, fetch module examples from GitHub raw URLs, generate HCL and call a remote IaCService to apply/destroy infrastructure. These actions are coherent with the stated purpose but involve reading local credentials/config and writing state files (e.g., terraform_state_ids.env). The instructions do include user confirmation points (plan → present → confirm → apply), which is good, but they also direct the agent to run many automated commands that will use your credentials.
Install Mechanism
There is no install spec (instruction-only), which reduces installation risk. However the provided Python scripts import Alibaba Cloud SDK packages (alibabacloud_tea_openapi, alibabacloud_credentials, alibabacloud_openapi_util, etc.) and the shell scripts expect an aliyun CLI >=3.3.x and Bash. These runtime dependencies are not declared in registry metadata; the skill will fail or behave unexpectedly if the environment lacks those SDKs/tools.
Credentials
The skill requires access to Alibaba Cloud credentials and requests RAM permissions that include openapiexplorer actions and broad IaCService actions (Validate/ExecuteApply/ExecuteDestroy) with Resource="*" (see references/ram-policies.md). Those permissions are consistent with deploying arbitrary solutions, but they are powerful (can create/destroy resources and bill your account). The registry metadata declaring no required env vars or primary credential is a clear inconsistency. Also the recommended IAM policy is wide (Resource "*") — you should prefer least-privilege bindings.
Persistence & Privilege
always:false and the skill does not claim system-wide persistence. The scripts write local artifacts (STATE_IDs to terraform_state_ids.env) and may modify ~/.aliyun/config.json via aliyun configure if the user runs those commands, which is expected for a deploy tool. The skill does not try to alter other skills' configs or enforce permanent inclusion.
What to consider before installing
This skill appears to do what it says (search solutions, generate parameters, and deploy via Alibaba Cloud CLI/IaCService), but there are important concerns you should address before installing:
- Credentials: The skill metadata claims no required env vars, yet SKILL.md and the scripts require Alibaba Cloud credentials (AK/SK, STS token, or ECS RAM role) and will read ~/.aliyun/config.json or environment variables. Do not enable this skill with your production root credentials. Use a dedicated RAM user or temporary STS credentials.
- Permissions: The provided RAM policy includes powerful iacservice:* and openapiexplorer:* actions with Resource "*". If you proceed, attach the minimal necessary permissions and test in a sandbox account to avoid unexpected charges or resource creation.
- Dependencies: The Python scripts rely on Alibaba Cloud SDK packages and the runtime requires aliyun CLI >=3.3.x. Ensure those are present in a controlled environment. Ask the publisher to list these as required dependencies in metadata.
- State & cost: The skill will create cloud resources and save STATE_IDs locally; review and retain state IDs for teardown. Always review plans and explicitly confirm before apply — SKILL.md says to prompt the user, but confirm this behavior in practice.
- Source & trust: The source/owner in the registry is opaque. If you don't recognize the publisher, request provenance (GitHub repo, homepage) and inspect the scripts yourself. Prefer running this in a test/sandbox Alibaba account first.
- Ask for fixes: Request that the publisher update the skill metadata to declare required env vars (ALIBABA_CLOUD_ACCESS_KEY_ID / ALIBABA_CLOUD_ACCESS_KEY_SECRET or note ECS RAM role), and list runtime Python and CLI dependencies, and narrow recommended IAM permissions.
If you accept those conditions and test in a non-production account with least-privilege credentials, the skill's behavior is understandable for its stated purpose; otherwise treat it as risky.Like a lobster shell, security has layers — review code before you run it.
latestvk97747jwza782r3bm06vcxabh184kv79
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
