CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

77

Quality

97%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is kubernetes-operator in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

96%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong, dense body: every section is actionable with real commands, workflows carry explicit validation and triage gates, and detail is properly deferred to verified one-level-deep references. The only weakness is deliberate duplication of the same anti-patterns across four sections, which costs tokens without adding guidance.

DimensionReasoningScore

Conciseness

Efficient and assumes Claude's competence — no basic Kubernetes explanations — but the same anti-patterns are repeated across 'Core principle' (7 failure modes), the tool check lists, 'Reconcile loop principles', and 'Anti-patterns' (time.Sleep and status-vs-spec each appear three to four times). This trimmable duplication keeps it at anchor 4 rather than 5, while the absence of any explanation of known concepts keeps it above anchor 3.

4 / 5

Actionability

Fully executable, copy-paste-ready commands throughout: 'python "$SKILL/scripts/crd_validator.py" --crd config/crd/myapp.yaml', 'kubebuilder init --domain example.com --repo github.com/org/myapp-operator', and 'python scripts/reconcile_lint.py --controller controllers/myapp_controller.go', plus enumerated checks and concrete decision rules ('New operator + Go shop → kubebuilder') covering the common cases.

5 / 5

Workflow Clarity

Three numbered workflows with explicit validation checkpoints and feedback loops: 'Fix every WARN before writing controller code', 'Run reconcile_lint.py', 'confirm L1', and audit triage rules 'FAIL → block release; fix before next deploy / WARN → file an issue; fix in next 30 days'. Sequence, checkpoints, and error-recovery paths are all explicit.

5 / 5

Progressive Disclosure

The body is an overview with quick rules inline while full detail is pushed to four clearly signaled, one-level-deep references ('See references/crd_design.md for full detail', plus a References section), and all referenced files (4 references, 3 scripts, 2 assets) exist in the bundle with no nested cross-references. Navigation is easy and content is appropriately split.

5 / 5

Total

19

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is exemplary: concrete capabilities, explicit when-to-use triggers covering every relevant framework name, third-person voice, and an explicit boundary against adjacent k8s skills. It clearly matches the top anchor on all four dimensions.

DimensionReasoningScore

Specificity

Lists multiple specific concrete capabilities — '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' — with comprehensive coverage of what the skill provides. Uses third-person voice throughout ('Ships', 'Triggers'), and the anchor-4 gap (minor coverage gaps) does not apply.

5 / 5

Completeness

Explicitly answers both what ('custom controllers that reconcile CRD state' plus the shipped validator/linter/auditor tooling) and when ('Use when building a Kubernetes Operator ... Triggers on ...') with concrete trigger phrases, matching the anchor-5 example structure exactly.

5 / 5

Trigger Term Quality

Comprehensive natural trigger terms including synonyms and all framework names a user would actually say: '"build an operator", "CRD design", "reconcile loop", "controller-runtime", "kubebuilder", "operator-sdk", "metacontroller", "KOPF", "operator capability levels", or "custom resource"'. No common variation is missing.

5 / 5

Distinctiveness Conflict Risk

Clear niche (the Operator pattern) with an explicit negative boundary — 'NOT a generic k8s skill — specifically the Operator pattern' — which distinguishes it from general Kubernetes, Helm, and devops skills. Minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

alirezarezvani/claude-skills

Path

engineering/skills/kubernetes-operator/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.