ecosystem-health

# Ecosystem Health Check ## Platform-native (CC 2.1.105+) 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. ## Session Config Fields Used 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 checks - **`cross-repos`** — list of related repositories for critical issue scanning Both fields are optional. The skill degrades gracefully when either is missing. On Codex this means `AGENTS.md`; on Claude/Cursor it means `CLAUDE.md`. ## Service Health Read the `health-endpoints` field from Session Config. If not configured or empty, print: > No health endpoints configured in Session Config. Add `health-endpoints` to enable service monitoring. and skip this section. Otherwise, for each configured endpoint, run a health check: ```bash # Example health-endpoints config: # health-endpoints: # - name: API # url: https://api.example.com/health # - name: Worker # url: http://worker:8080/healthz # - na...