Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →borghei/kubernetes-operator
Design, build, and operate Kubernetes operators.
Passed 22 of 22 test cases with the skill, and 18 of 22 without it.
and 3 more in the full report
4 fixed18 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
We want to generate a new Go operator project skeleton for an object named `Queue` under group `messaging.io` called `queue-operator`. What exact command string executes the scaffold script with all required identity options?
| Checked | Without skill | With skill |
|---|---|---|
| Uses the --name queue-operator parameter | Missed | Passed |
| Uses the --group messaging.io parameter | Missed | Passed |
| Uses the --kind Queue parameter | Passed | Passed |
The instructions your model reads when the skill loads.
End-to-end Kubernetes operator design and construction. Covers the operator pattern (control loops for stateful workloads), CRD design (schema, validation, conversion, status), the reconciliation loop (idempotency, convergence, level- vs edge-triggered), framework selection (controller-runtime / Kubebuilder / operator-SDK / metacontroller), and operational concerns (finalizers, leader election, RBAC scoping, status subresource, observability). Targets Go-based operators (the dominant ecosystem) with notes on alternatives (KOPF, JOSDK, kube-rs).
| Situation | Skill applies |
|---|---|
| Building a new operator for an internal platform primitive | Yes — start with the operator pattern decision |
| Auditing an existing operator for production-readiness | Yes — use anti-patterns + scripts/reconciliation_audit.py |
| Designing CRDs for a custom resource | Yes — use CRD design + scripts/crd_validator.py |
| Deciding "operator vs Helm chart vs plain manifests" | Yes — use the decision matrix |
| Scaffolding a new operator project | Yes — scripts/operator_scaffold.py |
| Debugging a controller that "isn't reconciling" | Yes — use reconciliation troubleshooting |
| Just running someone else's operator (Postgres, Kafka, etc.) | Partially — useful for understanding what it does and how to monitor it |
Before scaffolding or auditing, confirm these inputs. If any is unknown or vague, ASK — do not assume:
operator_scaffold.py vs crd_validator.py vs reconciliation_audit.py)--name/--group/--kind); for validation/audit: the CRD YAML or controller path (the input the scripts read)Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
| Tool | Purpose | Command |
|---|
test cases passed, vs 18 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.