Vmware Avi
v1.4.6Use this skill whenever the user mentions load balancing, ingress, virtual services, pool members, AVI, NSX ALB, AKO, or application delivery. Also trigger w...
⭐ 0· 79·0 current·0 all-time
by@zw008
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
high confidencePurpose & Capability
The skill is targeted at AVI/AKO (virtual services, pool members, AKO, ingress diagnostics). Required items (vmware-avi binary, VMWARE_AVI_CONFIG, ~/.vmware-avi/config.yaml and .env, kubectl/helm/avisdk for AKO or controller operations) match that purpose. No unrelated cloud/provider credentials are requested.
Instruction Scope
SKILL.md instructs the agent to use the vmware-avi CLI and to read the config and .env files, check kubeconfig, and call kubectl/helm/avisdk as needed — all within the stated domain. It does not instruct the agent to read unrelated system files or exfiltrate data to unexpected endpoints. It documents double-confirmation for destructive ops.
Install Mechanism
The skill is instruction-only (no code shipped). SKILL.md recommends installing via 'uv tool install vmware-avi' (uv package) and lists dependencies (avisdk, kubernetes Python lib). The registry metadata lists no platform install spec; installation is performed by external tooling — this is normal but means the user should review the vmware-avi package before installing.
Credentials
The only declared required env var is VMWARE_AVI_CONFIG (path to config.yaml). The runtime uses ~/.vmware-avi/.env to load controller passwords (e.g. PROD_AVI_PASSWORD). Access to those files/vars is proportional for a management CLI, but these are sensitive credentials — user should ensure .env permissions (chmod 600) and use least-privilege controller accounts.
Persistence & Privilege
always:false and model invocation not disabled (normal). The skill expects vmware-policy to be used and writes audit entries to ~/.vmware/audit.db — this is documented and appropriate for auditing. The skill does not request persistent elevated platform privileges or to modify other skills.
Assessment
This skill appears coherent for managing VMware AVI/AKO, but it needs local tooling and access to sensitive controller credentials. Before installing or enabling it: 1) review the vmware-avi package/source you will install (uv tool install will fetch code); 2) ensure ~/.vmware-avi/.env is protected (chmod 600) and contains only least-privilege controller passwords or API tokens; 3) be aware AKO operations require kubectl/helm and may be disruptive (double-confirm prompts are documented for destructive commands); 4) audit ~/.vmware/audit.db is created locally — verify that audit behavior meets your policy; 5) if you want tighter control, run commands manually or inspect the vmware-avi CLI before allowing autonomous agent invocation.Like a lobster shell, security has layers — review code before you run it.
latestvk971h84a74trrbjspzx26d0nbn84bekm
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🔀 Clawdis
OSmacOS · Linux
Binsvmware-avi
EnvVMWARE_AVI_CONFIG
Config~/.vmware-avi/config.yaml, ~/.vmware-avi/.env
Primary envVMWARE_AVI_CONFIG
