CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

75

Quality

94%

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

88%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, executable operator skill: concrete tool invocations, decision rules, and three workflows with explicit validation/triage checkpoints. It is near the top on actionability and workflow clarity; minor conciseness trims and verification of the referenced bundle files would lift the remaining two dimensions.

Suggestions

Trim conceptual restatement in the CRD-design and reconcile-loop principle lists (e.g. re-explaining the spec/status split and finalizer rationale) to push conciseness toward fully lean.

Verify the referenced reference/ and assets/ files (operator_pattern.md, crd_design.md, reconcile_loop.md, tooling_landscape.md, crd_template.yaml, reconcile_skeleton.go) actually ship in the bundle so the signaled navigation is real, not aspirational.

DimensionReasoningScore

Conciseness

Lean, task-focused prose that assumes Claude knows Kubernetes — the reconcile diagram, the 7 failure modes, and the bullet check-lists earn their tokens. It edges toward 5 but a few sections re-explain well-known concepts (e.g. restating 'spec is what the user wants; status is what the controller observed' and basic finalizer/leader-election rationale) that could be trimmed, so it sits noticeably above the 3 anchor but short of fully lean.

4 / 5

Actionability

Fully executable copy-paste guidance: concrete `python "$SKILL/scripts/..." --crd ...` commands, explicit per-tool check lists, framework decision rules, and three numbered end-to-end workflows. Specific examples cover the common operator-building and -auditing cases.

5 / 5

Workflow Clarity

The three workflows are clearly sequenced with explicit validation checkpoints — e.g. Workflow 1 step 4 'Fix every WARN before writing controller code' and step 7 'confirm L1', and Workflow 2's triage matrix ('FAIL → block release; WARN → fix in next 30 days') provides the validate→fix feedback loop the rubric rewards for batch/audit operations.

5 / 5

Progressive Disclosure

SKILL.md is an overview with well-signaled one-level-deep references (references/operator_pattern.md, crd_design.md, reconcile_loop.md, tooling_landscape.md) plus inline 'See ... for full detail. Quick rules:' summaries, and clearly listed scripts and asset templates. It does not reach 5 because the referenced reference files and asset templates are not present in the bundle to verify, so navigation is signaled but unconfirmed against actual files.

4 / 5

Total

18

/

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.

A model description: concrete actions, an explicit 'Use when' trigger clause with natural keywords, and an explicit boundary statement distinguishing it from generic k8s skills. All four dimensions land at the top of the scale.

DimensionReasoningScore

Specificity

Lists multiple concrete, specific actions — 'Ships CRD validator, reconcile-loop linter, and OperatorHub capability auditor (all stdlib Python)' plus 'a /operator-audit slash command' — with comprehensive coverage of what the skill provides.

5 / 5

Completeness

Explicitly answers both 'what' (custom controllers that reconcile CRD state + the 3 shipped tools) and 'when' (an explicit 'Use when building a Kubernetes Operator' clause followed by concrete trigger phrases), matching the score-5 anchor for clear what-and-when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including both framework names users would actually say ('build an operator', 'CRD design', 'reconcile loop', 'controller-runtime', 'kubebuilder', 'operator-sdk', 'metacontroller', 'KOPF') and capability-level synonyms, spanning the whole operator tooling vocabulary.

5 / 5

Distinctiveness Conflict Risk

A clear niche (the Operator pattern, not generic k8s) with a 'NOT a generic k8s skill — specifically the Operator pattern' boundary statement, giving distinct triggers and minimal conflict risk against sibling skills like helm-chart-builder or senior-devops.

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.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 14 missing

Warning

Total

14

/

16

Passed

Repository
alirezarezvani/claude-skills
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.