cloudmonkey
WarnAudited by ClawScan on May 10, 2026.
Overview
This is a legitimate CloudStack administration skill, but it gives the agent broad command-line control over cloud resources and local cmk profiles with limited scoping.
Use this only if you intend to let the agent administer CloudStack. Before any action, confirm the active cmk profile, target environment, resource IDs, and exact command, and require approval for all changes that start, stop, delete, create, attach, detach, or reconfigure cloud resources.
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.
The agent could disrupt or delete cloud resources, alter networking or storage, or run an unexpected CloudStack API command if the user gives an ambiguous request or the wrong target is selected.
This grants broad raw CLI/API authority over cloud infrastructure, including destructive and disruptive operations, without clear scope limits for which resources, environments, or non-destructive mutations require approval.
"Manage Apache CloudStack infrastructure ... list/start/stop/destroy VMs, manage networks, volumes, snapshots, and run any CloudStack API command."
Require explicit user confirmation for every state-changing command, not only destroy/expunge; confirm the active profile, account, project, zone, resource IDs, and expected effect before running cmk commands.
Commands could run under the wrong CloudStack profile or account, potentially affecting the wrong environment, tenant, or production resources.
The skill relies on local CloudMonkey profiles that represent different CloudStack environments and allows profile switching, but it does not bound which profile may be used or require confirming the active identity before privileged operations.
"CloudMonkey supports multiple profiles ... `cmk set profile <name>` ... Config is stored in `~/.cmk/config`"
Declare the cmk profile/config dependency, use least-privilege CloudStack credentials, and require the user to choose and confirm the active profile before any listing or mutation.
Users have less information to verify who authored the skill or where to inspect its history, even though the reviewed artifact is only an instruction file.
The skill has no code or install step, which lowers supply-chain risk, but the published source and homepage are not provided, so provenance is limited.
"Source: unknown" and "Homepage: none"
Install only if you trust the registry entry, and independently verify that the local cmk binary comes from the official Apache CloudMonkey distribution.