⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
kubernetes-skill
Prevent Kubernetes hallucinations by diagnosing and fixing failure modes: insecure workload defaults, resource starvation, network exposure, privilege sprawl, fragile rollouts, and API drift. Use when generating, reviewing, refactoring, or migrating manifests, Helm charts, Kustomize overlays, cluster policies, and platform-specific Kubernetes work for EKS, GKE, AKS, OpenShift, GitOps controllers, or observability stacks.
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
Kubernetes Skill for Claude Code and Codex: KubeShark
The #1 Kubernetes skill for Claude Code and Codex, measured by GitHub stars.
Fixes Hallucinations.
LLMs hallucinate a lot when it comes to Kubernetes. They omit security contexts, generate deprecated APIs, use wildcard RBAC, forget resource limits, and produce probes that cause cascading failures. This skill fixes it. It includes best practices for Kubernetes -- good, bad, and neutral examples so the AI avoids common mistakes. Using KubeShark, the AI keeps proven practices in mind, eliminates hallucinations, and defaults to secure, reliable, production-ready manifests.
KubeShark is built as the production-grade Kubernetes skill for Claude Code and Codex: broader than resource-template skills, safer than generic Kubernetes prompts, and tuned for hallucination prevention instead of raw tutorial volume.
Very Token-Efficient.
Most Kubernetes skills dump huge walls of text onto the agent and burn expensive tokens -- with no upside. LLMs don't need the entire Kubernetes docs again. KubeShark was aggressively de-duplicated and optimized for maximum quality per token.
Based on Official Best Practices.
KubeShark is primarily based on the official Kubernetes documentation, the NSA/CISA Kubernetes Hardening Guide, OWASP Kubernetes Top 10, Pod Security Standards, and the CIS Kubernetes Benchmark. When guidance conflicts, it prioritizes official Kubernetes documentation.
Quick Start · Why KubeShark · Token Strategy · What's Included · How It Works · Sponsor · Philosophy
2 min Quickstart
Option 1: Skills CLI
If you manage skills with the skills CLI, install KubeShark directly from GitHub:
npx skills add https://github.com/lukasniessen/kubernetes-skill --skill kubernetes-skill
Option 2: Clone
macOS / Linux:
git clone https://github.com/LukasNiessen/kubernetes-skill.git ~/.claude/skills/kubernetes-skill
Windows (Powershell):
git clone https://github.com/LukasNiessen/kubernetes-skill.git "$env:USERPROFILE\.claude\skills\kubernetes-skill"
Windows (Command Prompt):
git clone https://github.com/LukasNiessen/kubernetes-skill.git "%USERPROFILE%\.claude\skills\kubernetes-skill"
That's it. Claude Code auto-discovers skills in ~/.claude/skills/ -- no restart needed.
Option 3: Marketplace
Claude Code has a built-in plugin system with marketplace support. Instead of cloning manually, you can add KubeShark's marketplace and install directly from the CLI:
/plugin marketplace add LukasNiessen/kubernetes-skill
/plugin install kubernetes-skill
Or use the interactive plugin manager -- run /plugin, switch to the Discover tab, and install from there. The marketplace reads the .claude-plugin/marketplace.json in this repo to register KubeShark as an installable plugin.
Option 4: Codex
Codex has no global skill system -- setup is per-project. Clone KubeShark into your repo and reference it from your AGENTS.md:
# Clone into your project root
git clone https://github.com/LukasNiessen/kubernetes-skill.git .kubernetes-skill
Then add to your AGENTS.md (or create one in the repo root):
## Kubernetes
When working with Kubernetes manifests, Helm charts, or Kustomize overlays, follow the workflow in `.kubernetes-skill/SKILL.md`.
Load references from `.kubernetes-skill/references/` as needed.
That's it!
Done. Now ask Claude Code / Codex any Kubernetes question. KubeShark responses follow the 7-step failure-mode workflow and include an output contract with assumptions, tradeoffs, and rollback notes.
Invoke explicitly:
/kubernetes-skill Create a production-ready Deployment with an Ingress and autoscaling
/kubernetes-skill Review my Deployment for security issues and add proper RBAC, NetworkPolicies, and resource limits
Or just ask naturally -- KubeShark activates automatically for any Kubernetes task:
Review my deployment.yaml for security issues
Create a Helm chart for a PostgreSQL StatefulSet with backup CronJobs
Why KubeShark
Overview
| Dimension | KubeShark | No Skill |
|---|---|---|
| SKILL.md activation cost | Low, procedural workflow only | 0 |
| Reference granularity | 26 focused files | -- |
| Token burn per query | Low (load only matched refs) | 0 |
| Architecture | Failure-mode workflow | -- |
| Diagnoses before generating | Yes (Step 2) | No |
| Output contract | Yes -- assumptions, tradeoffs, rollback | No |
| Conditional references | EKS, GKE, AKS, OpenShift, GitOps, observability stacks | No |
| Security-first defaults | PSS restricted profile | No |
| Good/bad examples | Yes (2 dedicated files) | No |
| Do/Don't checklist | Yes (dedicated file) | No |
| Compliance coverage | NSA/CISA, OWASP K8s Top 10, CIS, Pod Security Standards | No |
| Hallucination prevention | Core design goal | No |
| Cross-resource validation | Label/selector/port consistency checks | No |
| Helm/Kustomize guidance | Dedicated reference files | No |
| Policy engine integration | Kyverno and OPA/Gatekeeper patterns | No |
| License | MIT | -- |
Why Failure-Mode-First Matters for Kubernetes
The key insight is architectural. A static reference manual gives Claude information but never tells it how to think about a problem. There's no diagnosis step, no risk assessment, and no structured output -- Claude reads the reference and generates whatever it thinks fits.
KubeShark takes the opposite approach. The core SKILL.md is a compact operational workflow. It forces Claude through a diagnostic sequence: capture context -> identify failure modes -> load only the relevant references -> propose fixes with explicit risk controls -> validate -> deliver a structured output contract.
This matters for Kubernetes specifically because:
- Silent failures are common. A Service with the wrong selector depl
// HOW IT'S BUILT
KEY FILES