What is kubernetes-expert?

A guide for running applications on Kubernetes, a system that deploys and manages containers across servers. It covers workloads, networking, configuration, health checks, resource limits, scaling, and troubleshooting.

Use it to write and review Kubernetes manifests, configure probes and resources, manage rollouts and autoscaling, and troubleshoot deployments with Helm or Kustomize.

It helps choose the right Kubernetes resource and diagnose failures such as containers restarting, images not downloading, or pods running out of memory.

kubernetes-expert — Skill for Claude Code by Miaoge-Ge

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add Miaoge-Ge/coding-agent-skills --skill kubernetes-expert

Clone the repo

git clone --depth 1 https://github.com/Miaoge-Ge/coding-agent-skills

Made for: Claude Code.

Or install kubernetes-expert, the plugin that ships this one along with the rest of its 1 skill.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/miaoge-ge/coding-agent-skills/kubernetes-expert/github.svg)](https://agentmods.dev/skills/miaoge-ge/coding-agent-skills/kubernetes-expert)

Your own site

<a href="https://agentmods.dev/skills/miaoge-ge/coding-agent-skills/kubernetes-expert"><img src="https://agentmods.dev/badge/skills/miaoge-ge/coding-agent-skills/kubernetes-expert/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/miaoge-ge/coding-agent-skills/kubernetes-expert"><img src="https://agentmods.dev/badge/skills/miaoge-ge/coding-agent-skills/kubernetes-expert.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 93 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,105 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00093	$0.01105
Opus 5	$0.00046	$0.00553
Sonnet 5	$0.00019	$0.00221
Haiku 4.5	$0.00009	$0.00111

Measured 10d ago against content hash 7816667a1006, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

kubernetes-expert scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/kubernetes-expert/skills/kubernetes-expert/SKILL.md · 80 lines

How it starts

The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Kubernetes Expert

Declarative, resilient, right-sized. Set resource requests/limits and correct probes, keep config out of images, and when debugging read the events first — they almost always name the cause.

When to Use

Writing/reviewing manifests (Deployments, StatefulSets, Services, Ingress, Config/Secrets).
Probes, resource requests/limits, autoscaling (HPA), rollouts.
Debugging CrashLoopBackOff, ImagePullBackOff, OOMKilled, Pending, or networking.
Templating with Helm/Kustomize.

When NOT to Use

Building the container image → docker-expert.
App-level bugs inside the container → relevant language skill.
CI/CD pipeline wiring → github-master.

Core Principles

1. Pick the right workload

Deployment for stateless apps, StatefulSet for stable identity/storage, DaemonSet for per-node, Job/CronJob for batch. Don't run databases as a plain Deployment.

2. Resources & scheduling

Always set requests and limits. Requests drive scheduling and guarantees; limits cap usage. Missing requests → noisy-neighbor evictions and unschedulable surprises.
Memory limit too low → OOMKilled. CPU limit throttles (doesn't kill). Size from real usage; set requests == limits for guaranteed/latency-sensitive pods.

3. Health & rollouts

Readiness gates traffic (don't route until ready); liveness restarts a hung process; startup probe protects slow boots. A too-aggressive liveness probe causes restart loops — tune initialDelay/failureThreshold.
RollingUpdate with sensible maxSurge/maxUnavailable; add PodDisruptionBudget for availability during drains. Pin image tags/digests, never :latest.

4. Config, secrets, security

Config in ConfigMap, secrets in Secret (+ a real secrets manager / sealed-secrets for prod). Never bake them into images. Roll pods on config change (checksum annotation).
Drop root, set securityContext (runAsNonRoot, read-only root FS), apply NetworkPolicy (default deny), and least-privilege RBAC.

Read the full file on GitHub · 80 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

10d ago First seen · 80 lines · 93 tokens per session scan A 7816667a1006

Subscribe to this mod's changes

kubernetes-expert is a skill published in the GitHub repository Miaoge-Ge/coding-agent-skills (5 stars, last pushed 3mo ago), licensed MIT. It adds 93 tokens to every session and 1,105 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude Code Cloud Containers DevOps and cloud ai coding-assistant cursor prompt-engineering system-prompts

dokploy-deploy

This skill should be used when user asks to "deploy with Dokploy", "use Dokploy Cloud", "manage self-hosted Dokploy", "deploy Docker Compose on Dokploy", "manage Dokploy databases", "configure Dokploy domains", or "look up Dokploy CLI commands".

fcakyon/claude-codex-settings · 63 tokens

qdrant-deployment-options

Guides Qdrant deployment selection. Use when someone asks 'how to deploy Qdrant', 'Docker vs Cloud', 'local mode', 'embedded Qdrant', 'Qdrant EDGE', 'which deployment option', 'self-hosted vs cloud', or 'need lowest latency deployment'. Also use when choosing between deployment types for a new project.

qdrant/skills · 79 tokens

kubernetes-expert