How do I install the Kind Dev skill?

Run npx skillmds@latest add coder/kind-dev in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Kind Dev skill do?

Per-workspace KIND clusters for coder-k8s dev + demos. It is listed under DevOps & Infra on SkillMD.

Is Kind Dev safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Kind Dev?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Kind Dev free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Kind Dev?

coder (@coder) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Kind Dev by coder — Agent Skill

Name: Kind Dev
Author: coder

File contents

KIND dev clusters (coder-k8s)

Load this skill only when you need a real Kubernetes cluster (KIND) during development or demos.

Unique cluster names (parallel agents)

Prefer a per-workspace name to avoid collisions:

export CLUSTER_NAME="coder-k8s-${MUX_WORKSPACE_NAME:-dev}"

Bootstrap

./hack/kind-dev.sh up
kubectl --context kind-${CLUSTER_NAME} get nodes

./hack/kind-dev.sh up defaults to KIND_NODE_IMAGE=kindest/node:v1.34.0. Override it when needed:

KIND_NODE_IMAGE=kindest/node:v1.32.0 ./hack/kind-dev.sh up

If the cluster already exists and you change KIND_NODE_IMAGE, recreate it first:

./hack/kind-dev.sh down
KIND_NODE_IMAGE=kindest/node:v1.32.0 ./hack/kind-dev.sh up

Start controller (out-of-cluster)

# up already switches your current context; run ctx again if needed.
./hack/kind-dev.sh ctx

GOFLAGS=-mod=vendor go run . --app=controller

Optional: in-cluster controller

./hack/kind-dev.sh load-image
kubectl --context kind-${CLUSTER_NAME} apply -f config/e2e/deployment.yaml
kubectl --context kind-${CLUSTER_NAME} -n coder-system wait --for=condition=Available deploy/coder-k8s --timeout=120s

Demo with k9s

k9s --context kind-${CLUSTER_NAME}

Cleanup

./hack/kind-dev.sh down

Validation when implementing

Nix tools available:

nix develop -c kubectl version --client
nix develop -c kind version
nix develop -c k9s version

Script sanity:
```
bash -n hack/kind-dev.sh
```

Bootstrap smoke test (deterministic cluster name):

CLUSTER_NAME=coder-k8s-dev ./hack/kind-dev.sh up
test "$(kubectl config current-context)" = "kind-coder-k8s-dev"
kubectl --context kind-coder-k8s-dev get crd codercontrolplanes.coder.com
kubectl --context kind-coder-k8s-dev get clusterrole manager-role
kubectl --context kind-coder-k8s-dev -n coder-system get sa coder-k8s

Optional in-cluster controller smoke test:

CLUSTER_NAME=coder-k8s-dev ./hack/kind-dev.sh load-image
kubectl --context kind-coder-k8s-dev apply -f config/e2e/deployment.yaml
kubectl --context kind-coder-k8s-dev -n coder-system wait --for=condition=Available deploy/coder-k8s --timeout=120s

Skill file exists:
```
test -f .mux/skills/kind-dev/SKILL.md
```

Cleanup:

CLUSTER_NAME=coder-k8s-dev ./hack/kind-dev.sh down

Use explicit kubectl --context kind-${CLUSTER_NAME} commands whenever possible to avoid acting on the wrong cluster.

---name: kind-devdescription: Per-workspace KIND clusters for coder-k8s dev + demos.---# KIND dev clusters (coder-k8s)Load this skill only when you need a real Kubernetes cluster (KIND) during development or demos.## Unique cluster names (parallel agents)Prefer a per-workspace name to avoid collisions:```bashexport CLUSTER_NAME="coder-k8s-${MUX_WORKSPACE_NAME:-dev}"```## Bootstrap```bash./hack/kind-dev.sh upkubectl --context kind-${CLUSTER_NAME} get nodes````./hack/kind-dev.sh up` defaults to `KIND_NODE_IMAGE=kindest/node:v1.34.0`. Override it when needed:```bashKIND_NODE_IMAGE=kindest/node:v1.32.0 ./hack/kind-dev.sh up```If the cluster already exists and you change `KIND_NODE_IMAGE`, recreate it first:```bash./hack/kind-dev.sh downKIND_NODE_IMAGE=kindest/node:v1.32.0 ./hack/kind-dev.sh up```## Start controller (out-of-cluster)```bash# up already switches your current context; run ctx again if needed../hack/kind-dev.sh ctxGOFLAGS=-mod=vendor go run . --app=controller```## Optional: in-cluster controller```bash./hack/kind-dev.sh load-imagekubectl --context kind-${CLUSTER_NAME} apply -f config/e2e/deployment.yamlkubectl --context kind-${CLUSTER_NAME} -n coder-system wait --for=condition=Available deploy/coder-k8s --timeout=120s```## Demo with k9s```bashk9s --context kind-${CLUSTER_NAME}```## Cleanup```bash./hack/kind-dev.sh down```## Validation when implementing1. Nix tools available: ```bash nix develop -c kubectl version --client nix develop -c kind version nix develop -c k9s version ```2. Script sanity: ```bash bash -n hack/kind-dev.sh ```3. Bootstrap smoke test (deterministic cluster name): ```bash CLUSTER_NAME=coder-k8s-dev ./hack/kind-dev.sh up test "$(kubectl config current-context)" = "kind-coder-k8s-dev" kubectl --context kind-coder-k8s-dev get crd codercontrolplanes.coder.com kubectl --context kind-coder-k8s-dev get clusterrole manager-role kubectl --context kind-coder-k8s-dev -n coder-system get sa coder-k8s ```4. Optional in-cluster controller smoke test: ```bash CLUSTER_NAME=coder-k8s-dev ./hack/kind-dev.sh load-image kubectl --context kind-coder-k8s-dev apply -f config/e2e/deployment.yaml kubectl --context kind-coder-k8s-dev -n coder-system wait --for=condition=Available deploy/coder-k8s --timeout=120s ```5. Skill file exists: ```bash test -f .mux/skills/kind-dev/SKILL.md ```6. Cleanup: ```bash CLUSTER_NAME=coder-k8s-dev ./hack/kind-dev.sh down ```Use explicit `kubectl --context kind-${CLUSTER_NAME}` commands whenever possible to avoid acting on the wrong cluster.

Frequently asked questions

Kind Dev