Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
aj-geddes avatar

Health Check Endpoints

  • 409 installs
  • 305 repo stars
  • Updated March 4, 2026
  • aj-geddes/useful-ai-prompts

health-check-endpoints is an agent skill that designs liveness and readiness HTTP endpoints with dependency checks, timeouts, and JSON contracts for developers who need Kubernetes probes and load balancers to route traff

About

health-check-endpoints is an agent skill from aj-geddes/useful-ai-prompts that guides design of production health probe APIs. The skill separates liveness versus readiness routes, defines JSON response schemas, sets dependency check timeouts, and documents how orchestrators should interpret status codes. Developers reach for health-check-endpoints when shipping services behind Kubernetes, load balancers, or external uptime monitors that require predictable probe contracts. Outputs include endpoint paths, check matrices for databases and queues, and failure semantics so traffic only routes to healthy instances.

  • Separate liveness vs readiness semantics
  • Dependency checks with timeouts and degraded states
  • JSON contracts for orchestrators and monitors
  • Load balancer and Kubernetes probe compatibility
  • Operational signals without leaking internals

Health Check Endpoints by the numbers

  • 409 all-time installs (skills.sh)
  • Ranked #1,063 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/aj-geddes/useful-ai-prompts --skill health-check-endpoints

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs409
repo stars305
Last updatedMarch 4, 2026
Repositoryaj-geddes/useful-ai-prompts

How do you design Kubernetes liveness and readiness probes?

Design liveness and readiness HTTP endpoints with dependency checks, timeouts, and JSON contracts so load balancers, k8s probes, and uptime monitors route traffic safely.

Who is it for?

Backend developers shipping containerized APIs who need probe endpoints that satisfy Kubernetes, load balancers, and uptime monitors.

Skip if: Teams that only need synthetic browser uptime checks without application-level dependency validation or JSON probe contracts.

When should I use this skill?

A developer asks to add /healthz or /readyz endpoints, define Kubernetes probe behavior, or document dependency health check contracts.

What you get

Liveness and readiness route specs, dependency check list with timeouts, and JSON response contract for orchestrator probes.

  • Probe endpoint specification
  • JSON health response schema

Files

SKILL.mdMarkdownGitHub ↗

Health Check Endpoints

Table of Contents

Overview

Implement health check endpoints to monitor service health, dependencies, and readiness for traffic.

When to Use

  • Kubernetes liveness and readiness probes
  • Load balancer health checks
  • Service discovery and registration
  • Monitoring and alerting systems
  • Circuit breaker decisions
  • Auto-scaling triggers
  • Deployment verification

Quick Start

Minimal working example:

import express from "express";
import { Pool } from "pg";
import Redis from "ioredis";

interface HealthStatus {
  status: "healthy" | "degraded" | "unhealthy";
  timestamp: string;
  uptime: number;
  checks: Record<string, CheckResult>;
  version?: string;
  environment?: string;
}

interface CheckResult {
  status: "pass" | "fail" | "warn";
  time: number;
  output?: string;
  error?: string;
}

class HealthCheckService {
  private startTime = Date.now();
  private version = process.env.APP_VERSION || "1.0.0";
  private environment = process.env.NODE_ENV || "development";

// ... (see reference guides for full implementation)

Reference Guides

Detailed implementations in the references/ directory:

GuideContents
Express.js Health ChecksExpress.js Health Checks
Spring Boot Actuator-Style (Java)Spring Boot Actuator-Style (Java)
Python Flask Health ChecksPython Flask Health Checks

Best Practices

✅ DO

  • Implement separate liveness and readiness probes
  • Keep liveness probes lightweight
  • Check critical dependencies in readiness
  • Return appropriate HTTP status codes
  • Include response time metrics
  • Set reasonable timeouts
  • Cache health check results briefly
  • Include version and environment info
  • Monitor health check failures

❌ DON'T

  • Make liveness probes check dependencies
  • Return 200 for failed health checks
  • Take too long to respond
  • Skip important dependency checks
  • Expose sensitive information
  • Ignore health check failures

Related skills

FAQ

What is the difference between liveness and readiness in health-check-endpoints?

health-check-endpoints treats liveness as a process-alive signal and readiness as a dependency-ready gate before traffic. The skill defines separate HTTP routes, JSON contracts, and timeout rules so Kubernetes and load balancers route only to instances that pass readiness checks.

What dependencies should readiness checks cover?

health-check-endpoints maps critical upstream dependencies such as databases, caches, and message queues into readiness checks with explicit timeouts. Each dependency gets a named status field in the JSON contract so orchestrators can distinguish partial failures.

Backend & APIsbackenddevopstesting

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.