Use when deploying or managing Kubernetes workloads. Invoke to create deployment manifests, configure pod security policies, set up service accounts, define network isolation rules, debug pod crashes, analyze resource limits, inspect container logs, or right-size workloads. Use for Helm charts, RBAC policies, NetworkPolicies, storage configuration, performance optimization, GitOps pipelines, and multi-cluster management.
The author's original description, preserved in English. It describes intent, not verified performance.
Use when deploying or managing Kubernetes workloads. Invoke to create deployment manifests, configure pod security policies, set up service accounts, define network isolation rules, debug pod crashes, analyze resource limits, inspect container logs, or right-size workloads. Use for Helm charts, RBAC policies, NetworkPolicies, storage configuration, performance optimization, GitOps pipelines, and multi-cluster management.
A Kubernetes Skill that produces declarative manifests with resource limits, probes, RBAC and NetworkPolicies, then validates rollout with kubectl.
Review scope
Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.
Observable capabilities
Writes declarative Deployment, Service and related manifests with requests, limits and health probes.
Applies least-privilege RBAC and default-deny NetworkPolicies.
Avoids latest tags, default ServiceAccounts and plain-text secrets.
Validates with rollout status, describe, logs and rollback commands.
Limitations & scope
Requires cluster access and kubectl for the validation commands to be meaningful.
Helm, GitOps, service mesh and multi-cluster detail sits in separate reference files.
Manifests are not tested against any real cluster here.
Relevant for
Platform and DevOps engineers
Developers packaging apps for Kubernetes
Teams hardening workload security
02 / STRUCTURE
What ships with the skill
The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.
{
"name": "kubernetes-specialist",
"description": "Use when deploying or managing Kubernetes workloads. Invoke to create deployment manifests, configure pod security policies, set up service accounts, define network isolation rules, debug pod crashes, analyze resource limits, inspect container logs, or right-size workloads. Use for Helm charts, RBAC policies, NetworkPolicies, storage configuration, performance optimization, GitOps pipelines, and multi-cluster management.",
"license": "MIT",
"metadata": {
"author": "https://github.com/Jeffallan",
"company": "https://synergetic.solutions",
"version": "1.1.2",
"domain": "infrastructure",
"triggers": "Kubernetes, K8s, kubectl, Helm, container orchestration, pod deployment, RBAC, NetworkPolicy, Ingress, StatefulSet, Operator, CRD, CustomResourceDefinition, ArgoCD, Flux, GitOps, Istio, Linkerd, service mesh, multi-cluster, cost optimization, VPA, spot instances",
"role": "specialist",
"scope": "infrastructure",
"output-format": "manifests",
"related-skills": "devops-engineer, cloud-architect, sre-engineer, terraform-engineer, security-reviewer, chaos-engineer"
}
}
03 / WORKFLOW
A reading of the operating sequence
This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.
01
Input
Gather workload requirements
Understand workload characteristics, scaling needs and security requirements.
Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.
Attention recommended
104 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.
Network accessObserved
File writesObserved
Credential useObserved
High
Credential or secret material is referenced
12 occurrences
This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 12 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.
This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 32 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.
A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 56 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.
Privilege-elevation syntax is present. Confirm whether elevation is necessary and inspect every operation performed under it; static analysis cannot prove that elevation succeeded. This rule matched 1 location(s) in the collected text; 1 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.
This line combines retrieval and execution. Such patterns can run mutable remote code. Review pinning, integrity checks, and isolation; the analyzer performed no download or execution. This rule matched 3 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.
Confirm the kubectl context and namespace before running any command the agent suggests, especially rollout undo.
05 / CONTEXT
Where context can be spent
Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.
Exact token counts unavailable
All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.
No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.
06 / EVALUATION
Controlled evaluation
No controlled evaluation
This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.
Not tested
07 / USAGE
Use with the source in view
Install command
git clone https://github.com/Jeffallan/claude-skills.git
cd claude-skills
# Copy this skill directory into one of:
# ~/.claude/skills/kubernetes-specialist
# .claude/skills/kubernetes-specialist
Open the pinned source at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/kubernetes-specialist/SKILL.md.
Review the license, prerequisites and all bundled reference files.
Copy the skill directory into a personal or project-level Claude Code skills directory.
Restart or refresh Claude Code so the skill can be discovered.
Verify installation
Ask Claude Code for a Deployment manifest and confirm it includes resource limits, probes, a dedicated ServiceAccount and a pinned image tag.
Prerequisites
Requires cluster access and kubectl for the validation commands to be meaningful.
Helm, GitOps, service mesh and multi-cluster detail sits in separate reference files.
Manifests are not tested against any real cluster here.
Example prompts
Representative task
Using the kubernetes-specialist skill, write manifests for a stateless web app in namespace shop with 3 replicas, probes, a least-privilege ServiceAccount and a default-deny NetworkPolicy allowing only the frontend.
Inspect before use
Read the kubernetes-specialist skill at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/kubernetes-specialist/SKILL.md and its reference files. Explain its workflow, any commands it tells the agent to run, and the main risks before I decide whether to install it.
08 / VERDICT
A decision, with its limits attached
Strengths
Concrete YAML patterns for security context, RBAC and NetworkPolicy.
Includes a validation and rollback command set.
Considerations
Strict defaults such as read-only root filesystem may need adjusting per workload.
Commands such as rollout undo change live cluster state.
Research conclusion
A security-conscious baseline for writing and checking Kubernetes manifests.
09 / PROVENANCE
Traceable by construction
The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.
Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.