Agent skill · software engineering · jeremylongshore
castai-common-errors
Diagnose CAST AI connection, agent, node autoscaling, and workload autoscaling failures without making speculative changes. Use when a cluster is disconnected, recommendations are absent, pods are not optimized, or capacity does not scale as expected. Trigger with: "debug CAST AI", "CAST AI is not scaling", "why is CAST AI disconnected".
Why this skill is useful
Provides specific commands and troubleshooting steps for diagnosing and fixing CAST AI agent issues that the AI wouldn't reliably generate on its own.
What it needs
Requires curl, jq, kubectl installed locally. Requires castai account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
CAST AI Failure Triage Overview Separate observation, connectivity, policy, capacity, and disruption failures before proposing a change. Preserve the failing state, use current component topology, and stop when the evidence requires cloud-provider or CAST AI support access. Prerequisites The exact kube context, cluster, region, time window, and observed symptom Read-only access to the castai-agent namespace The declared installation owner: castctl, Terraform, GitOps, or console Instructions Step 1: Freeze the symptom Record expected versus actual behavior, timestamps, workload identity, pending-pod reason, and recent configuration changes. Use Read and Grep on runbooks and IaC to determine whether Cost Monitoring, Node Autoscaling, or Workload Autoscaling is actually enabled. Step 2: Check installation health Use Bash(castctl:) for version or non-mutating status commands supported by the installed client. Use Bash(helm:) to inspect releases and values, then Bash(kubectl:\) to inspect workloads, readiness, events, and bounded logs in castai-agent. Do not restart components before collecting evidence. Step 3: Classify the failure plane Plane Evidence Likely boundary ---------------- ------------------------------------------------------ ----------------------------------------------------------- Connection Agent readiness, outbound failures, console disconnect Identity, network, or cloud permissions Node scaling Pending pods, policy bounds, node-template fit Unsatisfied constraints or maximum CPU boundary Workload scaling Missing recommendations, policy assignment, metrics Metrics server, confidence, policy, or unsupported workload Disruption Eviction denial, PDB events, deferred changes PDB or selected apply mode Reporting Missing cost or savings window Ingestion, baseline, adoption, or pricing configuration Step 4: Test one hypothesis Choose the smallest reversible check. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/castai-common-errors--a382a9