More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    kubectl: Operate Kubernetes the Safe Way

    1

    Operate Kubernetes clusters from the command line with a safety-first habit: inspect before acting, dry-run before applying, roll back cleanly.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    kubectl: Operate Kubernetes the Safe Way

    kubectl: Operate Kubernetes the Safe Way

    Example session with this skill installed

    A deployment is CrashLoopBackOff in production. Walk me through triage, then ship the fix and prove the rollout worked.

    • Read your context and instructions
    • Compiled the kubectl

    Context check first: kubectl config current-context confirmed the production cluster before any mutating command — the two-second check that prevents the classic wrong-cluster incident. Triage: kubectl get pods -l app=myapp scoped by label; kubectl describe pod read bottom-up, Events showing the container exiting before logging; kubectl logs --previous confirmed the process died on startup. The divergence: the new image tag pointed at a build that never pushed. Fix shipped with discipline: manifest corrected, applied with --dry-run=server first to validate against admission controllers, then applied for real. Rollout watched with kubectl rollout status -w until it completed — nobody walked away mid-rollout. Proof: kubectl get pods -l app=myapp showed all new pods Running and Ready, old ones gone; a YAML snapshot of the pre-change deployment was saved before the fix so the last known good is on disk. Rollback was ready the whole time: kubectl rollout undo deployment/myapp was the named undo before the apply, not something to look up in a panic. It was not needed — the rollout went green on the first attempt, and the saved snapshot of the last known good stays on disk for the next change.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    kubectl is a loaded tool pointed at shared infrastructure. The discipline that matters: look before you touch, rehearse before you apply, and know the undo before you need it. This skill is organized around the three jobs you actually do — triaging broken workloads, shipping changes, and maintaining nodes — rather than a command dump. It teaches the habits that prevent the classic incidents: confirming context before any mutating command, reading describe output bottom-up because the Events section is where the truth lives, dry-running on the server before applying, watching a rollout to completion, and rolling back fast instead of admitting failure slowly. It also covers output shaping with wide, jsonpath, and custom columns, plus context and namespace hygiene so staging configs never land in production.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse All Claude Skills.

    It assumes kubectl v1.20+ and a working kubeconfig — without those, setup comes before any habit.
    It is a command-line discipline, not a dashboard replacement; visual and graph-heavy investigation still belongs in the UI.
    Drain respects disruption budgets and never uses kubectl delete node as a shortcut.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 3 days ago

    Permissions

    Terminal / Shell
    Listed3 days ago

    What's inside

    Frequently Asked Questions

    Confirming context before any mutating command. `kubectl config current-context` takes two seconds and prevents the classic wrong-cluster incident.

    Client dry-run checks syntax locally; server dry-run validates against the cluster's admission controllers and catches more. For anything touching production, run the server variant.

    Immediately, when the rollout is wrong. Rolling back is a decision you make fast, not a failure you admit slowly — fix forward after the service is healthy again.