radar-pulse — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited radar-pulse (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.
Social tells you what people think and what is gaining traction before it reaches papers/docs, and it is often the FASTEST place to spot that something official exists (a post links a repo, a release, a paper). Social is not a primary source — but it is a discovery accelerator. This skill captures both without corroding the ledger's evidence standard.
The platform/channel/profile list lives in SOURCES.md; treat it as a seed and curate it by your own judgment — add platforms and accounts that prove useful, drop noise. Don't restrict yourself to a fixed roster.
observation_queue items, marked unverified — promotable to atrend ONLY after the claim is confirmed on a primary artifact (paper, repo, release, official doc), via the radar-source-verify skill;
summarise the signal ("a widely-upvoted r/LocalLLaMA thread reports X"). No handles in evidence/queue text beyond the bare URL.
Per run, ITERATE EVERY entry in the source lists at SOURCES.md (see "## Source lists" below) — the list is the CONTRACT: execute all of it, do not "sample" a representative subset (sampling is exactly how feed-less entries get silently dropped while the easy RSS ones get done). "Light" means SHALLOW per source (read the new items' titles), NEVER skipping a source: the CHECK (fetch each entry and see what is new since the last pass) is owed EVERY run, even one minute after another pass; only the EXTRACT (follow a new item to its primary and verify) is conditional on something new. A skipped source is not "light", it is a missed lane. For each source, by category:
subs AND the broad-pulse subs. Note two things, not one: (a) recurring on-axis topics, and (b) whatever is dominating a community right now, on-axis or not.
don't-miss), in addition to term searches.
tvly extract of its index/page (exactly as the lab sweep does for feed-less NVIDIA/Meta). A feed-less entry is NEVER a reason to skip — if it has no recorded method, that is a radar-source-heal job, not a drop. Log each entry as opened OR degraded: <reason>; a listed entry absent from the coverage log is a coverage lie. For every new video/post, FOLLOW the link to the named primary and verify it (radar-source-verify); cite the primary, never the curator. This is how high-signal work surfaced by a curator gets caught before it ranks on arXiv/HF.These are unreliable in 2026 (no free API); if a profile can't be fetched, log "X/IG degraded: <handle> unreachable" in logs/source_rotation.md and move on — do not fabricate.
Like radar-lab-sweep, this skill does NOT name individual channels/blogs in its prose; the data lives in SOURCES.md and you execute ALL of it. The lists to iterate every run:
SOURCES.md → "Social & community channels" (Reddit subs, Hacker News, X/IG).SOURCES.md → "YouTube — TRUSTED-CURATOR POINTER LANE" (one feed per channel).SOURCES.md → "Curated digests + explainer/aggregator blogs" (the pointer/digestblogs — fetch each by its recorded method: feed, or tvly extract of its index for feed-less ones). For each list: iterate EVERY entry, fetch by its recorded access method, log each as opened or degraded: <reason>. A new source you find goes INTO the relevant SOURCES.md list (so it is iterated next run), never just into the skill prose.
When a social signal LINKS TO or NAMES a primary artifact (repo, release, paper, official blog post), do not just queue the rumour — FOLLOW the link in the same run and verify the artifact via radar-source-verify. If the artifact clears the evidence rules, it becomes evidence THIS run, cited to the primary source (never to the social post). Social is how you find it days early; the primary artifact is what you cite. Only when there is no reachable artifact yet does the signal stay a queue item.
A NAMED primary has exactly TWO valid end-states, never a third: (a) verified → evidence, or (b) an observation_queue item carrying the named id/URL. "Intake — no action", "noted", "hit-attributed to <curator>" are NOT end-states: attribution records WHERE you saw it, capture records WHAT it is, and only the queue/ledger is capture — report prose and SOURCES notes are not. "We already know this is a miss" is the trap, not an excuse: if a named primary is recognized but is not in the queue or the ledger, it has been LOST, so queue it now. (The failure this prevents: a primary named repeatedly in report/SOURCES prose and attributed to a curator, yet never followed to its artifact, verified, or queued — so the radar never even holds its id.)
For signals without an artifact: if it points to something concrete but not yet findable, log a queue item ("verify <thing>"); if it is pure sentiment, hold it for the pulse note. Cap at ~5 pulse items per run — but a field-shaking event (below) always makes the cut, even off-axis.
The pulse's job is NOT only to extract on-axis signal — it is also to notice when the ground moves. The classic failure: the top post of your #1 community is a field-shaking story, but you discard it because it doesn't map to a tracked axis. Do not do that.
earthquake check is multi-channel every run: HN front page (Algolia) + the broad Reddit subs + the trusted curators + the digests; X best-effort. HN is the reliable backbone, but an HN-only pulse is incomplete — and the report must NAME which channels were actually checked (a single-channel pulse is a visible gap to fix, not "done"). Cross-posting is your friend: a real field-shaking event shows up across several of these within hours, so checking the reliable set catches it even when X/Reddit-direct are flaky.
of a major community — or several communities at once (technical AND broad) — that IS the signal, on-axis or not. Surface it.
OpenAI, Google, Meta, Anthropic, Mistral, xAI, regulators, the open-weight labs — whoever the earthquake involves. Do not over-index on a single vendor; the test is "is the field consumed by it", not "which logo is on it".
trend (a model ban, an abrupt global access cut, a vendor/government action, an acquisition, a major outage) does NOT go in the trend ledger and is NOT evidence — but it MUST appear in the community-pulse note ("the community is consumed by X"). The radar must say the ground moved, even when it has no trend for it. Follow to a primary source if one exists; otherwise log it as the dominant unverified pulse item with the thread link.
it belonged in the pulse. Operational earthquakes (a model you depend on vanishing) count, even though they are not papers or releases.
SOURCES.md as you findones that recur with signal; drop channels that produce only noise (one-line reason in the report).
trying until conditions change.
env secrets (e.g. a paid X API) — the curator decides those, not the agent.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.