kubernetes-operator
Use when building a Kubernetes Operator — custom controllers that reconcile CRD state. Triggers on "build an operator", "CRD design", "reconcile loop", "controller-runtime", "kubebuilder", "operator-sdk", "metacontroller", "KOPF", "operator capability levels", or "custom resource". Ships CRD validator, reconcile-loop linter, and OperatorHub capability auditor (all stdlib Python), 4 references on the operator pattern + CRD design + reconcile patterns + tooling landscape, and a /operator-audit slash command. NOT a generic k8s skill — specifically the Operator pattern.
Profile →npx skills add alirezarezvani/claude-skills --skill kubernetes-operator --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Kubernetes Operator Build operators that reconcile correctly. Most operator bugs are not Kubernetes bugs — they are reconcile-loop bugs: missing finalizers, blocking calls, no requeue on transient errors, status drift, RBAC over-grants. This skill catches them deterministically before they reach a cluster. ## When to use - Building a new Kubernetes Operator (controller for a CRD) - Reviewing an existing operator for capability-level gaps - Auditing a CRD spec for status/conditions/finalizer correctness - Choosing a framework (controller-runtime / kubebuilder / operator-sdk / metacontroller / KOPF) - Designing the API surface of a Custom Resource - Hardening RBAC, leader election, or webhook validation ## When NOT to use - Plain Helm chart packaging → use `helm-chart-builder` - Standard kubectl operations / blue-green deploys → use `senior-devops` - General k8s security posture → use `cloud-security` - "I want to run a workload" — that's a Deployment / Job, not an operator ## Core principle: an operator is a reconcile loop, not a script ``` observe(actual) → desired = read(spec) → diff(actual, desired) → act → update(status) ↓ requeue / done ``` Operators that fail are the ones th
- When to use
- When NOT to use
- Core principle: an operator is a reconcile loop, not a script
- Quick start
- The 3 Python tools
- crdvalidator.py
- reconcilelint.py
- operatorcapabilityaudit.py
- Tooling landscape
- CRD design principles
- Reconcile loop principles
- Workflows
- Workflow 1: Bootstrap a new operator (Go + kubebuilder)
- Workflow 2: Audit an existing operator
Validate a CRD design python "$SKILL/scripts/crd_validator.py" --crd config/crd/myapp.yaml Lint a Go reconcile function python "$SKILL/scripts/reconcile_lint.py" --controller controllers/myapp_controller.go Score against OperatorHub Capability Levels (1-5) python "$SKILL/scripts/operator_capability_audit.py" --operator-dir . python scripts/crd_validator.py --crd config/crd/myapp.yaml python scripts/crd_validator.py --crd config/crd/ --format json python scripts/reconcile_lint.py --controller controllers/myapp_controller.go python scripts/operator_capability_audit.py --operator-dir .
What does the kubernetes-operator skill do?
Use when building a Kubernetes Operator — custom controllers that reconcile CRD state. Triggers on "build an operator", "CRD design", "reconcile loop", "controller-runtime", "kubebuilder", "operator-sdk", "metacontroller", "KOPF", "operator capability levels", or "custom resource". Ships CRD validator, reconcile-loop linter, and OperatorHub capability auditor (all stdlib Python), 4 references on the operator pattern + CRD design + reconcile patterns + tooling landscape, and a /operator-audit slash command. NOT a generic k8s skill — specifically the Operator pattern.
How do I install it?
Run `npx skills add alirezarezvani/claude-skills --skill kubernetes-operator --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From alirezarezvani/claude-skills, a repository with 23,791 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.