Radar lab sweep
Skill Neetx/ai-security-research-radar/.claude/skills/radar-lab-sweep
AI Security Research Radar — AI for security and security for AI
npx -y skills add Neetx/ai-security-research-radar --skill radar-lab-sweepAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Sweep the primary security feeds — vendor/lab red-team & security blogs, research venues, and advisory feeds — on EVERY daily run (not rotated) so no attack-technique, red-team tool release, or disclosure is missed. Prefer RSS/Atom over HTML to survive JavaScript-rendered indexes. Use at the start of every daily scan, before the rotating exploration slot.
SKILL.md
2.7 KB, as published. Nobody here has run it
Primary-feed sweep — every run, no rotation
A real security radar checks its primary feeds every single day. This sweep is mandatory on every daily run and is separate from (and in addition to) the rotating exploration slot. Vendor/lab security blogs, research venues, repos and advisories are primary sources under the Hard rules, so anything found here is citable evidence (filtered for OFFENSIVE relevance — attack techniques, red-team tooling, exploitation research).
The CHECK (fetch every feed and see what is new since the last scan) is owed on EVERY run, even one minute after another pass — it is cheap triage and may never be skipped as a "light pass". Only the EXTRACT (open a new post in full) is conditional on a genuinely new entry.
Method (efficient)
- For each source in the list, fetch its FEED first (RSS/Atom), not the HTML
index — feeds are immune to the JS-rendering that hid
lmsys.org/blog. To find a feed: try/rss.xml,/feed,/atom.xml,/index.xml, or read the page's<link rel="alternate" type="application/rss+xml">. - Open only entries dated AFTER the last daily scan (check the previous date in
logs/source_rotation.md). Skip everything older — this keeps the sweep cheap. - Apply the evidence rules: open the actual post, cite its own date, match to a
trend or log to
observation_queue/study_shelfas appropriate. - Log the sweep in
logs/source_rotation.mdevery run, even when nothing is new ("lab-sweep: no new posts").
Source list
The lists live in SOURCES.md → "Primary feeds — vendor/lab security blogs &
advisories" and "Research venues — arXiv & security conferences" (agent-owned: mark
feeds DEAD if they stop resolving, add new sources as they appear). Iterate EVERY
entry; prefer the feed URL, fall back to the HTML index via tvly extract only if
no feed exists. Log each source opened or degraded: <reason>.
Notes
- The sweep complements, never replaces, the rotating exploration slot.
- Vendor/lab security blogs and cons often disclose attack techniques and red-team tool releases that never become arXiv papers — those are exactly what this sweep exists to catch. Filter for offensive relevance; skip product/marketing.
- Keep this list in sync with the
SOURCES.mdregistry.