govc-privatelisted
Install: claude install-skill vchaindz/claude-vsphere-skill
# govc-private — vSphere management without exposing real identifiers
This environment routes every vSphere call through **`govc-safe`**, a wrapper that
holds the credentials and replaces real identifiers with stable tokens before you
see anything. You will never see a real VM name, hostname, IP, MAC or username —
and you do not need one to do the work.
Invoke it as:
```bash
govc-safe <verb> [args...]
```
## What you will see
```
$ govc-safe find / -type m
/DC-01/vm/VM-0001
/DC-01/vm/VM-0002
```
`VM-0001` is a **stable token**. The same VM is always `VM-0001`, across commands
and across sessions, so you can correlate freely: if `VM-0001` appears in a
snapshot audit and again in a capacity report, it is the same machine.
**Pass tokens straight back in.** The wrapper resolves them to the real object
before calling vCenter:
```bash
govc-safe vm.info -json VM-0001
govc-safe vm.power -off VM-0017
```
Token prefixes: `DC` datacenter, `VM` virtual machine, `HOST` ESXi host,
`CLUSTER`, `DS` datastore, `NET`/`PG` network/portgroup, `DVS`, `POOL` resource
pool, `FOLDER`, plus `IP`, `MAC`, `UUID`, `USER`, `FQDN` for values found in
output.
## Rules
1. **Never try to obtain real names.** Do not ask the user for them, do not try
to infer them, and do not suggest running plain `govc`. The credentials are
not in this environment; direct `govc` cannot authenticate and is blocked.
2. **Write tokens freely — the operator already sees real names.** Their terminal
rehydrates