k8s-capi

Manage Kubernetes Cluster API lifecycle operations for provisioning, scaling, and upgrading clusters.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/spigell/my-agents --skill k8s-capi-spigell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: k8s-capi
Source: https://github.com/spigell/my-agents/tree/main/agents/shared/src/tools/ask_kubernetes_expert/skills/k8s-capi
Command: npx skills add https://github.com/spigell/my-agents --skill k8s-capi-spigell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cluster API lifecycle operations—provisioning, scaling, and upgrading Kubernetes clusters—are complex and error-prone, so this Skill helps you plan and execute the right sequence of actions with visibility into cluster and machine status.

Core Features & Use Cases

  • CAPI Installation & Readiness Checks: Detects Cluster API installation first and verifies cluster phase before running lifecycle actions.
  • Cluster & Kubeconfig Access: Lists clusters, fetches detailed cluster state, and retrieves kubeconfig after provisioning.
  • Machine & Deployment Scaling Control: Monitors machines and scales MachineDeployments while checking the underlying rollout state.

Quick Start

Use the k8s-capi skill to detect CAPI installation, list clusters in a namespace, and fetch the kubeconfig for a selected cluster by asking it what tool calls to run in order.

Frequently Asked Questions about k8s-capi

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if Cluster API is installed before provisioning Kubernetes clusters?

To check if Cluster API is installed, you must first detect the CAPI installation and verify the cluster phase before running any provisioning or lifecycle actions.

How do I retrieve the kubeconfig after provisioning a Cluster API cluster?

To retrieve the kubeconfig after provisioning a Cluster API cluster, you orchestrate the correct sequence of discovery and validation steps, which includes fetching the kubeconfig for operational access.

How do I monitor machines during Kubernetes Cluster API scaling operations?

To monitor machines during Kubernetes Cluster API scaling, you scale MachineDeployments while checking the underlying rollout state to track machine status and deployment progress.

What is the correct priority order for Kubernetes Cluster API lifecycle operations?

The correct priority order for Kubernetes Cluster API lifecycle operations involves installation detection first, followed by phase checks, machine monitoring during scaling, and kubeconfig retrieval after provisioning.

Does this approach support upgrading and scaling multiple Kubernetes workloads simultaneously?

Yes, this approach supports upgrading, scaling, and provisioning Kubernetes clusters across multiple workloads by orchestrating discovery and validation steps for each lifecycle phase.

Why should I verify cluster phase and conditions before running Kubernetes lifecycle actions?

Verifying cluster phase and conditions before running Kubernetes lifecycle actions is necessary because CAPI operations are complex and error-prone, requiring visibility into cluster and machine status to execute safely.