radar-repo-watchlisted
Install: claude install-skill Neetx/ai-research-radar
# GitHub watch — repos, profiles, and fork trees
In big projects, important changes show up as PR/issue/fork activity well before
the headline release. Watching repos, the people behind them, and their fork
trees surfaces that build-up early.
## How to fetch (feeds first, no auth, no rate-limit worries)
Prefer GitHub's public Atom feeds and plain pages — the same RSS pattern as the
lab sweep, readable via `tvly` with no API key and no rate limit:
- Releases: `https://github.com/<o>/<r>/releases.atom`
- Tags: `https://github.com/<o>/<r>/tags.atom`
- Commits on default branch: `https://github.com/<o>/<r>/commits.atom`
- A user's public activity: `https://github.com/<u>.atom`
- PR list / issues / a fork's page: extract the HTML via `tvly` (no feed exists).
The REST API (`api.github.com`) is OPTIONAL — use it only if it is reachable
and authenticated in this environment (it may not be: the network often routes
through Tavily only, and unauthenticated API is 60 req/hr). When available it
gives cleaner structured data (exact `ahead_by`, merged_at); when not, the feeds
and page extraction above are sufficient. Never let the watch block on the API.
Check activity since the last scan (previous `source_rotation` date). Log the
watch every run, even when quiet ("github-watch: no movement").
## 1. Watched repositories
For each repo in SOURCES.md → "Watched repositories":
- **Releases / tags** (releases.atom / tags.atom) — a new release is a citable
artifact (evidence-eligible ag