Kubernetes 任何AI代理的排除故障技能:先读,再问再换 任何东西。

类群中真实运行的 oom- killed 情景, 仅限视图 库贝克 命令和输出被缩短,答案是代理人自己的 词

k8s-技能是一套特工技能,它教人工智能特工 调查Kubernets的问题 经验丰富的SRE的方式: 如何看,在 命令,每个发现意味着什么, 和什么建议。 Claude的技能工作 代码 代码 双子座 CLI 反重力 GitHub 副驾驶和任何其他读取的代理 SKILL.md文件并可以运行 [[T1].

如何操作,如何测试每种技能, 以及打破类组76的方法 K8s- 技能: 教人工智能特工 向没有麻烦的Kubernetes 击出.

快开始

然后向您的代理描述问题, 例如“ 我的应用程序在我的命名空间中保存 ” 重启中 。 找出原因。 * 对于只能看的代理人,给它只读 Kubeconfig(你的经纪人,你的决定). 更多安装方式 正在安装中。

试试丢掉的星团

还没准备好指向真正的集群吗? 与多克,善良的

k8s-skills

Kubernetes troubleshooting skills for any AI agent: read first, ask before changing anything.

A real run of the oom-killed scenario on a kind cluster, with a view-only kubeconfig. The commands and output are shortened, and the answer is the agent’s own words.

k8s-skills is a set of Agent Skills that teach an AI agent to investigate Kubernetes problems the way an experienced SRE does: what to look at, in which order, what each finding means, and what to propose. The skills work in Claude Code, Codex, Gemini CLI, Antigravity, GitHub Copilot and any other agent that reads SKILL.md files and can run kubectl.

How it works, how each skill is tested, and what breaking a kind cluster 76 ways showed about the docs: k8s-skills: Teaching AI Agents to Troubleshoot Kubernetes Without Breaking It.

Quick start

npx skills add k8s-servant/k8s-skills -a claude-code   # or -a codex, ...
gemini extensions install https://github.com/k8s-servant/k8s-skills   # Gemini CLI

Then describe the problem to your agent, for example “my-app in my-namespace keeps restarting. Find out why.” For an agent that can only look, give it a read-only kubeconfig (Your agent, your decision). More ways to install are under Install.

Try it on a throwaway cluster first

Not ready to point an agent at a real cluster? With Docker, kind and kubectl, one command creates a local test cluster, breaks something on purpose and prints what to give your agent:

git clone https://github.com/k8s-servant/k8s-skills.git && cd k8s-skills
tests/try.sh                # default: a pod that is OOMKilled; tests/try.sh --list for more

It prints a prompt and a view-only KUBECONFIG. Start your agent in an empty folder with that KUBECONFIG, ask the prompt, then compare the answer with the scenario’s expected.md. The identity can only read, so the agent cannot change anything. When you