How do I install the K3d Environment skill?

Run npx skillmds@latest add bionic-gpt/k3d-environment 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 K3d Environment skill do?

Set up or reconfigure Bionic's local k3d Kubernetes environment. Trigger only when the user explicitly asks to initialize, configure, or set up the local k3d environment. It is listed under DevOps & Infra on SkillMD.

Is K3d Environment 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 K3d Environment?

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 K3d Environment free to use?

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

Who published K3d Environment?

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

K3d Environment by bionic-gpt — Agent Skill

Name: K3d Environment
Author: bionic-gpt

File contents

k3d Environment

Use this skill only for an explicit request to create, initialize, configure, or set up the local k3d environment. Do not trigger it for ordinary builds, tests, watcher startup, diagnosis, or application deployment.

Run the scripts from the repository root:

bash .agents/skills/k3d-environment/dev-init.sh
bash .agents/skills/k3d-environment/dev-setup.sh
bash .agents/skills/k3d-environment/get-config.sh

dev-init.sh deletes and recreates the k3d-bionic cluster, then updates the user kubeconfig. dev-setup.sh installs and deploys the development and Selenium Stack resources. get-config.sh changes the user's kubeconfig, including disabling TLS verification for local development.

Prerequisites:

k3d, kubectl, stack, iproute2 and sudo are installed.
The commands are run from a checkout of this repository.
The user understands that these scripts change local Kubernetes resources or host configuration.

These scripts are state-changing and must never run automatically. Confirm the user explicitly requested the relevant operation before executing it. Do not run dev-init.sh merely because the cluster is unavailable; it destroys the existing cluster.

Frequently asked questions

K3d Environment