Health check endpoints for liveness, readiness, dependency monitoring. Use for Kubernetes, load balancers, auto-scaling, or encountering probe failures, startup delays, dependency checks, timeout configuration errors.
95
93%
Does it follow best practices?
Impact
95%
1.33xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Liveness vs readiness separation
Liveness path
0%
100%
Readiness path
0%
100%
Liveness is lightweight
100%
100%
Liveness has timestamp
0%
100%
Readiness checks db
100%
100%
Readiness checks Redis
100%
100%
503 on unhealthy
100%
100%
200 on healthy
100%
100%
Error in response
100%
100%
Latency metrics
0%
50%
Kubernetes probe configuration
Liveness path correct
100%
100%
Readiness path correct
100%
100%
Startup probe present
100%
100%
Startup probe path
100%
100%
Startup failureThreshold >= 25
100%
100%
Liveness initialDelay >= 15
0%
0%
Readiness initialDelay 5
0%
100%
Liveness failureThreshold 3
100%
100%
Readiness failureThreshold 3
100%
100%
Liveness timeout set
100%
100%
Readiness timeout set
100%
100%
Resource limits present
100%
100%
Deep health with system metrics
Liveness path
100%
100%
Readiness path
100%
100%
Deep health path
0%
100%
Liveness no deps
100%
100%
Readiness returns 503
100%
100%
Liveness has timestamp
100%
100%
Latency in checks
50%
100%
Error message captured
100%
100%
CPU metric in deep
100%
100%
Memory metric in deep
100%
100%
Disk metric in deep
0%
100%
503 for deep unhealthy
0%
100%
90d6bd7
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.