Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →notque/service-health-check
Service health monitoring, endpoint validation, and CVE source auditing.
Passed 18 of 21 test cases with the skill, and 7 of 21 without it.
and 11 more in the full report
12 fixed8 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
An isolated cache daemon 'redis-server' is verified running with PID 1102. No health JSON file path is defined in its service manifest, and no port probe is configured. What exact status should be assigned?
| Checked | Without skill | With skill |
|---|---|---|
| Assigns status RUNNING to the service | Missed | Passed |
The instructions your model reads when the skill loads.
This skill provides deterministic service health monitoring using the Discover-Check-Report pattern. It finds services, gathers health signals from multiple sources (process table, health files, port binding), and produces actionable reports identifying degraded or failed services.
Core principle: Health assessment is evidence-based. Never report a service healthy without verifying process status independently of health file content. Never assume a running process is functional — always cross-check against health files and port binding.
| Signal | Load These Files | Why |
|---|---|---|
| Endpoint validation request | references/endpoint-validator.md | Full endpoint validation methodology |
| Security header WARNs, HSTS/CSP/X-Frame issues | references/security-headers.md | Deep security header reference |
| Config errors, hardcoded IPs, timeout problems | references/endpoint-config-preferred-patterns.md | Endpoint config patterns |
| 401/403 failures, Bearer/API-key/cookie auth | references/auth-endpoint-patterns.md | Auth endpoint patterns |
| CVE source audit request | references/cve-source-check.md | Full CVE source check methodology |
| CVE registry schema questions | references/registry-schema.md | Registry shape and entry format |
| CVE source URL verification | references/source-verification.md | HEAD-check semantics |
| CVE report format questions | references/output-formats.md | JSON schema and Markdown sections |
Goal: Identify all services to check before running any health probes.
Step 1: Locate service definitions
Search for service configuration in this order:
services.json in project rootStep 2: Build service manifest
test cases passed, vs 7 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.