From bcf74bb91a41749f80eb2c111832ed05ea8e7877 Mon Sep 17 00:00:00 2001
From: lolwierd <lolwierd@outlook.com>
Date: Tue, 28 Apr 2026 11:52:41 +0530
Subject: [PATCH] Remove compute instances list reference

---
 skills/excloud-cli/SKILL.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/skills/excloud-cli/SKILL.md b/skills/excloud-cli/SKILL.md
index b3241ef..59305a1 100644
--- a/skills/excloud-cli/SKILL.md
+++ b/skills/excloud-cli/SKILL.md
@@ -121,7 +121,6 @@ Typical progression for a fresh VM: `CREATING` → `STARTING` → `RUNNING` in r
 ### Inspect and control
 
 - `exc compute list` — hides `TERMINATED` VMs by default. Use this for "what is alive now".
-- `exc compute instances list` — rich-metadata variant that shows **all** states unless filtered; add `--states running,stopped`, `--created_after <rfc3339>`, `--created_before <rfc3339>` as appropriate.
 - `exc compute get --id <vm_id>` — single VM detail. Shows `INTERFACE_ID` (needed for publicip / SG binding ops) but not `ROOT_VOLUME_ID`.
 - `exc compute rename --vm_id <id> --name <new_name>`
 - `exc compute resize --vm_id <id> --instance_type <type>` — generally requires the VM to be STOPPED first.
@@ -297,7 +296,7 @@ exc compute volume list             # the root volume should disappear / move to
 
 Every command either prints a column table (or TSV) or prints JSON — no command should print raw Go-struct dumps anymore. Both shapes are machine-parseable; pick your tool accordingly.
 
-- **Column tables / TSV** (awk / `cut` / `awk -F\t` friendly): `compute list`, `compute instances list`, `compute get`, `compute create`, `compute terminate` (TSV `vm_id\tstate`), `compute instancetype list` / `capacity`, `compute image list`, `compute subnet list`, `compute volume list`, `compute volume get`, `compute snapshot list`, `compute publicip list`, `compute key list`, `securitygroup list` / `rule list` / `binding list`, `org list`, `account list`, `apikey list`, `policy list`, `config list`, `compute seriallogs`.
+- **Column tables / TSV** (awk / `cut` / `awk -F\t` friendly): `compute list`, `compute get`, `compute create`, `compute terminate` (TSV `vm_id\tstate`), `compute instancetype list` / `capacity`, `compute image list`, `compute subnet list`, `compute volume list`, `compute volume get`, `compute snapshot list`, `compute publicip list`, `compute key list`, `securitygroup list` / `rule list` / `binding list`, `org list`, `account list`, `apikey list`, `policy list`, `config list`, `compute seriallogs`.
 - **JSON** (pipe through `jq`): `me`, `quota`, `billing get`, `compute health` (`{"raw":"OK"}`), `k8s health`, `compute subnet get`, `compute publicip get`, `compute key get`, `securitygroup get`, `compute metrics`, `compute connect`, `serviceaccount list`, `compute protect`, `compute unprotect`, `compute rename`, `k8s cluster kubeconfig get` (raw kubeconfig YAML, not JSON-wrapped), and the inline `kubeconfig` field inside the JSON response from `k8s cluster create` when `-o` is not set.
 
 Before scripting heavy logic against a command, run it once and check the shape. The split between "table" and "JSON" is not always guessable — lists tend to be tables, getters tend to be JSON, but verify.