rhpds/sandbox-cli:cluster-list
sandbox-cli/skills/cluster-list/SKILL.md
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".
$ install --global
skillsauthnpx skillsauth add rhpds/rhdp-skills-marketplace sandbox-cli:cluster-listInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 11, 2026, 10:54 PM21.9s1 file scanned
SKILL.md
- name:
- sandbox-cli:cluster-list
- description:
- 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".
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:
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.
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
sandbox-cli status
If not authenticated or token expired, tell the user to re-login:
sandbox-cli login --server <SERVER_URL> --token <TOKEN>
Step 4: List All Clusters
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 = NOare unreachable and may need investigation or forced offboarding. - Clusters with
?as max placements have nomax_placementslimit configured. - Clusters with
0placements are idle and available for workloads. - If the user wants more details about a specific cluster, suggest using
/sandbox-cli:cluster-details.
Related Skills
rhpds/ftl:validate-writer
tools
VerifiedTrustedCommunity
Writes validate.yml playbooks using the validation_check Ansible plugin. Takes the content-reader task report and solve-writer actions as input, producing checks that verify student progress without manual steps or navigation instructions.
13SKILL.mdUpdated Apr 16, 2026
rhpds/ftl:solve-writer
tools
VerifiedTrustedCommunity
Writes solve.yml playbooks from the structured task report produced by ftl:content-reader. Uses the automation priority ladder (k8s_exec → k8s → uri → wait_for → Playwright) to generate Ansible tasks that replicate what the student does in the lab.
13SKILL.mdUpdated Apr 16, 2026
rhpds/ftl:env-connector
development
VerifiedTrustedCommunity
Pushes solve.yml and validate.yml to a live RHDP showroom, restarts the pod, and runs the full test cycle (fresh validate → solve → validate again → idempotency check). Reports pass/fail per task with full output for debugging.
13SKILL.mdUpdated Apr 16, 2026
rhpds/ftl:content-reader
tools
VerifiedTrustedCommunity
AsciiDoc reader agent for the FTL lab validator. Reads a showroom .adoc module file, extracts executable code blocks (role="execute"), classifies each step by automation type, and outputs a structured task report for the solve-writer and validate-writer agents.
13SKILL.mdUpdated Apr 16, 2026