builder-map

Today is ${today}. Read `memory/MEMORY.md` before starting. If `soul/SOUL.md` + `soul/STYLE.md` exist and are populated, read them to match the operator's voice; otherwise use a clear, direct, neutral tone. ## Why this skill exists When a repo, framework, or stack attracts builders — forks, third-party apps, integrations, research uses — that signal compounds quietly across GitHub and social. Without a regular sweep, the picture stays fragmented. This skill is a weekly cross-project builder discovery run: who's building on top of the watched repos, which categories are emerging, where the ecosystem is thickening. ## Config This skill reads watched repos from `memory/topics/watched-repos.md`. Each row should declare a primary repo and optional search keywords. Example format: ```markdown # Watched Repos | Repo | Keywords | Notes | |------|----------|-------| | acme/coreframework | coreframework, acmesdk | flagship stack | | acme/dataengine | dataengine, acmedata | trading / quant ecosystem | ``` If `memory/topics/watched-repos.md` doesn't exist, fall back to `memory/watched-repos.md` (legacy single-line OWNER format). If neither exists, log `BUILDER_MAP_SKIP: no watched repos configured` and stop — there's nothing to map. ## Steps ### 1. Load ecosystem baseline Read `memory/topics/ecosystem.md`. If it doesn't exist, create it with this seed and continue: ```markdown # Builder Ecosystem *Last run: never* ## Known Builders - (populate as discoveries land) ## Fork C...