ecosystem-health

Monitors service health, CI pipelines, and critical issues across repositories.

50|7|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/Kanevry/session-orchestrator --skill ecosystem-health-kanevry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ecosystem-health
Source: https://github.com/Kanevry/session-orchestrator/tree/main/skills/ecosystem-health
Command: npx skills add https://github.com/Kanevry/session-orchestrator --skill ecosystem-health-kanevry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many engineering sessions begin without a clear, up-to-date view of service availability, CI pipeline health, and critical issues across related repositories; this Skill centralizes those checks so teams can identify attention items immediately at session start.

Core Features & Use Cases

  • Service Health Checks: Dynamically executes health probes against configured endpoints and reports status, including extracting JSON "status" fields when available.
  • Cross-Repo Critical Issue Scanning: Resolves related repositories via VCS auto-detection and queries open issues labeled priority:critical or priority:high, aggregating top results.
  • CI Pipeline Reporting: Queries the detected VCS CLI for the most recent pipeline or workflow runs for the current repo and surfaces the last three outcomes.
  • Use Case: Run before planning or release sessions to produce a single-pane summary of service reachability, outstanding critical issues across related repos, and recent CI results.

Quick Start

Run the ecosystem-health skill to produce a compact dashboard of service statuses, CI pipeline results, and cross-repo critical issues.

Frequently Asked Questions about ecosystem-health

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor CI pipeline health and service endpoints across multiple repositories?

You can monitor cross-repo health by running a session-driven check that probes configured service endpoints, queries recent CI pipeline outcomes via VCS CLI, and formats a compact dashboard with attention flags for critical issues.

What is the best way to get a cross-repo status snapshot before a release session?

A cross-repo status snapshot aggregates service reachability, outstanding priority:critical or priority:high issues across related repositories, and the last three CI pipeline results into a single-pane summary for immediate review.

How does cross-repo critical issue scanning detect high-priority bugs?

Cross-repo critical issue scanning resolves related repositories via VCS auto-detection and queries open issues labeled priority:critical or priority:high, aggregating the top results for the current session.

Can I use this dashboard tool for multi-repo engineering projects without external dependencies?

Yes, the dashboard operates without external dependencies, relying on Session Config to read health-endpoints and cross-repos, and using the VCS CLI to resolve projects and query pipelines and issues.

What does a service health check probe report when monitoring endpoints?

Service health checks dynamically execute probes against configured endpoints and report status, including extracting JSON "status" fields when available, to indicate service reachability.

When should I run a cross-repo health dashboard during my engineering workflow?

Run the cross-repo health dashboard at session-start or before planning and release sessions to identify attention items immediately and ensure service availability across your engineering ecosystem.