ecosystem-health

Ecosystem Health Check

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:

# 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:
curl -sf <url> 2>/dev/null && echo "<name>: OK" || echo "<name>: unreachable"

# If the 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>: unreachable"

Generate the check commands dynamically from the config — do not hardcode any service names or URLs.

Critical Issues Across Projects

Read the cross-repos field from Session Config. If not configured or empty, print:

No cross-repos configured in Session Config. Add cross-repos to enable cross-project issue scanning.

and skip this section.

Detect VCS

VCS Reference: Detect the VCS platform per the "VCS Auto-Detection" section of the gitlab-ops skill. Use CLI commands per the "Common CLI Commands" section. For cross-project queries, see "Dynamic Project Resolution."

For each cross-repo, query critical issues

Using the detected VCS CLI (per gitlab-ops "Common CLI Commands" and "Dynamic Project Resolution" sections):

1. Resolve the project ID or owner/repo slug for each cross-repo
2. Query open issues with priority:critical or priority:high labels (limit 5 per repo)
3. Collect results across all configured repos

CI Pipeline Status

Query the latest pipeline/workflow runs for the current repo using the detected VCS CLI (per gitlab-ops "Common CLI Commands" section). Report the 3 most recent runs.

Report Format

Present as a compact health dashboard. Build the table dynamically from whichever endpoints are configured:

## Ecosystem Health
| Service       | Status            |
|---------------|-------------------|
| <name>        | [OK/unreachable]  |
| ...           | ...               |

Critical issues: [N total across cross-repos]
CI: [green/red/pending]

If no health endpoints are configured, omit the service table entirely. If no cross-repos are configured, omit the critical issues line.

Flag any service that is DOWN or any critical issue count > 0 as requiring attention.