agentleFS
sabahudin-websabahudin-web/competitive-intelligence-radar/skills/radar-render-dashboard/SKILL.md

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

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
  1. Very specific:

    Read the template at ${CLAUDE_PLUGIN_ROOT}/assets/dashboard-template.html.

    line 18
  2. Very specific:

    Write the result to outputs/dashboard/<YYYY-MM-DD>-dashboard.html.

    line 25
  3. Distinctive:

    No write permission to outputs: report the error and the intended path rather than failing silently.

    line 38

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Inputs: the run date and the dashboard data JSON path from radar-merge-briefing (outputs/dashboard/<YYYY-MM-DD>-data.json). Read it.
  2. Read the template at ${CLAUDE_PLUGIN_ROOT}/assets/dashboard-template.html.
  3. 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.
  4. Write the result to outputs/dashboard/<YYYY-MM-DD>-dashboard.html. Also write or overwrite outputs/dashboard/index.html as a copy of the latest run for a stable "open this" path.
  5. 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_room null; the dashboard shows a prompt to run /radar-council. radar-publish-council re-renders later with the addendum filled in.
  • No write permission to outputs: report the error and the intended path rather than failing silently.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.