Volcengine Security Kms

Key lifecycle management with Volcengine KMS. Use when users need key creation, rotation policies, encryption/decryption workflows, or key permission troubleshooting.

This skill claims to manage Volcengine KMS but is missing essential operational details (authentication and concrete API/CLI steps). Before installing or using it: - Treat it as advisory documentation rather than an actionable integration until the author documents auth and invocation details. - Ask the publisher to declare required credentials (e.g., VOLCENGINE_ACCESS_KEY_ID, VOLCENGINE_SECRET_ACCESS_KEY, REGION/ENDPOINT) and the minimum IAM permissions needed for each operation. - Do not expose high-privilege or long-lived keys to the agent; prefer least-privilege scoped credentials or ephemeral roles. - If you intend to let the agent perform real KMS operations, test in a non-production account with narrowly scoped permissions and audit logs enabled. - If the skill will run autonomously with access to credentials, require explicit confirmation and review of the credential scope first. If the author clarifies that the skill is purely a checklist/documentation (no runtime API calls), it would be lower risk; if it is intended to perform real KMS operations, the current lack of declared credentials/config is a red flag and should be corrected.

Type: OpenClaw Skill Name: volcengine-security-kms Version: 1.0.0 The skill bundle defines an OpenClaw agent skill for Volcengine KMS key management. All files, including `SKILL.md` (which contains instructions for the AI agent), are aligned with the stated purpose. There is no evidence of malicious prompt injection, unauthorized data access, external communication, or code execution. The `SKILL.md` even includes 'Safety Rules' promoting secure handling of secrets and permissions, indicating a focus on secure operation rather than malicious intent.