How do I install the Kubernetes skill?

Run npx skillmds@latest add paulasilvatech/kubernetes in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Kubernetes skill do?

Use when editing tracked AKS, Kubernetes, Helm, Kustomize, or generated GitOps manifests. It is listed under DevOps & Infra on SkillMD.

Is Kubernetes safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Kubernetes?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Kubernetes free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Kubernetes?

paulasilvatech (@paulasilvatech) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Kubernetes by paulasilvatech — Agent Skill

Name: Kubernetes
Author: paulasilvatech

File contents

Kubernetes and Helm

Conventions

Use explicit versioned image tags; never use latest.
Apply standard app.kubernetes.io/* labels consistently to workloads, services, selectors, monitoring, and policy targets.
Set realistic resource requests and limits plus startup, readiness, and liveness probes that match the service contract.
Run as non-root, disallow privilege escalation, drop capabilities, use RuntimeDefault seccomp, and prefer a read-only root filesystem.
Use dedicated service accounts, namespace-scoped RBAC, Workload Identity, and least-privilege network policies.
Reference secrets through External Secrets or approved Key Vault integration; never commit a Kubernetes Secret value.
Keep namespaces, selectors, ports, service names, and Helm value keys consistent across related manifests.
Keep generated GitOps examples under scripts/golden-paths/; no root argocd/ path is assumed.
Preserve rollout safety with disruption budgets, topology constraints, and graceful termination where availability requires them.

Verification

YAML, Helm, and Kustomize rendering produce valid resources with no unresolved tokens.
Policy checks cover tags, resources, non-root execution, privilege, and registry restrictions.
Rendered workloads have immutable images, probes, resources, identity, and secret references.

Do / Do Not

Do	Do not
Render manifests and enforce identity, resources, probes, and policy controls.	Apply unrendered files or weaken controls to make a deployment pass.
Use immutable images and external secret references.	Use floating tags or commit secret values.

Checklist Before Opening a PR

The change matches this instruction's applyTo scope.
YAML, Helm, and Kustomize rendering pass without unresolved tokens.
Policy checks cover identity, privilege, network, resources, and registry rules.
Workloads use immutable images, probes, and external secret references.
No unrelated edits or unresolved placeholders remain.

---name: kubernetesdescription: Use when editing tracked AKS, Kubernetes, Helm, Kustomize, or generated GitOps manifests.---# Kubernetes and Helm## Conventions- Use explicit versioned image tags; never use `latest`.- Apply standard `app.kubernetes.io/*` labels consistently to workloads, services, selectors, monitoring, and policy targets.- Set realistic resource requests and limits plus startup, readiness, and liveness probes that match the service contract.- Run as non-root, disallow privilege escalation, drop capabilities, use `RuntimeDefault` seccomp, and prefer a read-only root filesystem.- Use dedicated service accounts, namespace-scoped RBAC, Workload Identity, and least-privilege network policies.- Reference secrets through External Secrets or approved Key Vault integration; never commit a Kubernetes Secret value.- Keep namespaces, selectors, ports, service names, and Helm value keys consistent across related manifests.- Keep generated GitOps examples under `scripts/golden-paths/`; no root `argocd/` path is assumed.- Preserve rollout safety with disruption budgets, topology constraints, and graceful termination where availability requires them.## Verification- YAML, Helm, and Kustomize rendering produce valid resources with no unresolved tokens.- Policy checks cover tags, resources, non-root execution, privilege, and registry restrictions.- Rendered workloads have immutable images, probes, resources, identity, and secret references.## Do / Do Not| Do | Do not || --- | --- || Render manifests and enforce identity, resources, probes, and policy controls. | Apply unrendered files or weaken controls to make a deployment pass. || Use immutable images and external secret references. | Use floating tags or commit secret values. |## Checklist Before Opening a PR- [ ] The change matches this instruction's `applyTo` scope.- [ ] YAML, Helm, and Kustomize rendering pass without unresolved tokens.- [ ] Policy checks cover identity, privilege, network, resources, and registry rules.- [ ] Workloads use immutable images, probes, and external secret references.- [ ] No unrelated edits or unresolved placeholders remain.

Frequently asked questions

Kubernetes