Aliyun Use
Analysis
This appears to be a straightforward Aliyun LLM and translation wrapper, with expected API key and external data-sharing considerations.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
Source: unknown; Homepage: none
The artifacts do not provide a source repository or homepage, which limits independent provenance checks even though the included code is coherent with the stated purpose.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
key = api_key or os.environ.get("ALIYUN_BAILIAN_API_KEY") ... "Authorization": f"Bearer {key}", "x-api-key": keyThe skill reads an Aliyun API key and sends it as an authentication credential, which is expected for this integration but gives access to the user's provider account or quota.
Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.
payload = {"model": model, "messages": anthropic_messages, ...}; response = requests.post(api_url, headers=headers, json=payload, timeout=60)The skill transmits chat messages or translation text to the configured external API endpoint, which is central to its purpose but means user content leaves the local environment.
