health-checks-ai-kit

Define health check endpoint standards and tagging rules for .NET microservices.

Updated May 11, 2026
One-click install
npx skills add https://github.com/ducthang-hub/nw-ai-kit --skill health-checks-ai-kit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: health-checks-ai-kit
Source: https://github.com/ducthang-hub/nw-ai-kit/tree/main/.agents/skills/health-checks-ai-kit
Command: npx skills add https://github.com/ducthang-hub/nw-ai-kit --skill health-checks-ai-kit

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about health-checks-ai-kit

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

FAQPage Schema
How do I structure ASP.NET Core health check endpoints for load balancer and deployment pipeline routing?

ASP.NET Core health check endpoints should separate liveness and readiness by exposing `/health/live` for fast process reachability and `/health` for aggregated dependency-aware status, using HealthCheckOptions with predicate-based tag filtering.

What health check tags should I use for .NET microservices monitoring?

Microservices monitoring requires predictable health check tagging using categories like `liveness`, `dependency`, `infra`, `external-service`, and `internal-service` so the same service can support different operational contexts via HealthCheckOptions predicate filtering.

How do I verify readiness in an Azure App Service deployment slot for a .NET microservice?

Azure App Service readiness verification uses the `/health/ready` endpoint to check startup suitability and post-deployment slot strategies, ensuring dependency connectivity checks for SQL Server, Redis, and Azure Service Bus pass before routing traffic.

Can I use AspNetCore HealthChecks to monitor SQL Server, Redis, and Azure Service Bus dependencies?

AspNetCore HealthChecks can monitor SQL Server, Redis, and Azure Service Bus dependencies by registering lightweight checks tagged as `dependency`, allowing the `/health` endpoint to aggregate their status for operational monitoring.

Why does my .NET liveness probe fail during deployment when dependencies are unavailable?

Liveness probes fail when they include dependency checks instead of fast process reachability logic. The `/health/live` endpoint must exclude `dependency` tags using HealthCheckOptions predicates to return healthy status regardless of external service connectivity.