kubernetes-operations

Kubernetes operations including manifests, Helm charts, operators, troubleshooting, and resource management

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/kubernetes-operations/SKILL.md

Quality

Content

80%

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

The content is a strong, executable Kubernetes operations quick-reference: lean, concrete, and copy-paste-ready. Its main gaps are the absence of validation feedback loops for destructive operations and a monolithic single-file structure that could offload detailed manifests to reference files.

Suggestions

Add a brief deployment workflow with an explicit validation checkpoint, e.g. "kubectl apply -f deploy.yaml" → "kubectl rollout status deployment/api-server" → on failure rollback and re-check.

Move full canonical manifests and the troubleshooting command catalog into reference files (e.g. references/manifests.md, references/troubleshooting.md) and keep SKILL.md as a concise overview pointing to them.

Add a short "Prerequisites/Verification" note so destructive operations like scaling or applying manifests include a verify-then-proceed loop.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient: it presents manifests and commands directly without explaining Kubernetes/Pod/Deployment concepts Claude already knows, and the few prose lines (e.g. "Always set resource requests and limits") are useful guidance rather than padding.	3 / 3
Actionability	It provides fully executable, copy-paste-ready YAML manifests (Deployment, HPA, values.yaml) and concrete kubectl commands with realistic flags and clearly marked placeholders, matching anchor 3.	3 / 3
Workflow Clarity	The content is well organized by topic and includes a checklist, but it is a reference catalog rather than a sequenced workflow and lacks explicit apply→verify→rollback feedback loops for the destructive/batch operations (kubectl apply, scaling, deployment changes) the rubric flags, capping it at 2.	2 / 3
Progressive Disclosure	The ~180-line file is well sectioned with no nested references, but it keeps full manifests and recipe blocks inline that could be split into reference files for a cleaner overview, matching anchor 2's "content that should be separate is inline".	2 / 3
	Total	10 / 12 Passed

Description

57%

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 names a distinct Kubernetes niche with several natural trigger terms but stops short of explicit "when to use" guidance and concrete action verbs. Adding a "Use when..." clause and more natural keyword variations (kubectl, k8s, pods, deployments) would lift it from good to strong.

Suggestions

Append an explicit trigger clause, e.g. "Use when working with Kubernetes clusters, deploying Helm charts, writing manifests, or troubleshooting pods and deployments."

Add natural keyword variations users actually say ("kubectl", "k8s", "pods", "deployments", "kubectl apply") to improve trigger-term coverage.

Reframe capability areas as concrete actions (e.g., "write and validate manifests", "package and install Helm charts", "scale and autoscale workloads") to raise specificity.

Dimension	Reasoning	Score
Specificity	The description names the Kubernetes domain and several concrete capability areas ("manifests, Helm charts, operators, troubleshooting, and resource management") but mostly uses noun-phrases rather than specific concrete actions, matching anchor 2 rather than the verb-rich anchor 3.	2 / 3
Completeness	It clearly states what the skill does but provides no "Use when..." clause or equivalent explicit trigger guidance; per the rubric guidelines, a missing explicit trigger caps completeness at 2.	2 / 3
Trigger Term Quality	It includes natural terms users would say ("Kubernetes", "Helm charts", "operators", "troubleshooting") but omits common variations like "kubectl", "k8s", "pods", and "deployments", so it lands at anchor 2 rather than full anchor 3 coverage.	2 / 3
Distinctiveness Conflict Risk	The triggers (Kubernetes, Helm charts, operators) form a clear, distinct niche unlikely to conflict with other skills, matching anchor 3; the broad "operations" framing is not enough to pull it down to 2.	3 / 3
	Total	9 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: rohitg00/awesome-claude-code-toolkit
Path: skills/kubernetes-operations/SKILL.md
Commit: ebdf1d5

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.