Agent skill · software engineering · jeremylongshore
castai-deploy-integration
Deploy CAST AI through a reviewable GitOps or Terraform lane with pinned artifacts, explicit control ownership, and staged promotion. Use when standardizing CAST AI across clusters or moving console-managed configuration into code. Trigger with: "deploy CAST AI with GitOps", "manage CAST AI as code", "roll out CAST AI to multiple clusters".
Why this skill is useful
Adds Terraform scripts for deploying CAST AI across multiple cloud Kubernetes clusters, which are not commonly found in public documentation.
What it needs
Requires terraform 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 Deployment Integration Overview Make the repository the declared source of truth for CAST AI installation and policy, then promote one cluster ring at a time. Keep registration, cloud permissions, chart configuration, and automation decisions independently reviewable. Prerequisites Target clusters grouped into canary, staging, and production rings A chosen owner: Terraform, GitOps Helm, castctl, or console Pinned provider, module, chart, and policy inputs Secret delivery that does not commit or render credentials into artifacts Instructions Step 1: Inventory existing ownership Use Read and Grep to find CAST AI resources, individual component charts, the unified castai chart, Terraform state addresses, Flux or Argo CD objects, and console-only settings. Stop if two systems can reconcile the same resource. Step 2: Define the repository contract Use Write or Edit to separate cluster registration, cloud IAM, Helm values, scaling policies, node templates, workload annotations, notification settings, and automation toggles. Parameterize organization, region, and cluster identity; never parameterize a secret with a committed literal. Step 3: Render and plan Use Bash(helm:) to lint and render the pinned chart. Use Bash(terraform:) to format, validate, and save a plan. Use Bash(kubectl:\) for client-side manifest checks. Review RBAC, webhooks, CRDs, namespace, disruption behavior, deleted resources, and ownership transfers. Step 4: Handle existing installations If the cluster uses individual CAST AI Helm releases, evaluate the documented castctl cluster migrate path to the unified umbrella chart. Use Bash(castctl:\) only after recording current releases, values, rollback, and the exact cluster context. Step 5: Promote by ring Apply through the declared delivery controller to one canary cluster. Verify agent health, telemetry, policy state, and automation boundaries before staging and production. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/castai-deploy-integration