agentsclimarketplace

Radar render dashboard

Skill Neetx/ai-research-radar/.claude/skills/radar-render-dashboard

AI Research Radar — Evidence-Grounded Trend Ledger for AI Systems

Install
npx -y skills add Neetx/ai-research-radar --skill radar-render-dashboard

Assembled 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.
  • 2 stars2 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

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.

SKILL.md

4.5 KB, as published. Nobody here has run it

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.
  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."
  5. Pinned topics (⭐) — ## ⭐ Pinned topics then a table of ONLY the trends with pinned: true, same columns as the main table. These are the curator's standing-watch axes; they appear here AND in the main table (where their trend label is prefixed with ⭐). Sort by last_evidence descending.
  6. Trends section — stage strip on one line (🌱 n · 📈 n · 🚀 n · 🌊 n · 🏔 n · 📉 n · 💤 n), then ONE table | trend | stage | latest signal | with ALL trends (pinned included, prefix their label with ⭐), sorted accelerating → emerging → seed → mainstreaming → saturated → declining → dormant, then by last_evidence descending:
    • trend = short label (≤5 words; reuse previous README labels for stability) linking to the trend's anchor in TRENDS.md (see anchor rule); prefix with ⭐ when pinned: true.
    • stage = emoji + word.
    • latest signal = the last_evidence date linking to the evidence URL whose date equals last_evidence (first match in list order); if none matches, link the top evidence item.
  7. Worth studying — the study_shelf section of TRENDS.md, newest first, up to 12 bullets: [name](url) — one line of why (the shelf persists ~20 picks / 30 days so a reader away for a couple of weeks can still catch up).
  8. Community pulse — ## Community pulse (Phase 3): up to 5 bullets distilled from the latest radar-pulse intake — non-evidence, link-only, NEVER naming individuals (link the thread/profile, summarise). If no pulse data yet, one line: "No community pulse sampled yet." This section is clearly marked as unverified sentiment, separate from the verified trend table.
  9. Output map — one line of links: TRENDS.md, watchlist (queue count) → TRENDS.md#observation_queue, reports/ + newest daily, newest weekly ("weekly: none yet" if absent), AGENTS.md, SOURCES.md.

Anchor rule (GitHub heading slugs)

For a heading ### [id: slug-NNN] Title, the anchor is: lowercase the whole heading text, delete every character that is not a letter, digit, space or hyphen (no replacement — Prefill/decode → prefilldecode), then replace spaces with hyphens. Example: ### [id: pd-disagg-002] Prefill/decode disaggregation as the standard LLM serving architecture → TRENDS.md#id-pd-disagg-002-prefilldecode-disaggregation-as-the-standard-llm-serving-architecture. Anchors are recomputed at every render, so title edits stay in sync.

Checks before commit

  • Badge counts = stage-strip counts = table row count = number of ### [id: blocks in TRENDS.md.
  • Every table date equals that trend's last_evidence exactly; every row has two working relative/absolute links.
  • No Mermaid, no images besides the badges, no sections beyond the blocks above.
  • Pinned-topics table contains exactly the pinned: true trends; every pinned trend is ⭐-prefixed in the main table too.
  • Community-pulse items are link-only and name no individuals.
  • Commit README.md together with the TRENDS.md change that triggered it.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.