dotnet-healthchecks

Name: dotnet-healthchecks
Availability: InStock
Author: mcj-coder

Standardize ASP.NET Core health checks with AspNetCore.Diagnostics.HealthChecks for Kubernetes probes.

1|1|Updated Jan 3, 2026

Search Tags:#monitoring #api #kubernetes #health checks #dotnet #asp.net core

Ready to run

npx skills add https://github.com/mcj-coder/development-skills --skill dotnet-healthchecks

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dotnet-healthchecks
Source: https://github.com/mcj-coder/development-skills/tree/main/skills/dotnet-healthchecks
Command: npx skills add https://github.com/mcj-coder/development-skills --skill dotnet-healthchecks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill standardizes the implementation of health checks in ASP.NET Core applications, ensuring reliable monitoring of application health and its dependencies.

Core Features & Use Cases

Standardized Implementation: Leverages the AspNetCore.Diagnostics.HealthChecks ecosystem for consistent health endpoint definition.
Dependency Health: Checks the health of databases, caches, message brokers, and external services.
Kubernetes Probes: Facilitates the configuration of liveness and readiness probes for containerized applications.
Use Case: When building a new ASP.NET Core microservice, use this Skill to quickly implement /health/live and /health/ready endpoints that accurately reflect the application's operational status and its critical dependencies.

Quick Start

Use the dotnet-healthchecks skill to add a health check for a PostgreSQL database to your ASP.NET Core application.

Frequently Asked Questions about dotnet-healthchecks

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

FAQPage Schema

How do I implement health checks for an ASP.NET Core microservice?▼

Implement ASP.NET Core health checks by standardizing liveness and readiness endpoint definitions using the AspNetCore.Diagnostics.HealthChecks ecosystem. This covers dependency health for databases, caches, and message brokers, integrating directly with Kubernetes probes for containerized applications.

What is the difference between liveness and readiness probes in Kubernetes health checks?▼

Kubernetes health checks distinguish liveness probes, which verify the application is running, from readiness probes, which confirm the application can handle traffic by checking dependencies like databases and caches. This Skill standardizes both configurations for ASP.NET Core services.

Can I monitor external service dependencies using ASP.NET Core health checks?▼

Yes, ASP.NET Core health checks can monitor external service dependencies. This Skill standardizes dependency health checks for databases, caches, message brokers, and external services to accurately reflect the operational status of your application.

What's the best way to configure Kubernetes probes for dotnet microservices?▼

The best way to configure Kubernetes probes for dotnet microservices is using standardized health check endpoints. This Skill leverages the AspNetCore.Diagnostics.HealthChecks ecosystem to facilitate reliable liveness and readiness probe configuration for containerized applications.

Do I need to test health check endpoints in ASP.NET Core?▼

Yes, testing health check endpoints is required. This Skill mandates adherence to best practices for configuration hygiene and testing to ensure reliable monitoring of your application's operational status and critical dependencies.

Why standardize health check implementation across ASP.NET Core services?▼

Standardizing health check implementation ensures reliable monitoring of application health and dependencies. This Skill provides consistent health endpoint definition using the AspNetCore.Diagnostics.HealthChecks ecosystem, covering liveness, readiness, and dependency checks for databases and external services.