contributor-spotlight

> **${var}** — Optional. Pass `dry-run` to skip the notification (article still writes, state still updates). Pass an `owner/repo` to override the auto-pick for one run. Empty = auto-pick from the most recent fork-cohort run. Today is ${today}. Convert the most recent `fork-cohort` output into one named recognition post per week. `fork-cohort` produces a cohort table; this skill turns one row of that table into a 150-word human moment that names the operator, what they shipped, and why it matters. ## Why this exists `fork-cohort` (PR #152) identifies POWER and ACTIVE forks weekly but produces a data table — not a recognition. `fork-contributor-leaderboard` ranks contributors by upstream PRs but doesn't see what's happening inside a fork. Neither closes the loop between *we have fork data* and *we do something social with it*. contributor-spotlight is the social loop: one fork operator per week gets a named callout — their handle, their fork, the skills they enabled, their star count, a one-line "keep shipping" close. That's the flywheel — operators who feel seen attract other operators. This is also formatted to feed `thread-formatter` directly, so the post is a tweetable artifact, not just a Telegram blip. ## Config No new secrets. No new env vars. Reads: - `articles/fork-cohort-*.md` — most recent (look back up to 14 days). Picks the POWER cohort roster. - `memory/topics/fork-cohort-state.json` — authoritative bucket assignments, fallback if no article exists. - `mem...