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

Health Check Endpoints

  • 325 installs
  • 202 repo stars
  • Updated August 4, 2026
  • secondsky/claude-skills

health-check-endpoints is an agent skill that implements liveness, readiness, startup, and deep health probe endpoints for developers who deploy services on Kubernetes, load balancers, or autoscaling groups.

About

health-check-endpoints is an MIT-licensed agent skill from secondsky/claude-skills that implements four probe types: liveness (process alive, restart on failure), readiness (traffic gating with 200/503), startup (delay other probes during boot), and deep (full dependency scans for alerting). It ships an Express HealthChecker class that runs SELECT 1 against a database and redis.ping(), exposes /health/live and /health/ready routes, and includes Kubernetes livenessProbe and readinessProbe YAML with initialDelaySeconds, periodSeconds, and failureThreshold values. Best practices stress keeping liveness free of external dependencies, limiting readiness to critical systems, and setting timeouts to prevent cascading failures. Additional reference implementations cover Python Flask and Java Spring Boot Actuator. Install with npx skills add secondsky/claude-skills --skill health-check-endpoints. Use when probe failures, startup delays, or missing dependency checks block zero-downtime deploys.

  • health-check-endpoints

Health Check Endpoints by the numbers

  • 325 all-time installs (skills.sh)
  • +16 installs in the week ending Aug 5, 2026 (Skillselion tracking)
  • Ranked #1,270 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/secondsky/claude-skills --skill health-check-endpoints

Add your badge

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

Listed on Skillselion
Installs325
repo stars202
Last updatedAugust 4, 2026
Repositorysecondsky/claude-skills

How do you implement Kubernetes health check endpoints?

Use health-check-endpoints for development tasks

Who is it for?

Backend developers shipping Node.js or JVM services to Kubernetes who need correct liveness versus readiness separation and dependency-aware probe endpoints.

Skip if: Static sites with no server process, batch jobs without HTTP listeners, or teams already fully standardized on a managed platform health abstraction.

When should I use this skill?

User mentions health checks, liveness probes, readiness probes, Kubernetes probe failures, startup delays, or dependency monitoring for load balancers.

What you get

/health/live and /health/ready HTTP routes, dependency check handlers, 200/503 responses, and Kubernetes liveness and readiness probe manifests.

  • Health check route handlers
  • Kubernetes probe configuration YAML

By the numbers

  • Defines 4 probe types: liveness, readiness, startup, and deep
  • Includes Kubernetes probe YAML with initialDelaySeconds 15 and periodSeconds 10 examples
  • Documents 2 dependency checks in the Express example: database and Redis

Files

SKILL.mdMarkdownGitHub ↗

Health Check Endpoints

Implement health checks for monitoring service availability and readiness.

Probe Types

ProbePurposeFailure Action
LivenessIs process alive?Restart container
ReadinessCan handle traffic?Remove from LB
StartupHas app started?Delay other probes
DeepAll deps healthy?Trigger alerts

Implementation (Express)

class HealthChecker {
  async checkDatabase() {
    const start = Date.now();
    try {
      await db.query('SELECT 1');
      return { status: 'healthy', latency: Date.now() - start };
    } catch (err) {
      return { status: 'unhealthy', error: String(err?.message || err) };
    }
  }

  async checkRedis() {
    try {
      await redis.ping();
      return { status: 'healthy' };
    } catch (err) {
      return { status: 'unhealthy', error: err.message };
    }
  }

  async getReadiness() {
    const checks = await Promise.all([
      this.checkDatabase(),
      this.checkRedis()
    ]);
    const healthy = checks.every(c => c.status === 'healthy');
    return { healthy, checks };
  }
}

// Liveness - lightweight
app.get('/health/live', (req, res) => {
  res.json({ status: 'ok', timestamp: new Date().toISOString() });
});

// Readiness - check dependencies
app.get('/health/ready', async (req, res) => {
  const health = await healthChecker.getReadiness();
  res.status(health.healthy ? 200 : 503).json(health);
});

Kubernetes Configuration

livenessProbe:
  httpGet:
    path: /health/live
    port: 3000
  initialDelaySeconds: 15
  periodSeconds: 10
  failureThreshold: 3

readinessProbe:
  httpGet:
    path: /health/ready
    port: 3000
  initialDelaySeconds: 5
  periodSeconds: 10

Best Practices

  • Keep liveness checks minimal (no external deps)
  • Check only critical systems in readiness
  • Return 200 for healthy, 503 for unhealthy
  • Set reasonable timeouts to prevent cascading failures
  • Include response time metrics

Additional Implementations

See references/implementations.md for:

  • Python Flask complete health checker
  • Java Spring Boot Actuator
  • Full Kubernetes deployment config

Never Do

  • Make liveness depend on external services
  • Return 200 when dependencies are down
  • Skip dependency checks in readiness

Related skills

How it compares

Pick health-check-endpoints over generic API design skills when you need Kubernetes-aligned probe separation and ready-to-paste Express or Spring health route patterns.

FAQ

What probe types does health-check-endpoints define?

health-check-endpoints defines four probes: liveness (is the process alive), readiness (can it serve traffic), startup (has boot finished), and deep (are all dependencies healthy for alerting). Each maps to distinct failure actions.

Should liveness checks call external databases?

No. health-check-endpoints explicitly warns that liveness probes must stay minimal and never depend on external services, because database outages would trigger unnecessary container restarts and worsen outages.

What HTTP status codes should readiness endpoints return?

health-check-endpoints requires readiness routes to return HTTP 200 when all critical dependency checks pass and HTTP 503 when any check fails, matching Kubernetes load balancer and ingress probe expectations.

Backend & APIsbackendintegrations

This week in AI coding

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

unsubscribe anytime.