health-check-validator

Validate health check endpoints and Kubernetes probe configurations.

3|2|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/robotijn/ctoc --skill health-check-validator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: health-check-validator
Source: https://github.com/robotijn/ctoc/tree/main/skills/specialized/health-check-validator
Command: npx skills add https://github.com/robotijn/ctoc --skill health-check-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Misconfigured health check endpoints and Kubernetes probes are a leading cause of cascade failures, rolling deploy outages, and latent production incidents in cloud-native applications. This Skill eliminates these critical defects by enforcing 2026 best practices for health check implementation.

Core Features & Use Cases

  • Probe Separation Validation: Ensures liveness, readiness, and startup probes are correctly partitioned to prevent cascade restarts from dependency blips.
  • Graceful Shutdown Auditing: Checks for proper preStop hooks and terminationGracePeriodSeconds configuration to avoid 5xx errors during rolling deploys.
  • Compliance Enforcement: Validates RFC 9457 compliant response bodies, unauthenticated probe access, and circuit-breaker protected dependency checks.
  • Use Case: For a Kubernetes-deployed microservice using a single /health endpoint for both liveness and readiness, use this Skill to identify the cascade-restart risk and get guidance to split into distinct /livez, /readyz, and /startupz endpoints.

Quick Start

Use the health-check-validator skill to audit the health endpoints and Kubernetes probe configuration of your deployed microservice.

Frequently Asked Questions about health-check-validator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate Kubernetes liveness and readiness probes to prevent cascade failures?

You validate Kubernetes probes by checking that liveness, readiness, and startup endpoints are correctly partitioned, preventing dependency blips from triggering cascade restarts across your microservices.

Why do my Kubernetes deployments return 5xx errors during rolling updates?

Rolling deploy 5xx errors often occur when health check endpoints lack proper preStop hooks and terminationGracePeriodSeconds configuration, failing to execute a graceful shutdown workflow for terminating containers.

Should I split my microservice health check endpoint into separate liveness and readiness probes?

Yes, splitting a single /health endpoint into distinct /livez, /readyz, and /startupz endpoints is required to prevent cascade restarts and correctly partition probe responsibilities in cloud-native applications.

What is an RFC 9457 compliant health check response body for Kubernetes probes?

An RFC 9457 compliant health check response body provides standardized problem details for HTTP APIs, ensuring unauthenticated probe access and circuit-breaker protected dependency checks return structured, machine-readable status payloads.

Can I audit graceful shutdown configuration and preStop hooks for Kubernetes microservices?

Yes, you can audit graceful shutdown configuration by validating preStop hooks and terminationGracePeriodSeconds settings in your Kubernetes deployments to eliminate rolling deploy outages and latent production incidents.