ecosystem-pulse

Map ECOSYSTEM.md projects to GitHub repos and collect stars, forks, pushes, and releases.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill ecosystem-pulse-atrium-hermes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ecosystem-pulse
Source: https://github.com/Atrium-Hermes/atrium-lighthouse/tree/main/skills/ecosystem-pulse
Command: npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill ecosystem-pulse-atrium-hermes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a weekly heartbeat for the projects listed in ECOSYSTEM.md by validating public GitHub repos, aggregating stars, forks, last-pushed dates, and recent releases to surface actionable signals for operators.

Core Features & Use Cases

  • Repo resolution: maps ECOSYSTEM.md entries to GitHub repos via an operator-maintained map or a best-effort search, then flags unresolved entries.
  • Metrics aggregation: collects stars, forks, last push date, and new releases to produce a digest.
  • Automation & reporting: generates an article and updates a per-project state snapshot to enable delta tracking and notifications.

Quick Start

Run the weekly pulse to verify ecosystem health and generate the latest digest article and state snapshot.

Frequently Asked Questions about ecosystem-pulse

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

FAQPage Schema
How do I generate a weekly GitHub ecosystem health digest from a markdown file?

To generate a weekly GitHub ecosystem health digest, you run a pulse check that parses a local ECOSYSTEM.md file, maps project entries to GitHub repositories, and aggregates stars, forks, and last push dates into a digest article.

What is the best way to track GitHub repo metrics like stars and releases for multiple projects?

Tracking GitHub repo metrics for multiple projects is done by maintaining a per-project state snapshot that records delta changes in stars, forks, last pushes, and new releases each week. This enables automated delta reporting and trend analysis.

Can I map project names from a markdown list to GitHub repositories automatically?

Yes, you can map project names to GitHub repositories automatically using a best-effort search algorithm or an operator-maintained mapping file. Any unresolved entries are flagged for manual curation.

Do I need the gh CLI to collect GitHub metrics for an ecosystem report?

You need the gh CLI to make optional GitHub API calls that surface live signals for your ecosystem report. The core metrics aggregation and markdown parsing operate locally without it.

What happens to unresolved GitHub repositories during an ecosystem health check?

Unresolved GitHub repositories are flagged during the ecosystem health check so operators can manually curate the project list. This ensures the automated metrics aggregation only tracks valid public repositories.