Agent skill · software engineering · jeremylongshore
castai-hello-world
Run a safe first CAST AI cluster connection that proves Cost Monitoring and agent health before enabling optimization. Use when starting a new evaluation, sandbox, or operator walkthrough. Trigger with: "CAST AI hello world", "try CAST AI safely", "connect my first CAST AI cluster".
Why this skill is useful
Adds executable scripts for querying the CAST AI API, which provide capabilities for cost optimization and cluster management that the AI wouldn't generate on its own.
What it needs
Requires curl, jq 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 Safe First Connection Overview Prove the minimum useful loop: identify one sandbox cluster, preview the connection, connect with Cost Monitoring, verify telemetry, and leave optimization automation unchanged. Prerequisites A disposable or non-production kube context with an accountable owner castctl installed from an official distribution and authenticated to the intended organization Cluster-admin and reviewed provider permissions An approved evidence and cleanup plan Instructions Step 1: Confirm the sandbox Use Bash(kubectl:\) to print the current context and inspect only basic cluster identity. Use Read and Grep to ensure the cluster is not already owned by CAST AI, another autoscaler, Terraform, or GitOps. Step 2: Preview with castctl Use Bash(castctl:\) to check the client version and run the documented cluster connection dry-run. Review detected provider, cluster name, region, organization, proposed features, namespace, and cloud changes. Step 3: Record the decision Use Write to capture the dry-run, selected cluster, owners, features, start time, expected telemetry, and cleanup path. Cost Monitoring is always enabled; do not select Node or Workload Autoscaling merely to complete a quickstart. Step 4: Connect once Run the reviewed interactive connection. Confirm the prompt resolves the same cluster and organization. Keep the returned console URL, but never store the browser token, kubeconfig, or API key in the receipt. Step 5: Verify the loop Use Bash(kubectl:\) to verify castai-agent namespace workloads, readiness, and recent warning events. Confirm the console identifies the correct cluster and begins showing cost data. Treat an empty initial report as ingestion time, not proof of zero cost. Step 6: Close or hand off If the evaluation continues, hand off to observation-first onboarding. If it ends, use the documented disconnect path only after reviewing cloud and cluster cleanup effects and preserving the final receipt. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/castai-hello-world--91fb14