sandbox-cli:cluster-list
This skill should be used when the user asks to "list clusters", "show all clusters", "list sandbox clusters", "show registered clusters", "what clusters are available", or "cluster list".
Best use case
sandbox-cli:cluster-list is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
This skill should be used when the user asks to "list clusters", "show all clusters", "list sandbox clusters", "show registered clusters", "what clusters are available", or "cluster list".
Teams using sandbox-cli:cluster-list should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/cluster-list/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How sandbox-cli:cluster-list Compares
| Feature / Agent | sandbox-cli:cluster-list | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
This skill should be used when the user asks to "list clusters", "show all clusters", "list sandbox clusters", "show registered clusters", "what clusters are available", or "cluster list".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
--- context: main --- # Skill: cluster-list **Name:** Sandbox Cluster List **Description:** List all OCP shared clusters registered with the RHDP Sandbox API. --- ## Purpose Display all registered OCP shared clusters with their status, API URLs, owners, and active placement counts. This is useful for getting an overview of cluster inventory, identifying idle or unreachable clusters, and finding a cluster to onboard/offboard/rotate. ## Workflow ### Step 1: Verify Prerequisites Check that sandbox-cli is installed: ```bash which sandbox-cli ``` If sandbox-cli is not installed, tell the user to run `/sandbox-cli:sandbox-setup` first and stop. ### Step 2: Verify Red Hat VPN Connection **CRITICAL:** Always verify VPN connectivity before any sandbox-cli operation. ```bash host squid.redhat.com ``` **If the DNS resolves** (returns an IP address like `10.x.x.x`), the user is on VPN. Proceed. **If it fails** with `NXDOMAIN`, `not found`, or `connection timed out`, STOP and tell the user: > You are NOT connected to the Red Hat VPN. The sandbox API is IP-restricted and all commands will fail with EOF errors. Please connect to the Red Hat VPN before proceeding. Do NOT proceed until VPN is confirmed. ### Step 3: Check Authentication ```bash sandbox-cli status ``` If not authenticated or token expired, tell the user to re-login: ```bash sandbox-cli login --server <SERVER_URL> --token <TOKEN> ``` ### Step 4: List All Clusters ```bash sandbox-cli cluster list ``` Expected output: ``` NAME VALID API_URL CREATED_BY PLACEMENTS cluster-9nj2n yes https://api.cluster-9nj2n.dynamic.redhatworkshops.io:6443 gucore 0 / 40 cluster-nlkxj yes https://api.cluster-nlkxj.dynamic.redhatworkshops.io:6443 judd 2 / 10 ocpv08 yes https://api.ocpv08.dal10.infra.demo.redhat.com:6443 310 / ? cnv-us-south-ocp-1 NO https://api.cnv-us-south-ocp-1.rhdp.net:6443 1 / ? cluster-ld7tc yes https://api.cluster-ld7tc.dynamic.redhatworkshops.io:6443 ritesh 0 / ? ``` ### Step 5: Summarize for the User Present the cluster list and highlight: - **Total cluster count** - **Healthy clusters** (`VALID = yes`) - **Unreachable clusters** (`VALID = NO`) -- flag these for attention - **Clusters with active placements** vs idle clusters - **Clusters at or near capacity** (placements close to max) ## Output Columns | Column | Description | |--------|-------------| | **NAME** | Cluster identifier | | **VALID** | Whether the cluster is reachable (`yes` / `NO`) | | **API_URL** | The OCP API server endpoint | | **CREATED_BY** | Who onboarded the cluster (blank for infrastructure clusters) | | **PLACEMENTS** | Active placements vs max (e.g., `3 / 30`). `?` means no max configured | ## Important Notes - Clusters with `VALID = NO` are unreachable and may need investigation or forced offboarding. - Clusters with `?` as max placements have no `max_placements` limit configured. - Clusters with `0` placements are idle and available for workloads. - If the user wants more details about a specific cluster, suggest using `/sandbox-cli:cluster-details`.
Related Skills
sandbox-cli:sandbox-setup
This skill should be used when the user asks to "install sandbox-cli", "setup sandbox", "configure sandbox-cli", "get sandbox-cli working", "download sandbox-cli", or "I don't have sandbox-cli installed".
sandbox-cli:cluster-rotate
This skill should be used when the user asks to "rotate a cluster", "replace a cluster", "swap clusters", "offboard old and onboard new cluster", "cluster rotation", "replace an old cluster with a new one", or "refresh cluster".
sandbox-cli:cluster-onboard
This skill should be used when the user asks to "onboard a cluster", "add a cluster to sandbox", "register a cluster", "onboard OCP cluster", "sandbox onboard", or "add a new shared cluster".
sandbox-cli:cluster-offboard
This skill should be used when the user asks to "offboard a cluster", "remove a cluster from sandbox", "decommission a cluster", "sandbox offboard", "take a cluster offline", or "remove a shared cluster".
sandbox-cli:cluster-details
This skill should be used when the user asks to "show cluster details", "get cluster info", "describe cluster", "cluster details", "inspect cluster", or "show cluster configuration".
showroom:verify-content
This skill should be used when the user asks to "verify my workshop content", "review my lab module", "check my Showroom content", "validate my AsciiDoc module", "quality check my demo", "review my workshop for Red Hat standards", or "run a content review on my lab".
showroom:create-lab
This skill should be used when the user asks to "create a lab module", "write a workshop module", "build a Showroom lab", "convert docs to a lab", "write a hands-on exercise", "create an AsciiDoc module", or "turn this documentation into a lab exercise".
showroom:create-demo
This skill should be used when the user asks to "create a demo module", "write a Know/Show demo", "build a presenter demo", "create a Showroom demo", "write a facilitator guide", "build a demo script", or "create a presenter-led demo for RHDP".
showroom:blog-generate
This skill should be used when the user asks to "turn this lab into a blog post", "write a blog post from this module", "generate a blog from my Showroom content", "convert my workshop to a blog", "write a Red Hat Developer blog post", or "create a blog post from my demo".
health:deployment-validator
Infrastructure Health Checker — use this when you need to validate that a workload or service DEPLOYED SUCCESSFULLY (pods running, routes accessible, dependencies ready). This is NOT for student E2E lab testing. For student exercise validation (solve/validate buttons), use /ftl:rhdp-lab-validator instead. Triggers on: 'create a validation role', 'build health checks', 'add deployment validation', 'create post-deployment checks', 'validate my deployment', 'check if my workload is healthy'.
agnosticv:validator
This skill should be used when the user asks to "validate my catalog", "check my AgnosticV config", "review common.yaml", "validate my RHDP catalog", "check for errors in my catalog", "lint my AgnosticV files", or "verify my catalog before submitting".
agnosticv:catalog-builder
This skill should be used when the user asks to "create a catalog", "build a common.yaml", "add a new RHDP lab", "set up a new catalog item", "create an AgnosticV catalog", "build a dev.yaml", "add a catalog entry", or "create a new lab catalog for RHDP".