radar-source-heal — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited radar-source-heal (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
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 tail of logs/source_rotation.md and SOURCES.md notes), fix it this run — don't just re-log it.
Coverage-honesty means every sweep logs each source as opened or degraded: <reason> in logs/source_rotation.md. So the heal worklist is a precise, queryable set — you do not guess what to fix:
grep 'degraded:' logs/source_rotation.md | tail → the candidates. A sourcemarked degraded in 2+ recent runs (or obviously degraded NOW — empty feed, 404, JSON/parse error, a feed whose newest item is months old) is OWED a heal this run. One transient blip → log it, retry next run; don't heal on a single failure.
log entirely (neither opened nor degraded — a coverage lie) is also a heal target: it is usually being skipped because it has no recorded access method and falls out of the list-iteration (this is the alphamatch failure class). Find a working method and record it.
The fix is written back into SOURCES.md (below), so the NEXT list-iteration consumes it automatically — that is what closes the loop: iterate → degraded / missing → heal → SOURCES.md method → next iteration succeeds.
Class A — broken / moved / stale feed or page
<link rel="alternate" type="application/rss+xml|atom+xml">, or try common paths: /rss, /feed, /rss.xml, /atom.xml, /index.xml, /blog/feed.xml.
confirm it resolves with recent posts.
the org now posts elsewhere; find the live channel (a different domain, their HF org activity, a docs/changelog page) and switch to it.
note it, so the sweep stops hunting for a feed.
Class B — failing tool call on an otherwise-live source
tvly flags, extract vs search,--extract-depth advanced, smaller/larger scope.
a JSON/search API — e.g. a public search endpoint — that returns clean data without scraping).
Write the WORKING access method back into SOURCES.md next to that source, dated, REPLACING the "degraded/404/stale" note — e.g. "feed at <url> (confirmed working YYYY-MM-DD)" or "use <endpoint>, not the feed (YYYY-MM-DD)". The registry is agent-owned; the repaired method is what makes the fix permanent. If a source is genuinely dead with no replacement, mark it RETIRED <date> — <reason> and drop it from the active list.
Some sources are blocked not by a broken path but by the environment — a datacenter-IP block by the site, or egress restricted to a few hosts. You cannot "repair" these, but you must NOT re-log "blocked from this IP" every run either.
like hn.algolia.com). If it works, the block is site-specific → switch that source to its API host (e.g. HN → hn.algolia.com/api/v1/...; HF → the huggingface.co/api/... endpoints; Reddit → the .json/RSS endpoints or a mirror). If even the neutral API host fails, the environment's egress is restricted.
a KNOWN CONSTRAINT with that method; then stop re-logging it run after run.
free Reddit OAuth app → REDDIT_CLIENT_ID/SECRET) or a change to the environment's allowed domains — those are the curator's call.
If the only working path needs a secret or paid API (e.g. a paid X API), do NOT hardcode it — keep the source best-effort, log it, and PROPOSE the paid option via the weekly amendment process for the curator to decide.
Heal at most ~1–2 sources per run; if several are broken, repair the highest-value first and leave the rest marked degraded: in the log (they stay on the worklist for following runs). Healing must never crowd out the actual scan.
A source that stays degraded or MISSING for weeks despite heal attempts is no longer a per-run heal job — it is a calibration signal. The weekly radar-self-eval coverage metric counts it, and per the coverage-honesty rule the answer is heal-or-REMOVE: a source the radar cannot actually sweep does not belong in a "swept every run" list. Propose the removal (or the secret/escalation it would need) via the weekly amendment process — don't leave it listed-but-unswept.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.