k8s-manifest-generator — Claude Code skill: manifests and setup
This skill generates Kubernetes manifests for application resources and configuration. Use it when you need Deployments, Services, ConfigMaps, Secrets, or PersistentVolumeClaims.
/plugin marketplace add wshobson/agents
/plugin install kubernetes-operations@claude-code-workflowsWhat k8s-manifest-generator does
k8s-manifest-generator guides an agent through Kubernetes YAML for Deployment, Service, ConfigMap, Secret, and PersistentVolumeClaim. It covers resource requests and limits, health checks, security contexts, labels, naming conventions, and specific image tags.
The skill also covers separating configuration from code, validating manifests before applying them, keeping them in Git, and preparing configurations for multiple environments. More detailed patterns are stored in references/details.md. Troubleshooting examples use commands such as kubectl describe pod <pod-name>, kubectl get events --sort-by='.lastTimestamp', and kubectl get configmap,secret.
Check the Service selector against Pod labels before debugging connectivity. A mismatch leaves the Service without the expected endpoints. The skill is available for Claude Code, Codex, and Cursor.
What it helps with
- create a Deployment for an application
- define a Service for network connectivity
- separate settings into ConfigMaps and Secrets
- add health checks and security contexts
- prepare a PersistentVolumeClaim for stateful workloads
Example prompts for the agent
- Generate Kubernetes manifests for my application: `Deployment`, `Service`, `ConfigMap`, and `Secret`. Add resource requests, limits, and health checks.
- Create a stateful workload manifest with `PersistentVolumeClaim`, standard labels, and a security context. Check the references between the resources.
- Investigate why the Pod is not starting with `kubectl describe pod <pod-name>`, `kubectl get nodes`, and `kubectl get events --sort-by='.lastTimestamp'`.
How to install k8s-manifest-generator
1Plugin marketplace
/plugin marketplace add wshobson/agents/plugin install kubernetes-operations@claude-code-workflowsThis installs the whole kubernetes-operations plugin with all its skills
2Skills CLI (Vercel)
npx skills add wshobson/agents --skill k8s-manifest-generator -a claude-code3Manually: put the files in place
~/.claude/skills/k8s-manifest-generator/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/k8s-manifest-generator/
1Skills CLI (Vercel)
npx skills add wshobson/agents --skill k8s-manifest-generator -a codex2Manually: put the files in place
.agents/skills/k8s-manifest-generator/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add wshobson/agents --skill k8s-manifest-generator -a cursor2Manually: put the files in place
.cursor/skills/k8s-manifest-generator/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install wshobson/agents k8s-manifest-generator2Manually: put the files in place
.github/skills/k8s-manifest-generator/SKILL.mdPlatform CLI
gemini skills install https://github.com/wshobson/agents --path plugins/kubernetes-operations/skills/k8s-manifest-generatorManually: put the files in place
.devin/skills/k8s-manifest-generator/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set213
The whole set →Similar
Questions about k8s-manifest-generator
How do I install k8s-manifest-generator in Claude Code?
Run /plugin marketplace add wshobson/agents, then run /plugin install kubernetes-operations@claude-code-workflows.
What does k8s-manifest-generator do?
It guides the agent in creating Kubernetes manifests for Deployment, Service, ConfigMap, Secret, and PersistentVolumeClaim, with resource limits, health checks, and security settings.
What should I check when a Service is not reachable?
Check whether the Service selector matches the Pod labels, then review the Service type and port. Use kubectl get endpoints <service-name> to inspect the endpoints.
Source text
SKILL.md · MIT
--- name: k8s-manifest-generator description: Create production-ready Kubernetes manifests for Deployments, Services, ConfigMaps, and Secrets following best practices and security standards. Use when generating Kubernetes YAML manifests, creating K8s resources, or implementing production-grade Kubernetes configurations. --- # Kubernetes Manifest Generator Step-by-step guidance for creating production-ready Kubernetes manifests including Deployments, Services, ConfigMaps, Secrets, and PersistentVolumeClaims. ## Purpose This skill provides comprehensive guidance for generating well-structured, secure, and production-ready Kubernetes manifests following cloud-native best practices and Kubernetes conventions. ## When to Use This Skill Use this skill when you need to: - Create new Kubernetes Deployment manifests - Define Service resources for network connectivity - Generate ConfigMap and Secret resources for configuration management - Create PersistentVolumeClaim manifests for stateful workloads - Follow Kubernetes best practices and naming conventions - Implement resource limits, health checks, and security contexts - Design manifests for multi-environment deployments ## Detailed patterns and worked examples Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient. ## Best Practices Summary 1. **Always set resource requests and limits** - Prevents resource starvation 2. **Implement health checks** - Ensures Kubernetes can manage your application 3. **Use specific image tags** - Avoid unpredictable deployments 4. **Apply security contexts** - Run as non-root, drop capabilities 5. **Use ConfigMaps and Secrets** - Separate config from code 6. **Label everything** - Enables filtering and organization 7. **Follow naming conventions** - Use standard Kubernetes labels 8. **Validate before applying** - Use dry-run and validation tools 9. **Version your manifests** - Keep in Git with version control 10. **Document with annotations** - Add context for other developers ## Troubleshooting **Pods not starting:** - Check image pull errors: `kubectl describe pod <pod-name>` - Verify resource availability: `kubectl get nodes` - Check events: `kubectl get events --sort-by='.lastTimestamp'` **Service not accessible:** - Verify selector matches pod labels: `kubectl get endpoints <service-name>` - Check service type and port configuration - Test from within cluster: `kubectl run debug --rm -it --image=busybox -- sh` **ConfigMap/Secret not loading:** - Verify names match in Deployment - Check namespace - Ensure resources exist: `kubectl get configmap,secret` ## Next Steps After creating manifests: 1. Store in Git repository 2. Set up CI/CD pipeline for deployment 3. Consider using Helm or Kustomize for templating 4. Implement GitOps with ArgoCD or Flux 5. Add monitoring and observability ## Related Skills - `helm-chart-scaffolding` - For templating and packaging - `gitops-workflow` - For automated deployments - `k8s-security-policies` - For advanced security configurations
© Seth Hobson · MIT · wshobson/agents