Agent skill · software engineering · jeremylongshore
castai-prod-checklist
Run a fail-closed production-readiness review for a CAST AI cluster before enabling or expanding automation. Use when deciding onboarding approval, control-plane migration, or rollout between cluster rings. Trigger with: "review CAST AI for production", "CAST AI go-live checklist", "approve CAST AI automation".
Why this skill is useful
Provides specific commands and validation steps for managing CAST AI autoscaling on Kubernetes clusters that the AI wouldn't reliably generate on its own.
What it needs
Requires curl, 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 Production Readiness Gate Overview Approve production only when identity, ownership, connectivity, observability, scaling safety, cost interpretation, rollback, and evidence are all explicit. An unchecked or unknown item is a stop, not a soft pass. Prerequisites Exact production kube context and CAST AI organization/region Reviewed infrastructure plan and pinned artifacts Workload owners, SLOs, PDBs, HPAs, quotas, and maintenance window Incident, rollback, and support escalation owners Instructions Step 1: Verify identity and ownership Use Read and Grep to prove cluster, organization, region, cloud account, IaC source, reconcilers, and secret references. Confirm one owner for node provisioning, vertical rightsizing, and each HPA. Step 2: Verify installation and access Use Bash(castctl:) for supported version or status inspection, Bash(helm:) for pinned release evidence, and Bash(kubectl:\) for component readiness and warning events. Confirm least-privilege cloud permissions and required outbound connectivity. Step 3: Verify scaling guardrails Review node templates, maximum CPU, cloud quotas, protected namespaces, workload policy assignment, minimum/maximum requests, apply mode, recommendation confidence, PDB behavior, HPA bounds, and ownership transfer. Reject deprecated cluster minimum CPU configuration. Step 4: Verify cost and reporting Confirm baseline source, representative data window, public versus adjusted prices, automation adoption, and reconciliation owner. Do not use available or modeled savings as an unconditional release gate. Step 5: Verify delivery and rollback Use Bash(terraform:) for the saved plan and Bash(helm:) for the reviewed render. Confirm no unexpected deletion, disconnect, IAM expansion, CRD replacement, webhook collision, or automation enablement. Use Write or Edit to record tested rollback steps and thresholds. Step 6: Make the decision Record PASS only when every required item has evidence. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/castai-prod-checklist--7c9be6