Kubernetes Specialist
Use when deploying or managing Kubernetes workloads.
Before & after
Same prompt, same agent — the only difference is the skill.
Deploying to Kubernetes involves setting up several components. You'd need a deployment manifest to define your container, configure how many replicas to run, and set up services so traffic can reach your app. You might also want to think about resource limits and security settings. There are quite a few options to consider. Do you have a Kubernetes cluster already? What's your app written in? Are there specific security requirements you need to meet? I could walk you through the general process if you'd like.
KUBERNETES DEPLOYMENT MANIFEST
apiVersion: v1
kind: Namespace
metadata:
name: production
---
apiVersion: v1
kind: ServiceAccount
metadata:
name: app-runner
namespace: production
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: api-server
namespace: production
spec:
replicas: 3
selector:
matchLabels:
app: api-server
template:
metadata:
labels:
app: api-server
spec:
serviceAccountName: app-runner
securityContext:
runAsNonRoot: true
runAsUser: 1000
fsReadOnlyRootFilesystem: true
containers:
- name: api
image: myregistry.azurecr.io/api-server:1.0
imagePullPolicy: IfNotPresent
ports:
- containerPort: 8080
resources:
requests:
memory: 512Mi
cpu: 250m
limits:
memory: 1Gi
cpu: 500m
livenessProbe:
httpGet:
path: /health
port: 8080
initialDelaySeconds: 30
periodSeconds: 10
securityContext:
allowPrivilegeEscalation: false
readOnlyRootFilesystem: true
capabilities:
drop: [ALL]
volumeMounts:
- name: tmp
mountPath: /tmp
volumes:
- name: tmp
emptyDir: {}
---
apiVersion: v1
kind: Service
metadata:
name: api-service
namespace: production
spec:
type: ClusterIP
selector:
app: api-server
ports:
- port: 80
targetPort: 8080
NETWORK POLICY (Pod-to-Pod only)
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: default-deny
namespace: production
spec:
podSelector: {}
policyTypes:
- Ingress
ingress:
- from:
- podSelector:
matchLabels:
role: frontend
DEPLOYMENT STEPS
1. Apply manifest: kubectl apply -f deployment.yaml
2. Verify: kubectl get pods -n production
3. Check logs: kubectl logs -f deployment/api-server -n production
4. Test health: kubectl port-forward svc/api-service 8080:80
5. Monitor: Watch resource usage via kubectl top podsAbout this skill
name: kubernetes-specialist description: Use when Use when deploying or managing Kubernetes workloads.
Kubernetes Specialist
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.
What you get
- Public GitHub repo
- the skills/kubernetes-specialist folder with SKILL.md and references.
Customize your output
- Fork the repo and extend the skill's reference files for your own stack conventions.
Example output
Activates on a matching request (e.g. building or reviewing Kubernetes Specialist code) and can chain with other skills in the pack.
Best for
Full-stack developers and engineering teams using Claude Code.
SKILL.md preview
---
name: kubernetes-specialist
description: Use when deploying, securing, or debugging Kubernetes workloads, including manifests, Helm charts, RBAC, and GitOps pipelines.
version: 1.0.0
category: Development / DevOps & Infra
author: AgentVolt
license: proprietary
tags:
- development
- devops-infra
---
# Kubernetes Specialist
Creates deployment manifests, configures pod security and service accounts, defines network isolation, and debugs pod crashes and resource sizing.
## When to use
… (sign up to view the full skill)More development skills
View all Development skills →Chaos Engineer
Designs controlled failure experiments — from a single fault injection to a full game day — and produces the runbook, rollback plan.
Devops Engineer
Creates Dockerfiles, configures CI/CD pipelines, writes Kubernetes manifests, and generates Terraform/Pulumi infrastructure templates.
Cloud Architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP.
Sre Engineer
Defines service level objectives, creates error budget policies, designs incident response procedures, develops capacity models.