What problem does it solve?
This Skill eliminates inconsistent or incomplete health check implementations in .NET microservices by defining exactly which endpoints to expose and how to tag dependency checks.
Core Features & Use Cases
- Required endpoint conventions: Establishes
/health for aggregated dependency-aware status, /health/live for fast process reachability, and an optional /health/ready for startup/readiness suitability.
- Health check tagging standards: Defines a predictable tagging model (
liveness, dependency, infra, external-service, internal-service) so the same service can support different operational contexts like load balancers and deployment pipelines.
- Implementation guidance for common integrations: Recommends lightweight dependency checks (SQL/Redis/Service Bus/external APIs) and points to HealthChecks ecosystem usage patterns, including Azure App Service and post-deployment slot strategies.
Quick Start
Ask the AI to produce a .NET HealthChecks setup that exposes /health, /health/live, and /health/ready with the required tag predicates for infra, external services, and internal dependencies.