radar-render-dashboard
Skill4 starsChanged 5 months agoMITView on GitHub
Renders the self-contained local HTML dashboard for a run by injecting the run's data JSON into the dashboard template. Produces one HTML file with inline CSS and JS and no external requests that the user can open directly in a browser. Use after radar-merge-briefing, as the last surface in a /radar run.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- Neetx/ai-research-radartheir own version, first seen Oct 31, 2026
- Neetx/ai-security-research-radartheir own version, first seen Oct 22, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- Neetx/ai-security-research-radar★ 8same name
- Neetx/ai-research-radar★ 5same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- radar-diff-changesSkill
- radar-merge-briefingSkill
- radar-onboardSkill
- radar-plan-targetsSkill
- radar-provision-notionSkill
- radar-publish-councilSkill
- radar-publish-notionSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Read the template at ${CLAUDE_PLUGIN_ROOT}/assets/dashboard-template.html.
- Very specific: line 25
Write the result to outputs/dashboard/<YYYY-MM-DD>-dashboard.html.
- Distinctive: line 38
No write permission to outputs: report the error and the intended path rather than failing silently.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
radar-render-dashboard
Automation level: AUTONOMOUS.
Goal: produce one double-clickable HTML file that shows the run, works offline, and needs no build step or dependencies.
Steps
- Inputs: the run date and the dashboard data JSON path from
radar-merge-briefing(outputs/dashboard/<YYYY-MM-DD>-data.json). Read it. - Read the template at
${CLAUDE_PLUGIN_ROOT}/assets/dashboard-template.html. - Inject the data: replace the single placeholder
{{RADAR_DATA_JSON}}(inside the<script id="radar-data" type="application/json">block) with the exact JSON contents. Do not add script tags, CDN links, or external fonts. The data must be inline JSON so the file is fully self-contained. - Write the result to
outputs/dashboard/<YYYY-MM-DD>-dashboard.html. Also write or overwriteoutputs/dashboard/index.htmlas a copy of the latest run for a stable "open this" path. - Confirm the absolute path and tell the user they can open it in any browser. Offer to open it
(on macOS,
open <path>), but do not require it.
Edge cases
- The data JSON contains characters that could break the inline script: the template reads the JSON with JSON.parse from a typed script block, so standard JSON is safe. Ensure the JSON does not contain the literal sequence that closes a script tag; if a value does, escape the slash.
- War room not yet present: leave
war_roomnull; the dashboard shows a prompt to run/radar-council.radar-publish-councilre-renders later with the addendum filled in. - No write permission to outputs: report the error and the intended path rather than failing silently.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

