radar-source-heallisted
Install: claude install-skill Neetx/ai-research-radar
# Source self-healing
Logging "degraded" run after run is a failure of the radar, not of the source.
If you logged the same breakage last run (check the recent `source_rotation`
tail and SOURCES.md notes), **fix it this run** — don't just re-log it.
## When to heal (don't thrash)
- One transient failure → log it, retry next run. Do not heal on a single blip.
- The SAME failure twice (across runs), OR obviously degraded data now (empty
feed, 404, JSON/parse error, a feed whose newest item is months old) → heal.
## Diagnose the failure class, then repair
**Class A — broken / moved / stale feed or page**
- Open the source's HTML index. Find the real feed from the page's
`<link rel="alternate" type="application/rss+xml|atom+xml">`, or try common
paths: `/rss`, `/feed`, `/rss.xml`, `/atom.xml`, `/index.xml`, `/blog/feed.xml`.
- Moved blog (org rebranded/changed domain) → search for the current URL and
confirm it resolves with recent posts.
- Stale feed (newest post months old while the org is clearly still active) →
the org now posts elsewhere; find the live channel (a different domain, their
HF org activity, a docs/changelog page) and switch to it.
- No feed exists at all → set the method to "HTML index via Tavily extract" and
note it, so the sweep stops hunting for a feed.
**Class B — failing tool call on an otherwise-live source**
- Vary the call shape: different `tvly` flags, `extract` vs `search`,
`--extract-depth advanced`, smaller/larger scope.
- Prefe