Agent skill · software engineering · jeremylongshore
castai-debug-bundle
Create a bounded, redacted CAST AI diagnostic bundle that preserves component, policy, and Kubernetes evidence for escalation. Use when triage must be handed to platform engineering, a cloud owner, or CAST AI support. Trigger with: "collect CAST AI diagnostics", "make a CAST AI support bundle", "capture CAST AI evidence".
Why this skill is useful
Adds an executable script that automates the collection of diagnostic data for CAST AI, which is not commonly available in public documentation.
What it needs
Requires helm, jq, kubectl installed locally. Requires castai account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
CAST AI Redacted Diagnostic Bundle Overview Capture enough evidence to reproduce a CAST AI failure without exporting credentials, Secret payloads, broad cluster inventory, application data, or unbounded logs. Prerequisites Exact kube context, cluster identifier, CAST AI region, incident window, and symptom Approved local destination with retention and audience Redaction rules for names, labels, annotations, IPs, account data, and credentials Instructions Step 1: Declare the bundle contract Use Write to record incident ID, collector, start and end time, selected namespaces, commands, excluded data classes, redaction method, checksum method, retention, and recipients. Step 2: Inventory component versions Use Bash(castctl:) for version information, Bash(helm:) for release metadata and redacted values, and Bash(kubectl:\) for component images and readiness. Do not collect Helm secrets, rendered Secret objects, service-account tokens, or kubeconfig contents. Step 3: Capture bounded health evidence Collect status, restart counts, recent warning events, selected resource descriptions, and logs constrained by component, time, and line count. Include metrics-server status when workload recommendations are involved and pending-pod reasons when node capacity is involved. Step 4: Capture declared policy context Use Read and Grep on repository-owned Terraform, Helm values, annotations, node templates, PDBs, and HPAs. Record source paths and commit identifiers. Prefer diffs and normalized summaries over raw state files. Step 5: Redact and verify Scan the bundle for API keys, authorization headers, tokens, Secret data, cloud account identifiers, email addresses, private endpoints, and application payloads. Replace values consistently so relationships remain debuggable. Step 6: Seal the handoff Write a manifest of included files, omitted evidence, timestamps, tool versions, hashes, and known gaps. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/castai-debug-bundle