← ClaudeAtlas

radar-render-dashboardlisted

Regenerate README.md, the repo's landing page and only output surface: badges, a 3-4 bullet "since last scan" digest with inline links, a clickable trend table, the study shelf, and an output map. Use after every change to TRENDS.md, in the same commit. README.md is fully derived and never edited by hand: if it disagrees with TRENDS.md, TRENDS.md wins — regenerate.
Neetx/ai-security-research-radar · ★ 4 · AI & Automation · score 67
Install: claude install-skill Neetx/ai-security-research-radar
# Render the dashboard (README.md) `README.md` is what GitHub renders on the repo home page — it IS the radar's output surface. It is fully derived from `TRENDS.md`; regenerate it from scratch on every run, never patch it. Design goal: one screen, everything clickable. ## Layout (exactly these blocks, in this order) 1. **Title** — `# AI Radar`. 2. **Badge row** — four shields.io static badges, style `flat-square`: `trends-<total>-3266ad`, `accelerating-<n>-e8590c`, `watchlist-<queue count>-6c757d`, `updated-<YYYY--MM--DD>-2f9e44` (escape `-` in dates as `--`). 3. **Intro line** — one sentence: what the radar tracks, for whom, and that the page is generated from [TRENDS.md](TRENDS.md). 4. **Digest** — `**Since last scan (YYYY-MM-DD):**` + 3–4 bullets MAX, in priority order: stage moves, queue promotions/drops, strongest new evidence. Every bullet must contain at least one link (trend anchor or evidence URL). If nothing changed: one bullet, "Quiet scan — no ledger changes." NAME every trend by its LABEL, never by a bare number: write the readable slug or the short label (`agentic-attack-surface-001`, "Agent-stack attacks"). `001`, `Trend 008` and every other bare-number reference are FORBIDDEN in prose — the number belongs inside the anchor/URL, not in the text a human reads. An id is self-describing only to someone who already has the ledger open, and this page is read by someone who does not. 5. **Pinned topics (⭐)** — `## ⭐ Pinned topic