Index of every page on this site: llms.txt
All skills
wshobson avatar

/k8s-manifest-generator

@4220308
by Seth Hobsonwshobson/agents43k stars
4,518
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/wshobson/agents/k8s-manifest-generator

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈75 tokens for metadata: the name and description. ≈692 when used: this file. ≈14k more on demand in 6 files.

Description uses 3.8% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈300 characters, or 3.8%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning15d5 checks · Risk SAFE
  • Gen Agent Trust Hub15d

    This skill is a collection of production-ready Kubernetes templates and documentation designed to help users generate secure manifests. It promotes security best practices such as non-root user execution, dropping all capabilities, and using read-only root filesystems. No malicious code, exfiltration patterns, or obfuscation techniques were detected.

  • Socket21d

    No alerts

  • Snyk15d

    Risk: LOW · No issues

  • Runlayer8mo

    3/6 files flagged

  • ZeroLeaks7mo

    1 finding · Score: 82/100

Signed by skilld at 4220308. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 days ago.

Activeupdated 6 months ago
  • kubernetes
  • k8s
  • deployment
  • manifest
  • yaml
  • configmap
  • secrets
  • service
  • docker

README badge

README badge for wshobson/agents/k8s-manifest-generator

Generates production-ready Kubernetes manifests for Deployments, Services, ConfigMaps, Secrets, and PersistentVolumeClaims with built-in best practices like resource limits, health checks, and security contexts. Use this when you need to author K8s YAML that follows cloud-native conventions and is ready for multi-environment deployment.

Generated from the current SKILL.md.

What Kubernetes resource types does this skill cover?
The skill covers Deployments, Services, ConfigMaps, Secrets, and PersistentVolumeClaims. It provides patterns for each resource type and how to combine them in production configurations.
Does this skill generate Helm charts or Kustomize templates?
No. This skill produces standard Kubernetes YAML manifests. The skill documentation references Helm and Kustomize as next steps for templating, but does not generate them itself.
What security practices does this skill enforce?
The skill emphasizes security contexts (non-root users, dropped capabilities), resource limits to prevent starvation, health checks for availability, and separation of sensitive data via Secrets rather than embedding in manifests.
Can I use this skill for multi-environment deployments?
Yes. The skill is designed to help you create manifests that work across multiple environments and includes guidance on naming conventions, labeling, and configuration management patterns that support multi-environment setups.
Does this skill include validation or dry-run testing?
The skill mentions validation and dry-run as best practices to perform before applying manifests, but does not automate these checks itself. It recommends using standard Kubernetes tools like kubectl validate.

Generated from the current SKILL.md. These answers refresh after source changes.