080-ecosystem-health

Ecosystem Health Check

Monitor health across configured service endpoints, CI pipelines, and critical issues. Automatically invoked during session-start when ecosystem-health is enabled in Session Config.

Session Config Fields

This skill reads from the project's ## Session Config section:

• 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.

---

1. Service Health

Read health-endpoints from Session Config. If not configured or empty:

"No health endpoints configured in Session Config. Add health-endpoints to enable service monitoring."

Skip this section and proceed to CI Pipeline Status.

Health Check Procedure

For each configured endpoint:

# Example config:
#   health-endpoints:
#     - name: API
#       url: https://api.example.com/health
#     - name: Worker
#       url: http://worker:8080/healthz

# Basic check
curl -sf <url> 2>/dev/null && echo "<name>: UP" || echo "<name>: DOWN"

# If endpoint returns JSON with a "status" field, extract it:
curl -sf <url> 2>/dev/null | python3 -c "
import json,sys
d=json.load(sys.stdin)
print(f'<name>: {d.get(\"status\",\"OK\")}')
" 2>/dev/null || echo "<name>: DOWN"

Generate check commands dynamically from config. Never hardcode service names or URLs.

Status Classification

Status	Meaning
UP	Endpoint responded successfully
DOWN	Endpoint unreachable or returned error
DEGRADED	Endpoint responded but reported unhealthy status in JSON body

---

2. CI Pipeline Status

Query the latest pipeline/workflow runs for the current repo. Report the 3 most recent runs.

VCS Detection

Detect the VCS platform per the VCS Auto-Detection section of the gitlab-ops rule. Then use the appropriate CLI:

# GitLab
glab pipeline list -R <OWNER>/<REPO> --per-page 3

# GitHub
gh run list -R <OWNER>/<REPO> --limit 3