ecosystem-pulse

> **${var}** — Optional. `dry-run` skips notify (state still updates and article still writes). Empty = normal run. Today is ${today}. `ECOSYSTEM.md` lists the projects, agents, and products building on top of Aeon (merged in #220). Today there is no skill that asks the obvious follow-up question: **are those projects actually shipping?** `fork-cohort` buckets Aeon *forks* by activation stage; `contributor-spotlight` recognises who pushes code to Aeon *itself*; `competitor-launch-radar` watches *new* entrants on Product Hunt / HN. None of them watch the projects already in `ECOSYSTEM.md`. This skill closes that gap: a weekly Monday scan that reads `ECOSYSTEM.md`, matches each project to a GitHub repo where it can, and reports stars / forks / last-commit recency plus any new releases in the 7-day window. Read `memory/MEMORY.md` for context. Read the last 8 days of `memory/logs/` for prior-run context. Read `soul/SOUL.md` + `soul/STYLE.md` if populated to match voice in the notification and article. ## Why this exists `ECOSYSTEM.md` is a curated list of products and agents built with Aeon — 40 projects at merge time (#220). A static list answers "who claims to build on Aeon?" but not "which of them are alive this week?" Operators (and the wider community reading the ecosystem page) have no signal on whether a listed project shipped a release, went quiet, or just woke back up. Without a recurring pulse, a project can go cold for months and the list still presents it as a pee...