Agent skill · software engineering · jeremylongshore
castai-core-workflow-a
Connect a Kubernetes cluster to CAST AI in observation-first mode and establish a trustworthy cost baseline before automation. Use when onboarding a new EKS, GKE, AKS, or CAST AI Anywhere cluster. Trigger with: "connect a cluster to CAST AI", "start CAST AI cost monitoring", "onboard CAST AI safely".
Why this skill is useful
Adds executable scripts for configuring CAST AI autoscaler policies and node templates that aren't in public documentation.
What it needs
Requires curl, jq, terraform 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 Observation-First Onboarding Overview Connect one approved cluster with the recommended castctl path, keep optimization automation off initially, and prove identity, telemetry, ownership, and rollback before expanding control. Prerequisites A named kube context for EKS, GKE, AKS, or a supported CAST AI Anywhere environment Cluster-admin access for installation and reviewed least-privilege cloud permissions metrics-server when Workload Autoscaling will be evaluated An owner, maintenance window, rollback decision, and evidence location Instructions Step 1: Establish ownership Use Read and Grep to locate existing CAST AI, autoscaler, Terraform, Helm, and GitOps definitions. Stop if another controller owns node provisioning or workload HPA behavior and no coexistence decision exists. Step 2: Preview the connection Use Bash(castctl:\) to verify the installed client, authenticate interactively to the intended organization, and run the documented connection dry-run. Record detected provider, cluster, region, selected features, namespace, and proposed cloud changes without connecting. Step 3: Review permissions and features Confirm least-privilege cloud access and the exact cluster context. Cost Monitoring is always enabled; select Node Autoscaling or Workload Autoscaling only when entitlement, metrics, disruption, and ownership prerequisites are met. Use Write or Edit to capture the approved choices in the repository runbook. Step 4: Connect the cluster Run the reviewed castctl connection during the approved window. Do not substitute the deprecated script flow for a supported castctl environment. Preserve the console URL and sanitized command receipt, never browser tokens or API keys. Step 5: Verify observation mode Use Bash(kubectl:\) to verify namespace workloads, readiness, events, and metrics prerequisites. Confirm the console receives the intended cluster and cost data while automation remains in the approved state. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/castai-core-workflow-a