service-health-check

Discover, check, and report deployed service health with structured results.

415|44|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/notque/claude-code-toolkit --skill service-health-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: service-health-check
Source: https://github.com/notque/claude-code-toolkit/tree/main/skills/service-health-check
Command: npx skills add https://github.com/notque/claude-code-toolkit --skill service-health-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual health checks and ad-hoc monitoring are error-prone and slow. This service health skill provides a deterministic Discover-Check-Report workflow that identifies services, collects signals, and outputs a structured health report.

Core Features & Use Cases

  • Discover services from common manifests and system definitions, then build a clear service manifest with process patterns, health files, and ports.
  • Check: verify processes, health data recency, and port bindings to determine accurate service status (HEALTHY, WARNING, DEGRADED, DOWN).
  • Report: generate a machine-readable health report with actionable recommendations and remediation guidance for operators.

Quick Start

Run a Discover-Check-Report health workflow on your configured services to generate a structured health report.

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 service health checks for process status and port listening?

Automate service health checks by discovering deployed services, verifying process patterns, and testing port bindings to generate a structured health report. This workflow determines accurate service status across diverse environments using deterministic, read-only behavior.

What is a deterministic health file staleness check for service monitoring?

A deterministic health file staleness check verifies the recency of health data files to determine service status. It identifies whether deployed services are HEALTHY, WARNING, DEGRADED, or DOWN by collecting read-only signals and outputting actionable recommendations.

How do I generate a machine-readable health report with remediation guidance?

Generate a machine-readable health report by running a Discover-Check-Report workflow that assesses process status, health file recency, and port bindings. The resulting report includes actionable recommendations and remediation guidance for operators.

Can I discover services from common manifests without writing custom monitors?

Discover services from common manifests and system definitions to build a clear service manifest with process patterns, health files, and ports. This replaces manual monitoring by automatically identifying configured services for subsequent health checks.

Does service health monitoring require write access to the deployed environment?

Service health monitoring requires deterministic, read-only behavior and does not need write access to the deployed environment. It safely collects signals from processes, health files, and ports to assess uptime and status without modifying system state.

Why are manual health checks error-prone compared to a structured workflow?

Manual health checks are error-prone because they rely on ad-hoc monitoring, whereas a structured Discover-Check-Report workflow provides deterministic service identification, signal collection, and machine-readable reporting to eliminate human error and speed up assessments.