Map GitHub forks and third-party repos for watched repositories weekly.
npx skills add https://github.com/aaronjmars/aeon --skill builder-map
Please help me install this Agent Skill. Skill: builder-map Source: https://github.com/aaronjmars/aeon/tree/main/skills/builder-map Command: npx skills add https://github.com/aaronjmars/aeon --skill builder-map
It answers the “who’s building on top of this stack?” question by continuously mapping forks and third-party usage across time.
Configure watched repositories in memory/topics/watched-repos.md, then run the builder-map schedule to produce a weekly ecosystem report and update memory/topics/ecosystem.md.
High-intent search queries and answers about installing and using this skill.
To track GitHub forks and find new builders, you can configure watched repositories to run weekly scans that classify forks as active, stale, or dormant and discover third-party repos using your stack. The scan results are written to a structured ecosystem memory file.
Developer adoption tracking monitors who is building on top of your technology stack over time. Ecosystem monitoring works by running weekly GitHub searches and web scans to identify third-party usage, classify fork activity, and score new builders based on public announcements.
You monitor developer adoption momentum by running scheduled weekly ecosystem scans that identify new builders, analyze fork activity, and mine web announcements. The scan emits a pending notification only when the tracked adoption momentum warrants attention.
Yes, you can use GitHub search to discover third-party repos mentioning your stack. The ecosystem scan finds non-fork repositories via GitHub CLI API search and categorizes these signals across verticals to update your ecosystem intelligence.
To configure watched repositories for weekly builder ecosystem mapping, you add them to a memory topics file. Running the mapping schedule then produces a weekly ecosystem report by analyzing forks and third-party usage for the configured repositories.
Builder ecosystem mapping requires no external dependencies to function, but it utilizes GitHub CLI API search and web search capabilities. The mapping runs weekly to categorize signals across verticals and write structured updates to memory.
Atrium-HermesIdentify and summarize active builders and ecosystem signals around watched repositories.
Atrium-HermesAggregate MCP ecosystem data from GitHub and npm into a weekly momentum score and briefing.
aeoncity-demoMonitor watched repositories for forks and builder announcements via GitHub API.
swarm-ai-researchIdentify and summarize active builders and ecosystem signals around watched repositories.
