Vmware Nsx Security

This skill appears to do what it says (NSX DFW, groups, tags, traceflow, IDPS), but there are several metadata vs. documentation mismatches you should resolve before installing: - Verify source and package integrity: SKILL.md recommends 'uv tool install vmware-nsx-security' but the registry has no install spec. Confirm the uv package origin (GitHub repo, checksums/signatures) before running it. - Confirm how credentials are supplied: the registry lists only VMWARE_NSX_SECURITY_CONFIG (a config path) as required, but the docs instruct use of environment variables like VMWARE_NSX_SECURITY_<TARGET>_PASSWORD and a ~/.vmware-nsx-security/.env file. Ask the maintainer (or inspect the package) to confirm which env vars the binary actually reads and whether any secrets are sent anywhere unexpected. - Audit/log path mismatch: the header mentions auditing to ~/.vmware/audit.db while the setup guide mentions ~/.vmware-nsx-security/audit.log. Check where audit logs are written and ensure they don't contain secrets and are appropriately permissioned. - Principle of least privilege: create/assign a dedicated NSX account with just the necessary DFW permissions (avoid global admin). Confirm the CLI honors password-only-in-env guidance and doesn't persist plaintext passwords into config files. - If you plan to enable MCP/autonomous invocation, be extra cautious: autonomous agents invoking this skill could make destructive changes. Keep always:false if you want to avoid forced inclusion, and restrict which agents/contexts may call the skill. If you can, obtain (or inspect) the actual vmware-nsx-security package/binary source and confirm the env var usage and network endpoints before installing. If you cannot verify those details, treat the inconsistent metadata as a potential risk and consider running the tool in a restricted environment or sandbox first.