Alibabacloud Openclaw Ecs Dingtalk

This skill appears to do what it claims (create ECS resources, get a Bailian API key via aliyun maas, and configure the DingTalk connector), but the registry metadata omits important runtime requirements. Before installing or running: - Confirm the 'aliyun' CLI is installed and that you are comfortable providing/using Alibaba Cloud credentials (RAM user or AccessKey). The skill expects the CLI and cloud credentials even though metadata lists none. - Do NOT attach broad FullAccess policies in production. Prefer the provided least-privilege custom RAM policy and scope resources where possible. - Understand that the skill will create and delete cloud resources and will run remote commands on created instances (ecs:RunCommand). Run it first in a throwaway/test account or sandbox to validate behavior. - Verify how the Bailian API key and DingTalk secrets will be stored and rotated after creation. The skill will create API keys via the CLI; ensure you collect/store them securely and rotate them if exposed. - Because the package origin is unknown and there are no code files, prefer to obtain an official source (repository, documentation, or publisher identity) before trusting automated actions. If you need higher confidence, ask the publisher for: the source repo link, signed release, or an explanation why required binaries/credentials are not declared in metadata. Confidence in this assessment is medium because the instructions themselves are coherent with the declared purpose, but metadata omissions and the potential for overly-broad IAM choices are red flags that should be resolved before trusting the Skill in a production environment.