Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Vmware Vks
v1.4.6Use this skill whenever the user needs to manage Tanzu Kubernetes (VKS) on vSphere — Supervisor clusters, vSphere Namespaces, and TKC cluster lifecycle. Dire...
⭐ 0· 135·0 current·0 all-time
by@zw008
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill is coherently named and describes VMware VKS/Tanzu operations and correctly requires a vmware-vks CLI and a configuration file (~/.vmware-vks/config.yaml). Requiring a vmware-vks binary and a config path is proportionate to the stated purpose. However, the SKILL.md and other reference docs claim companion auto-installs (vmware-policy) and mention audit locations that are inconsistent (e.g., ~/.vmware/audit.db vs ~/.vmware-vks/audit.log). The registry metadata said 'No install spec' while SKILL.md includes an installer block (uv / PyPI). These mismatches are odd but could be sloppy packaging rather than malicious intent.
Instruction Scope
Runtime instructions are primarily 'run the vmware-vks CLI' which is expected. But the SKILL.md and setup guide reference environment variables and secret-handling practices not declared in requires.env (e.g., recommends ~/.vmware-vks/.env with VMWARE_VKS_VCENTER01_PASSWORD, shows VMWARE_MYVENTER_PASSWORD in an MCP example — a clear typo). The docs also reference multiple different audit/log paths. The skill's runtime guidance therefore instructs the agent to read and use configuration and secret locations beyond the single declared VMWARE_VKS_CONFIG, which is a scope creep / clarity problem and could cause the agent to access secrets without them being explicitly declared.
Install Mechanism
Installation guidance points to standard sources (GitHub, PyPI, uv tool), which is reasonable and lower risk than arbitrary downloads. No obscure URL shorteners or personal IPs are used. The inconsistency is that registry metadata listed 'No install spec' while SKILL.md advertises an 'uv' installer and multiple install flows (npx, clawhub, PyPI). This is a packaging/metadata mismatch to resolve but not immediate high-risk behavior.
Credentials
The skill declares a single required env var/primary credential (VMWARE_VKS_CONFIG) and a config path (~/.vmware-vks/config.yaml). However, the setup docs and MCP examples show additional secret envs and files (per-target passwords in ~/.vmware-vks/.env, VMWARE_VKS_VCENTER01_PASSWORD, VMWARE_MYVENTER_PASSWORD) that are not declared as required. The skill under-declares the secrets it will read/use, and the docs contain typos and conflicting names. That mismatch increases the chance credentials will be accidentally provided to the agent or overlooked during review.
Persistence & Privilege
always:false (default) and the documentation states no background services or inbound listeners are started. MCP transport is stdio only. The skill does not request permanent presence or show behavior that would modify other skills or system-wide config. This aspect appears proportionate.
What to consider before installing
This skill appears to be intended for VKS/Tanzu management and uses the vmware-vks CLI, but there are several documentation and metadata inconsistencies you should resolve before trusting it with credentials: (1) Confirm exactly which environment variables and files the runtime will read — the registry lists only VMWARE_VKS_CONFIG, but the setup guide references per-target password envs and a ~/.vmware-vks/.env file. (2) Verify audit/log file locations (the docs mention both ~/.vmware/audit.db and ~/.vmware-vks/audit.log) so you can monitor actions. (3) Prefer installing the CLI from the official GitHub/PyPI repository and review that source tree before running. (4) Do not place cleartext credentials into agent-global env vars; instead use least-privileged accounts and a secrets manager or tightly permissioned ~/.vmware-vks/.env with proper filesystem permissions. (5) Ask the skill author to fix typos (e.g., VMWARE_MYVENTER_PASSWORD) and to update the skill metadata to list all required env vars and the installer method. If the author cannot clarify these points, treat the skill as risky for production use.Like a lobster shell, security has layers — review code before you run it.
latestvk9794228743wb497w6t5jh4sg984atbg
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
☸️ Clawdis
OSmacOS · Linux
Binsvmware-vks
EnvVMWARE_VKS_CONFIG
Config~/.vmware-vks/config.yaml
Primary envVMWARE_VKS_CONFIG