service-health-check

Probe service health endpoints and dependency reachability for readiness reports.

39|6|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/vladkesler/initrunner --skill service-health-check-vladkesler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: service-health-check
Source: https://github.com/vladkesler/initrunner/tree/main/examples/roles/integration-tester/skills/service-health-check
Command: npx skills add https://github.com/vladkesler/initrunner --skill service-health-check-vladkesler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Health teams need reliable visibility into service readiness by verifying endpoints and dependency connectivity across environments.

Core Features & Use Cases

  • Probes common health paths like /health, /healthz, and /readiness.
  • Validates dependency reachability for databases, caches, queues, and external APIs.
  • Provides consolidated readiness reports for CI, pre-deploy, and runtime monitoring.

Quick Start

Run the health-check skill against your service endpoints to verify readiness across dependencies.

Frequently Asked Questions about service-health-check

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

FAQPage Schema
How do I automate health checks for microservices in a CI pipeline?

Automated health checks for microservices in a CI pipeline probe common readiness paths like /health and /healthz to verify service readiness. This generates a consolidated readiness report validating dependency reachability across your environments.

What is service readiness monitoring and how does it work?

Service readiness monitoring diagnoses overall service health by probing common health paths and validating dependency reachability for databases, caches, and external APIs. It generates a consolidated readiness report to verify service readiness during runtime monitoring.

Can I verify database and cache reachability during pre-release smoke tests?

Yes, you can verify database and cache reachability during pre-release smoke tests by probing common health paths. This validates dependency reachability for databases, caches, queues, and external APIs, producing a consolidated readiness report for your deployed applications.

What's the best way to validate external API dependencies for deployed applications?

The best way to validate external API dependencies for deployed applications is by probing common health paths like /readiness. This verifies dependency reachability for external APIs and generates a consolidated readiness report for runtime monitoring and CI pipelines.

Does a health check skill support common health paths like /healthz and /readiness?

Yes, a health check skill supports common health paths like /healthz and /readiness to diagnose service health. It probes these endpoints to validate dependency reachability and generates a consolidated readiness report for CI pipelines and runtime monitoring.