How do I install the Techtide Kubernetes Pod Spec Review skill?

Run npx skillmds@latest add techtideohio/techtide-kubernetes-pod-spec-review 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.

Is Techtide Kubernetes Pod Spec Review 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 Techtide Kubernetes Pod Spec Review?

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 Techtide Kubernetes Pod Spec Review free to use?

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

Who published Techtide Kubernetes Pod Spec Review?

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

Techtide Kubernetes Pod Spec Review by techtideohio

Name: Techtide Kubernetes Pod Spec Review
Author: TechTideOhio

Techtide Kubernetes Pod Spec Review

Use this skill when reviewing a Kubernetes Pod spec, Deployment spec, or StatefulSet spec for correctness, security posture, and production-readiness. Trigger on any request to audit, validate, or score a workload manifest.

TechTideOhio Updated Sep 17, 2026

File contents

Kubernetes Pod Spec Review

Purpose

Review Kubernetes Pod, Deployment, and StatefulSet specifications for probe correctness, resource QoS configuration, securityContext posture, image pull policy safety, secret consumption patterns, topology spread, and termination grace period alignment. Output a structured findings list with severity, evidence, and safe remediation steps - aligned with CKAD domain knowledge and production-readiness standards.

Lean operating rules

Check both livenessProbe and readinessProbe; flag missing probes as HIGH for Deployments receiving traffic. Flag aggressive livenessProbe.failureThreshold (<=2) that kills pods during GC pauses.
Review resources.requests and resources.limits; flag missing requests (unschedulable under pressure) as MEDIUM and flag CPU limits without requests as Burstable QoS risk.
Audit securityContext at both pod level (runAsNonRoot, seccompProfile) and container level (allowPrivilegeEscalation: false, readOnlyRootFilesystem: true, capabilities.drop: [ALL]).
Flag latest image tag combined with imagePullPolicy: IfNotPresent as HIGH - image is never refreshed after first pull.
Flag Secrets consumed via envFrom.secretRef (bulk-mount exposes all keys) as MEDIUM; recommend volume mounts or specific env.valueFrom.secretKeyRef.
Check topologySpreadConstraints for multi-replica Deployments; flag absence as MEDIUM (single AZ failure = full outage).
Review terminationGracePeriodSeconds against application drain time; flag default 30s for gRPC or database workloads as MEDIUM.
Label all findings as live evidence, documentation-based, or inference.

References

Load these only when needed:

Workflow and output contract

Response minimum

Severity-labeled findings list (CRITICAL / HIGH / MEDIUM / LOW)
Evidence source for each finding
Specific field path that caused the finding (e.g., spec.containers[0].livenessProbe)
Recommended remediation with example YAML snippet
Overall production-readiness verdict

---name: techtide-kubernetes-pod-spec-reviewdescription: Use this skill when reviewing a Kubernetes Pod spec, Deployment spec, or StatefulSet spec for correctness, security posture, and production-readiness. Trigger on any request to audit, validate, or score a workload manifest.---# Kubernetes Pod Spec Review## PurposeReview Kubernetes Pod, Deployment, and StatefulSet specifications for probe correctness, resource QoS configuration, securityContext posture, image pull policy safety, secret consumption patterns, topology spread, and termination grace period alignment. Output a structured findings list with severity, evidence, and safe remediation steps - aligned with CKAD domain knowledge and production-readiness standards.## Lean operating rules- Check both `livenessProbe` and `readinessProbe`; flag missing probes as HIGH for Deployments receiving traffic. Flag aggressive `livenessProbe.failureThreshold` (<=2) that kills pods during GC pauses.- Review `resources.requests` and `resources.limits`; flag missing requests (unschedulable under pressure) as MEDIUM and flag CPU limits without requests as Burstable QoS risk.- Audit `securityContext` at both pod level (`runAsNonRoot`, `seccompProfile`) and container level (`allowPrivilegeEscalation: false`, `readOnlyRootFilesystem: true`, `capabilities.drop: [ALL]`).- Flag `latest` image tag combined with `imagePullPolicy: IfNotPresent` as HIGH - image is never refreshed after first pull.- Flag Secrets consumed via `envFrom.secretRef` (bulk-mount exposes all keys) as MEDIUM; recommend volume mounts or specific `env.valueFrom.secretKeyRef`.- Check `topologySpreadConstraints` for multi-replica Deployments; flag absence as MEDIUM (single AZ failure = full outage).- Review `terminationGracePeriodSeconds` against application drain time; flag default 30s for gRPC or database workloads as MEDIUM.- Label all findings as live evidence, documentation-based, or inference.## ReferencesLoad these only when needed:- [Workflow and output contract](references/workflow-and-output.md)## Response minimum- Severity-labeled findings list (CRITICAL / HIGH / MEDIUM / LOW)- Evidence source for each finding- Specific field path that caused the finding (e.g., `spec.containers[0].livenessProbe`)- Recommended remediation with example YAML snippet- Overall production-readiness verdict

Frequently asked questions