ecosystem-pulse

Generate weekly GitHub liveness and release recency reports from ECOSYSTEM.md.

626|225|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/aaronjmars/aeon --skill ecosystem-pulse-aaronjmars
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ecosystem-pulse
Source: https://github.com/aaronjmars/aeon/tree/main/skills/ecosystem-pulse
Command: npx skills add https://github.com/aaronjmars/aeon --skill ecosystem-pulse-aaronjmars

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ecosystem Pulse measures whether the projects listed as building on Aeon are actually active and shipping, turning a static ECOSYSTEM.md directory into a weekly liveness and releases heartbeat.

Core Features & Use Cases

  • Weekly GitHub liveness checks: Reads ECOSYSTEM.md and resolves each entry to a GitHub repository to measure stars, forks, and last push recency.
  • Release recency surfacing: Fetches recent releases and highlights anything published within the last 7 days.
  • Actionable movement reporting: Computes bucket transitions (COLD → ACTIVE, ACTIVE → COLD) and generates a snapshot article, with notifications only when meaningful signal exists.
  • Operator-controlled repo mapping: Uses a curated mapping file for trusted matches and safely degrades via strict best-effort search for unmapped items.

Quick Start

Run the ecosystem-pulse skill in normal execute mode to generate this week’s ecosystem shipping digest and notification if signal warrants.

Frequently Asked Questions about ecosystem-pulse

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

FAQPage Schema
How do I monitor GitHub repository liveness for a markdown project list?▼

Monitor GitHub liveness by reading a markdown project list, resolving entries to repositories, and fetching stars, forks, and pushed_at timestamps to generate a weekly heartbeat report.

Can I track recent GitHub releases for projects listed in a markdown directory?▼

Track recent GitHub releases by fetching repository release data and surfacing any projects that published within the last 7 days, creating an actionable weekly shipping digest.

How do I generate a weekly ecosystem report showing active and quiet projects?▼

Generate a weekly ecosystem report by computing bucket transitions like COLD to ACTIVE, writing a refreshed snapshot article, and gating notifications to only alert on meaningful changes.

Does the GitHub CLI need to be installed to check repository liveness?▼

The GitHub CLI is required to make authenticated API calls for resolving repositories, collecting metrics, and enforcing strict repo-match guards during the liveness check process.

What is the best way to track week-over-week state changes for GitHub repositories?▼

Track week-over-week changes by reading and updating local JSON state files, allowing you to compute bucket transitions and identify newly active or quiet projects in your ecosystem.

How does strict repo-match search work when resolving unmapped projects?▼

Strict repo-match search safely degrades for unmapped items by using best-effort search alongside a curated mapping file for trusted matches, ensuring accurate repository resolution.