Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/ecosystem-health
Monitor health across configured service endpoints, CI pipelines, and critical issues. Automatically invoked during session-start when ecosystem-health is enabled in Session Config.
Passed 13 of 19 test cases with the skill, and 8 of 19 without it.
and 3 more in the full report
6 fixed9 passed either way7 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
When a probed endpoint returns a plain response body that cannot be parsed as JSON, what range of HTTP response codes maps to an OK status?
| Checked | Without skill | With skill |
|---|---|---|
| Treats non-JSON HTTP status codes from 200 through 399 as status OK | Missed | Passed |
The instructions your model reads when the skill loads.
This skill's watcher is registered as a plugin monitor via .claude-plugin/plugin.json's experimental.monitors reference to monitors/monitors.json. Each session that loads this plugin auto-starts the watcher in the background (see scripts/lib/ecosystem-health.mjs). Each NDJSON stdout line from the watcher becomes a <task_notification> event Claude sees mid-session.
For harness < 2.1.105 (no monitor support), the skill's manual probes documented below serve as the fallback path.
This skill reads from the project's ## Session Config section in the platform instruction file:
health-endpoints — list of {name, url} objects for service health checkscross-repos — list of related repositories for critical issue scanningBoth fields are optional. The skill degrades gracefully when either is missing. On Codex this means AGENTS.md; on Claude/Cursor it means CLAUDE.md.
Read the health-endpoints field from Session Config. If not configured or empty, print:
No health endpoints configured in Session Config. Add
health-endpointsto enable service monitoring.
and skip this section.
Otherwise, for each configured endpoint, run a health check:
# Example health-endpoints config:
# health-endpoints:
# - name: API
# url: https://api.example.com/health
# - name: Worker
# url: http://worker:8080/healthz
# - name: Dashboard
# url: http://localhost:3000/api/health
# For EACH endpoint in health-endpoints, run:
# NAME=<name> URL=<url>
curl -s --max-time 6 -w '\nHTTP_STATUS:%{http_code}' "$URL" 2>/dev/null \
test cases passed, vs 8 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.