kubectl
Manage the local kubernetes cluster for development. Use when the user asks to check pods, restart deployments, view logs, apply manifests, create or delete resources, or perform any kubectl/helm operation.
Best use case
kubectl is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Manage the local kubernetes cluster for development. Use when the user asks to check pods, restart deployments, view logs, apply manifests, create or delete resources, or perform any kubectl/helm operation.
Teams using kubectl should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/kubectl/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How kubectl Compares
| Feature / Agent | kubectl | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Manage the local kubernetes cluster for development. Use when the user asks to check pods, restart deployments, view logs, apply manifests, create or delete resources, or perform any kubectl/helm operation.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
## Setup 1. **Read cluster config**: Read `dev_env/.env` to get: - `DATASPOKE_DEV_KUBE_CLUSTER` — kube context (e.g., `docker-desktop`) - `DATASPOKE_DEV_KUBE_DATAHUB_NAMESPACE` — DataHub namespace (e.g., `datahub-01`) - `DATASPOKE_DEV_KUBE_DATASPOKE_NAMESPACE` — DataSpoke namespace (e.g., `dataspoke-01`) - `DATASPOKE_DEV_KUBE_DUMMY_DATA_NAMESPACE` — Example sources namespace (e.g., `dummy-data1`) 2. **Verify prerequisites**: ```bash kubectl version --client kubectl config current-context # confirm correct context kubectl get nodes # confirm cluster access ``` If tools are missing or cluster is unreachable, stop and inform the user. --- ## Execution Strategy for `$ARGUMENTS` **Before acting**: identify the operation type from `$ARGUMENTS` — read, create, modify, or delete. **Read operations** (safe, execute immediately): ```bash kubectl get <type> -n <namespace> kubectl describe <type> <name> -n <namespace> kubectl logs <pod> -n <namespace> --tail=100 kubectl get events -n <namespace> --sort-by='.lastTimestamp' helm status <release> -n <namespace> helm history <release> -n <namespace> helm get values <release> -n <namespace> ``` **Create/apply operations** (use dry-run first): ```bash # Validate first kubectl apply -f <file.yaml> --dry-run=server # Then apply kubectl apply -f <file.yaml> -n <namespace> ``` **Modify operations** (confirm intent, then execute): ```bash kubectl rollout restart deployment/<name> -n <namespace> helm upgrade <release> <chart> -n <namespace> -f <values.yaml> ``` **Delete operations** — always follow this safety workflow: ```bash # 1. Confirm you're in the right context kubectl config current-context # 2. Describe before deleting kubectl describe <type> <name> -n <namespace> # 3. Delete kubectl delete <type> <name> -n <namespace> # 4. Verify kubectl get <type> -n <namespace> ``` **Never delete namespaces.** For scale-to-zero or namespace-level destructive operations, confirm with the user first. --- ## Report Results After every operation, summarize: - What was executed - What changed (before/after state if relevant) - Any warnings, errors, or events triggered - Suggested next steps if issues are found For errors, consult [reference.md](reference.md) for common causes and resolutions. --- See [reference.md](reference.md) for helm chart management, resource creation patterns, capacity planning, and error reference.
Related Skills
kubectl-skill
Execute and manage Kubernetes clusters via kubectl commands. Query resources, deploy applications, debug containers, manage configurations, and monitor cluster health. Use when working with Kubernetes clusters, containers, deployments, or pod diagnostics.
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
runpod
Cloud GPU processing via RunPod serverless. Use when setting up RunPod endpoints, deploying Docker images, managing GPU resources, troubleshooting endpoint issues, or understanding costs. Covers all 5 toolkit images (qwen-edit, realesrgan, propainter, sadtalker, qwen3-tts).
runbook
Generate operational runbooks for services, procedures, or incident response with step-by-step procedures, troubleshooting guides, and escalation paths
Run CI/CD Pipeline Locally
Run the Wavecraft CI checks locally. Prefer the native `cargo xtask` commands for speed; use Docker + `act` only when validating GitHub Actions workflows or Linux-specific behavior.
router-operations
Master orchestration for routing QA, testing, DevOps, observability, and git workflow questions through 15 operational skills
returns-reverse-logistics
Codified expertise for returns authorisation, receipt and inspection, disposition decisions, refund processing, fraud detection, and warranty claims management.
resume-craft
Craft tailored, honest, one-page resumes from job descriptions. Use when the user wants to create, tailor, or improve a resume for a specific job posting. Handles job description analysis, skill gap identification, resume writing, keyword optimization, and PDF generation. Triggers on resume, CV, job application, tailor my resume, craft resume, apply for this job.
resource-scout
Search and discover Claude Code skills and MCP servers from marketplaces, GitHub repositories, and registries. Use when (1) user asks to find skills for a specific task, (2) looking for MCP servers to connect external tools, (3) user mentions "find skill", "search MCP", "discover tools", or "what skills exist for X", (4) before creating a custom skill to check if one already exists.
rails-deployment
Deploy Rails applications to production using Kamal, Docker, and modern deployment strategies. Covers zero-downtime deployments, environment management, database migrations, SSL/TLS, and production configurations.
r2-transfer-service-playbook
Manage changes to the R2 transfer pipeline (Python service, Cloudflare Workers, PHP logger) with mandatory validations, allowlists, and regression checks.
quality-gate
Synthesize all quality assessments (risk, test-design, traceability, NFR) into evidence-based gate decision (PASS/CONCERNS/FAIL/WAIVED) with comprehensive rationale. Generates both YAML (CI/CD) and Markdown (human review) reports with action items. Use during final quality review to make go/no-go deployment decisions based on comprehensive quality evidence.